Skip to content

fix(skills/reporting-a-skill-gap): let the location block hold several skills #89

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sourcehawk merged 2 commits into from
Oct 6, 2026
Merged

fix(skills/reporting-a-skill-gap): let the location block hold several skills #89

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
85f2870
fix(skills/reporting-a-skill-gap): let the location block hold more t…
sourcehawk Oct 6, 2026
8919965
fix(skills/reporting-a-skill-gap): give the title and reproduction a …
sourcehawk Oct 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions skills/reporting-a-skill-gap/templates/skill-gap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ When you comment on an existing issue instead of filing a new one, the comment h

# <plain-english-title>

<!-- Title rule: a human-readable sentence that names the skill and the failure. Example: "fanning-out-with-worktrees: parallel subagents overwrite each other's files in the shared scratch directory". -->
<!-- Title rule: a human-readable sentence that names the skill and the failure. Example: "fanning-out-with-worktrees: parallel subagents overwrite each other's files in the shared scratch directory". When more than one skill is involved, name each of them, joined with "and". -->

## What happened

Expand All @@ -25,13 +25,13 @@ When you comment on an existing issue instead of filing a new one, the comment h
## Where in the plugin

<!--
Exactly these three lines:
One Skill and Section pair for each skill, then one Plugin version line:

- Skill: `feature-dev-workflow:<name>`
- Section: `<the heading, copied from the installed SKILL.md, with its # marks>`
- Plugin version: `<version from .claude-plugin/plugin.json>`

When the failure is that a skill did not trigger, the section is `description` (the frontmatter trigger text). When more than one skill is involved, repeat the Skill and Section lines for each.
When the failure is that a skill did not trigger, the section is `description` (the frontmatter trigger text). When more than one skill is involved, write the Skill and Section pair once for each skill, and the Plugin version line once at the end.
-->

<!-- optional -->
Expand All @@ -42,7 +42,7 @@ When the failure is that a skill did not trigger, the section is `description` (

## Reproduction

<!-- Required. A self-contained scenario that a maintainer can hand to a fresh subagent as a RED baseline. It must run without access to this session or the user's project: every fact the agent needs is written here, in generic terms. -->
<!-- Required. A self-contained scenario that a maintainer can hand to a fresh subagent as a RED baseline. It must run without access to this session or the user's project: every fact the agent needs is written here, in generic terms. When the gap spans an agent and the agents it dispatches, write one scenario for the agent that dispatches: the Task prompt is the message it receives, the Environment facts name the skill that each dispatched agent follows, and the Failure predicate checks the dispatch prompts and what the dispatched agents do, in the same run. -->

### Situation

Expand Down
Loading