fix-issue
Skill351 starsChanged 3 months agoApache-2.0View on GitHub
Fix a GitHub issue with proper branch, testing, and PR workflow
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, refactor and 9 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
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
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
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 repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/cpp-format.mdcCursor rule
- .cursor/rules/self-improvement.mdcCursor rule
- cmake-workflowSkill
- commit-conventionSkill
- commitSkill
- cursor-rulesSkill
- documentSkill
- fix-prSkill
- formatSkill
- github-prSkill
- gpu-optimizationSkill
- project-structureSkill
- push-tagSkill
- repository-setupSkill
- review-prSkill
- run-testsSkill
- simulation-devSkill
- xmake-workflowSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 5 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
If no issue number is provided, list and ask the developer to pick:
- Very specific: line 18
Note: Always use --repo spiriMirror/libuipc to reference the upstream repository (works with forks).
- Distinctive: line 24
Follow the owner working agreements: work on the current branch.
- Distinctive: line 25
Do not create a new branch as a workflow default.
- Very specific: line 36
Test binaries are in <cmake-binary-directory>/<configuration>/bin/.
- Distinctive: line 38
Run relevant tests to verify the fix.
- Very specific: line 42
Add new tests in apps/tests/ when the bug isn't covered by existing tests.
- Distinctive: line 51
Use the commit command to format, commit, and push.
“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
1. Identify the Issue
If no issue number is provided, list and ask the developer to pick:
gh issue list --repo spiriMirror/libuipc
gh issue view <ISSUE_NUMBER> --repo spiriMirror/libuipcNote: Always use --repo spiriMirror/libuipc to reference the upstream repository (works with forks). See repository-setup for details.
Determine the issue type: bug fix, feature, performance, refactor, docs, or test improvement.
2. Verify the Working Branch
Follow the owner working agreements: work on the current branch. Do not create a new branch as a workflow default; honor any different working branch explicitly selected by the owner.
3. Plan & Implement
Analyze the issue, identify the root cause, then implement the focused fix.
Build with the build command.
4. Test
- Test binaries are in
<cmake-binary-directory>/<configuration>/bin/. - Tests source code is in
apps/tests/. - Run relevant tests to verify the fix. See run-tests command.
Adding New Tests
Add new tests in apps/tests/ when the bug isn't covered by existing tests.
Rules:
- Tests must be independent of each other.
- Tests must cover the bug / feature.
- Do NOT modify existing tests to make a fix pass. If a test itself is wrong, fix it separately and flag it to the developer for review.
5. Commit
Use the commit command to format, commit, and push.
6. Review & PR
Review the changes. Create a PR via github-pr
only when requested; targeting main requires an explicit owner request.
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.