implementing-github-issue
Skill2 starsChanged 2 months agoBSD-3-ClauseView on GitHub
Implements what is described in a GitHub issue. What this does is first devise an implementation plan from the issue, execute the plan and validate production qualiy gates. Use this when the user is asking you to implement a GitHub issue. Use this skill also in Plan mode.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- addressing-pull-request-commentsSkill
- analyzing-github-issueSkill
- applying-ruby-conventionsSkill
- applying-test-conventionsSkill
- committing-changesSkill
- creating-pull-requestSkill
- editing-filesSkill
- enforcing-project-rulesSkill
- improving-agent-reflectionSkill
- running-cli-in-wsl-portableSkill
- syncing-branch-with-baseSkill
- updating-docSkill
- validating-production-qualitySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 13 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
When implementing a GitHub issue, follow those steps.
- Distinctive: line 19
Before executing anything, create a checklist named implementing-github-issue Execution Checklist with all steps of these instructions.
- Distinctive: line 21
After completing each step of these instructions, mark the item in the implementing-github-issue Execution Checklist as completed.
- Distinctive: line 22
Do not skip any item.
- Distinctive: line 23
If an item cannot be executed, explicitly explain why.
- Distinctive: line 24
Never mark the task as completed while any item from the implementing-github-issue Execution Checklist remains open.
- Distinctive: line 28
Always tell the user "SKILL: I am implementing a GitHub issue" to inform the user that you are running this skill.
- Very specific: line 32
Always use skill: analyzing-github-issue to get a full implementation plan.
- Distinctive: line 36
Always perform all the agreed steps from the implementation plan to implement the issue.
- Distinctive: line 37
Always perform a final verification of the implementation plan against all the actions you did.
- Very specific: line 41
Always use skill: validating-production-quality before attempting task completion to make sure that all needed quality gates are passing.
- Distinctive: line 45
Before declaring the task complete:
- Distinctive: line 49
If any step was not executed, execute it now.
- Very specific: line 54
Always use it every time another skill specifically mentions skill: implementing-github-issue.
- Distinctive: line 55
Always use it every time the user asks you to implement a GitHub issue.
- Distinctive: line 56
Always use it every time you need to implement a GitHub issue.
- Very specific: line 63
Use the skill named analyzing-github-issue to get an implementation plan
- Very specific: line 65
Use the skill named validating-production-quality to check all production quality gates
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Implementing a GitHub issue
Sequential steps to be followed when using this skill
When implementing a GitHub issue, follow those steps.
Create the implementing-github-issue Execution Checklist (MANDATORY)
- Before executing anything, create a checklist named implementing-github-issue Execution Checklist with all steps of these instructions.
- The implementing-github-issue Execution Checklist must include all numbered steps explicitly.
- After completing each step of these instructions, mark the item in the implementing-github-issue Execution Checklist as completed.
- Do not skip any item.
- If an item cannot be executed, explicitly explain why.
- Never mark the task as completed while any item from the implementing-github-issue Execution Checklist remains open.
1. Inform the user
- Always tell the user "SKILL: I am implementing a GitHub issue" to inform the user that you are running this skill.
2. Analyze the GitHub issue requirements to get an implementation plan (can be done when in Plan mode)
- Always use
skill: analyzing-github-issueto get a full implementation plan. This plan will take into consideration requirements from the issue, user inputs and the project's context.
3. Implement the issue following the implementation plan
- Always perform all the agreed steps from the implementation plan to implement the issue.
- Always perform a final verification of the implementation plan against all the actions you did. If you think some steps of the implementation plan were not implemented properly or are missing, fix it or inform the user about those missing steps.
4. Validate all production quality checks
- Always use
skill: validating-production-qualitybefore attempting task completion to make sure that all needed quality gates are passing.
Final Verification (MANDATORY)
Before declaring the task complete:
- Re-list all numbered steps from the implementing-github-issue Execution Checklist.
- Confirm each one was executed.
- If any step was not executed, execute it now.
When to use it
- This skill can be used when in Plan mode.
- Always use it every time another skill specifically mentions
skill: implementing-github-issue. - Always use it every time the user asks you to implement a GitHub issue.
- Always use it every time you need to implement a GitHub issue.
Usage and code examples
Implementing a GitHub issue
This skill should perform the following steps:
- Use the skill named
analyzing-github-issueto get an implementation plan - Execute all the steps that are identified in the implementation plan
- Use the skill named
validating-production-qualityto check all production quality gates
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

