fix-github-issue
Skill833 starsChanged 9 months agoApache-2.0View on GitHub
Fix a GitHub issue by number. Use when asked to fix GitHub issues.
- Commits and pushes
5 other projects use a version of this.
Adopted by
Most recently taken up by
- simiancraft/simiancraft-skillstheir own version, first seen Nov 1, 2026
- fxmartin/claude-code-configtheir own version, first seen Oct 31, 2026
- drvoss/everything-copilot-clitheir own version, first seen Oct 26, 2026
- open-guji/luatex-cntheir own version, first seen Oct 9, 2026
- Shopify/flash-listtheir own version, first seen Mar 24, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- Shopify/flash-list★ 7.2ksame name
- open-guji/luatex-cn★ 127same name
- drvoss/everything-copilot-cli★ 48same name
- simiancraft/simiancraft-skills★ 8same name
- fxmartin/claude-code-config★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- check-accessibilitySkill
- explain-codeSkill
- implement-ag-playbookSkill
- implement-github-featureSkill
- update-component-docsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 8 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Read .claude/PROJECT_CONTEXT.md for AgnosticUI structure, conventions, and workflows
- Distinctive: line 20
Check git status to ensure working directory is clean
- Distinctive: line 22
If not clean or on wrong branch, STOP and ask user to resolve
- Very specific: line 25
Follow convention from PROJECT_CONTEXT: issue-$ARGUMENTS/descriptive-name
- Very specific: line 31
Use gh issue view $ARGUMENTS to fetch full issue details
- Very specific: line 35
Use PROJECT_CONTEXT to identify relevant locations:
- Distinctive: line 39
Use Read, Grep, and Glob to find relevant files
- Distinctive: line 44
Consider impact across Lit, React, and Vue if applicable
- Very specific: line 45
Follow AgnosticUI's CSS-first, accessibility-focused principles
- Distinctive: line 51
Update related files (tests, docs, examples) if needed
- Very specific: line 52
Run tests if applicable (check PROJECT_CONTEXT for test commands)
- Distinctive: line 53
Verify the fix addresses the issue
- Distinctive: line 57
Create descriptive commit message: "Fix #$ARGUMENTS: [description]"
- Very specific: line 64
When ready, they can: git push -u origin issue-$ARGUMENTS/...
- Distinctive: line 72
Use clear, descriptive commit messages that reference the issue
- Very specific: line 73
Follow AgnosticUI conventions from PROJECT_CONTEXT
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Usage: /fix-github-issue ISSUE_NUMBER
Example: /fix-github-issue 276
Fix GitHub issue $ARGUMENTS following best practices.
Setup:
- Read
.claude/PROJECT_CONTEXT.mdfor AgnosticUI structure, conventions, and workflows
Steps:
- Verify we're starting from a clean state:
- Check
git statusto ensure working directory is clean - Confirm we're on
masterbranch - If not clean or on wrong branch, STOP and ask user to resolve
- Check
- Create a feature branch:
- Follow convention from PROJECT_CONTEXT:
issue-$ARGUMENTS/descriptive-name - Example:
issue-276/fix-button-variant - Use
git checkout -b issue-$ARGUMENTS/[short-description] - WAIT FOR USER APPROVAL of branch name
- Follow convention from PROJECT_CONTEXT:
- Analyze the issue:
- Use
gh issue view $ARGUMENTSto fetch full issue details - Understand the problem, reproduction steps, and expected behavior
- Use
- Investigate the codebase:
- Use PROJECT_CONTEXT to identify relevant locations:
- Core components in
v2/lib/src/components/ - Framework implementations in playgrounds
- Related tests and examples
- Core components in
- Use Read, Grep, and Glob to find relevant files
- Review current implementation and identify root cause
- Use PROJECT_CONTEXT to identify relevant locations:
- Propose the fix:
- Explain what needs to change and why
- Consider impact across Lit, React, and Vue if applicable
- Follow AgnosticUI's CSS-first, accessibility-focused principles
- Show the user your proposed changes
- WAIT FOR USER APPROVAL before making any changes
- Implement only after approval:
- Make the necessary code changes
- Update related files (tests, docs, examples) if needed
- Run tests if applicable (check PROJECT_CONTEXT for test commands)
- Verify the fix addresses the issue
- Prepare commit:
- Stage changes with
git add - Create descriptive commit message: "Fix #$ARGUMENTS: [description]"
- Show the user what will be committed
- WAIT FOR USER APPROVAL before committing
- Stage changes with
- Inform user about next steps:
- Remind user they're on branch
issue-$ARGUMENTS/... - Explain they should review changes with
git diff master - When ready, they can:
git push -u origin issue-$ARGUMENTS/... - Then create PR with:
gh pr create --base master --head issue-$ARGUMENTS/...
- Remind user they're on branch
Important Rules:
- ALWAYS create a feature branch - NEVER work directly on master
- NEVER push to remote without explicit user permission
- ALWAYS show proposed changes before implementing
- STOP and ask for approval at each major step
- Use clear, descriptive commit messages that reference the issue
- Follow AgnosticUI conventions from PROJECT_CONTEXT
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.