fix-issue
Skill1 starsChanged 5 months agoMITView on GitHub
Take a GitHub issue from read to closed — pull the issue, plan the fix, implement it on a feature branch, and open a PR that references and closes the issue. Use when working a tracked issue by number. Trigger phrases "fix issue #N", "work issue N", "take issue #N".
54 other projects use a version of this.
Adopted by
Most recently taken up by
- encoreshao/encore-skillstheir own version, first seen Nov 16, 2026
- charlesmsiegel/coding-skillstheir own version, first seen Nov 15, 2026
- elfrost/ai-patchlabtheir own version, first seen Nov 9, 2026
- 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
Used with
Projects with it also use prepare-release, document and 6 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
SentrySkillwrite-tests
Write tests following project conventions. Use when adding new tests or modifying existing ones.
Also in 3 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
MicrosoftSkilladversarial-review
Adversarial review of a system design from 6 critical perspectives -- SRE, security, staff engineer, finance, operator, and developer advocate. Produces a unified risk assessment. Use for INTERACTIVE on-demand reviews during a design conversation (/adversarial-review). For RECIPE-DRIVEN reviews (where prior step context is needed), use the systems-design-critic agent instead.
Also in 3 projects that use this
Microsoft AzureSkilltest
Also in 4 projects that use this
Other versions54 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 54
- pytorch/pytorch★ 106ksame name
- ZhuLinsen/daily_stock_analysis★ 72ksame name
- Dokploy/dokploy★ 39ksame name
- remix-run/remix★ 33ksame name
- PrefectHQ/fastmcp★ 29ksame name
- jlowin/fastmcp★ 29ksame name
- NVIDIA-NeMo/NeMo★ 19ksame name
- NVIDIA-NeMo/Speech★ 19ksame name
- getsentry/sentry-javascript★ 8.8ksame name
- datlechin/TablePro★ 6.5ksame name
44 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.
- catchupSkill
- claude-mdSkill
- context-budgetSkill
- db-querySkill
- debug-fixSkill
- eval-agentSkill
- explainSkill
- incident-ruleSkill
- pr-reviewSkill
- refactorSkill
- secrets-checkSkill
- setup-projectSkill
- shipSkill
- tddSkill
- test-writerSkill
- trace-agentSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 52 edited versions we read keep these.
1
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 32
Run them; show green.
“Common” is measured: kept by at least 6 in 10 of the 52 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-issue
Trigger: "fix issue #N" / "work issue N" / "take issue #N"
Standing rules: ../_conventions.md.
Close the loop cleanly: understand the issue, fix the real cause, land a PR that links back. Don't guess what the issue means — read it. Don't push to main.
Steps
- Read the issue.
gh issue view <n>. Extract: what's actually being asked, the expected vs actual behavior, any repro steps, and acceptance criteria. If the issue is ambiguous or underspecified, say what's unclear and ask before building the wrong thing. - Plan. State in 2–3 bullets how you'll fix it and which files you expect to
touch. If it's a bug, plan to reproduce first (hand off to
debug-fix). If it's a feature, considertdd. - Branch.
git switch -c fix/<n>-<short-desc>(orfeat/<n>-...). Never work an issue directly on main. - Implement. Make the change at the root cause. Add or update tests that encode the issue's acceptance criteria — the test is proof the issue is fixed. Run them; show green.
- Land it via
ship. The PR body must reference the issue so it auto-closes: includeCloses #<n>. State what changed, why, and the test evidence. - Report (terse): issue summary · branch · what you changed · PR url with
Closes #<n>. If you couldn't fully resolve it, say exactly what's left — honestly.
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.

