fix-issue
Skill1 starsChanged 23 days agoApache-2.0View on GitHub
Reproduce and resolve a repository issue, then validate local changes.
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
- 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
- Birfy/agentdescenttheir own version, first seen Oct 25, 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 repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-testSkill
- audit-fixissuesSkill
- autoresearchSkill
- benchmark-optimizeSkill
- circleci-job-resultsSkill
- citation-verifierSkill
- cli-designSkill
- codebase-auditSkill
- code-cleanupSkill
- deep-code-cleanupSkill
- doc-updateSkill
- emendSkill
- git-github-workflowSkill
- goal-modeSkill
- inspect-datasetSkill
- manage-pr-lifecycleSkill
- medcognetics-brandSkill
- notify-wakeSkill
- repo-maintenanceSkill
- review-fix-loopSkill
- standardize-ciSkill
- token-file-authSkill
- whats-nextSkill
- yeetSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 51 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Read current requirements and relevant discussion.
- Distinctive: line 17
If automation is impractical, use a deterministic reproduction and explain the limitation.
- Distinctive: line 24
Run affected tests and applicable repository gates.
- Distinctive: line 27
Leave changes unstaged and uncommitted by default.
“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 Issue
Accept an issue number, URL, or pasted text. With no issue context, use working changes. If none exist, identify a concrete bug in the repository and report a no-op when no actionable defect is found.
Read current requirements and relevant discussion. Define the expected outcome
from repository evidence. Use $git-github-workflow for GitHub reads or requested
publication, without invoking its default publish flow.
For a reproducible bug, add and run a failing regression before the fix. If automation is impractical, use a deterministic reproduction and explain the limitation. Do not invent a defect when the evidence contradicts the report.
Implement the smallest complete solution. Resolve routine tooling problems and failures caused by the change. Ask only when requirements conflict, a necessary decision is missing, or the next action exceeds existing authority.
Run affected tests and applicable repository gates. Continue until the issue's acceptance criteria pass or a concrete blocker prevents further work.
Leave changes unstaged and uncommitted by default. Commit, push, and create a PR only when explicitly requested. For an issue-backed PR, include its closing keyword.
Report the issue, reproduction evidence, changes, validation, and remaining blockers.
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.

