fix-issue
Skill1 starsChanged 9 months agoApache-2.0View on GitHub
Fix a GitHub issue end-to-end. Use when given an issue number to fix, implementing bug fixes, or addressing reported problems.
- Commits and pushes
53 other projects use a version of this.
Adopted by
Most recently taken up by
- domengabrovsek/agent-configtheir own version, first seen Nov 8, 2026
- domengabrovsek/claudetheir own version, first seen Nov 8, 2026
- TidalPaladin/skillstheir own version, first seen Nov 8, 2026
- ThinkFlowLab/agentdescenttheir own version, first seen Nov 8, 2026
- getsentry/sentry-javascripttheir own version, first seen Nov 6, 2026
- encoreshao/encore-skillstheir own version, first seen Oct 29, 2026
Used with
Projects with it also use prepare-release, document and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ShopifySkillprepare-release
Prepare the changeset-release/main branch for release by syncing version.ts files and running pnpm install
Also in 4 projects that use this
nicolasestremSkilldocument
Create focused documentation for specific components or features
Also in 4 projects that use this
GitHubSkillrefactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Also in 5 projects that use this
SentrySkillwrite-tests
Write tests following project conventions. Use when adding new tests or modifying existing ones.
Also in 3 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 6 projects that use this
Microsoft AzureSkillbuild
Build the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.
Also in 4 projects that use this
Other versions53 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 53
- pytorch/pytorch★ 105ksame name
- ZhuLinsen/daily_stock_analysis★ 68ksame name
- Dokploy/dokploy★ 38ksame name
- remix-run/remix★ 33ksame name
- PrefectHQ/fastmcp★ 28ksame name
- jlowin/fastmcp★ 28ksame name
- NVIDIA-NeMo/Speech★ 19ksame name
- NVIDIA-NeMo/NeMo★ 19ksame name
- getsentry/sentry-javascript★ 8.8ksame name
- datlechin/TablePro★ 6.4ksame name
43 more not listed
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 repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/tech-stack.mdcCursor rule
- build-and-fixSkill
- bumpup-versionsSkill
- clean-projectSkill
- improve-claude-configSkill
- initialize-projectSkill
- lint-and-fixSkill
- manage-adrSkill
- manage-changelogSkill
- node-upgradeSkill
- security-vulnerability-auditSkill
- setup-dev-envSkill
- sync-readmeSkill
- test-and-fixSkill
- test-integration-dockerSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 51 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Search for relevant code:
- Distinctive: line 60
Don't refactor unrelated code
- Distinctive: line 61
Keep changes focused and reviewable
- Distinctive: line 68
Verify the fix works (should pass with fix)
- Distinctive: line 73
Run the verification cycle:
“Common” is measured: kept by at least 6 in 10 of the 51 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
Fix GitHub Issue
Purpose
A complete workflow for fixing GitHub issues from understanding the problem to creating a pull request.
Arguments
$ARGUMENTS: GitHub issue number (e.g.,123or#123)
Workflow
1. Understand the Issue
gh issue view $ARGUMENTSAnalyze:
- What is the reported problem?
- What is the expected behavior?
- What is the actual behavior?
- Are there reproduction steps?
2. Research the Codebase
Search for relevant code:
# Search for keywords from the issue
grep -r "keyword" src/
# Find related files
find . -name "*.ts" | xargs grep -l "relatedTerm"Understand:
- Which files are involved?
- What is the current implementation?
- Where does the bug originate?
3. Create Feature Branch
git checkout -b fix/issue-$ARGUMENTS-<brief-description>4. Implement the Fix
Apply the minimum necessary change to resolve the issue:
- Fix the root cause, not symptoms
- Don't refactor unrelated code
- Keep changes focused and reviewable
5. Add/Update Tests
Create tests that:
- Reproduce the original bug (should fail without fix)
- Verify the fix works (should pass with fix)
- Cover edge cases
6. Verify the Fix
Run the verification cycle:
pnpm lint
pnpm test
pnpm buildOr invoke the verifier subagent for comprehensive validation.
7. Commit Changes
git add <specific-files>
git commit -m "fix(scope): brief description
Fixes #$ARGUMENTS"8. Create Pull Request
git push -u origin HEAD
gh pr create --title "fix(scope): description" --body "$(cat <<'EOF'
## Summary
Fixes #$ARGUMENTS
## Problem
[Description of the issue]
## Solution
[How this PR fixes it]
## Testing
- [ ] Added test case for the bug
- [ ] All tests pass
- [ ] Manually verified the fix
## Changes
- [List specific changes]
EOF
)"Quick Reference
| Task | Command |
| View issue | gh issue view <number> |
| List issues | gh issue list |
| Create branch | git checkout -b fix/issue-<n>-<desc> |
| Link PR to issue | Include Fixes #<n> in commit message |
| Close issue via PR | Include Closes #<n> in PR body |
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.

