agentleFS
eugnmueller-87eugnmueller-87/claude-blueprint/.claude/skills/fix-issue/SKILL.md

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

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.
  • ShopifySkill

    prepare-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

  • nicolasestremSkill

    document

    Create focused documentation for specific components or features

    Also in 4 projects that use this

  • SentrySkill

    write-tests

    Write tests following project conventions. Use when adding new tests or modifying existing ones.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    build

    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

  • MicrosoftSkill

    adversarial-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 AzureSkill

    test

    Also in 4 projects that use this

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
  1. Distinctive:

    Run them; show green.

    line 32

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. 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.
  2. 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, consider tdd.
  3. Branch. git switch -c fix/<n>-<short-desc> (or feat/<n>-...). Never work an issue directly on main.
  4. 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.
  5. Land it via ship. The PR body must reference the issue so it auto-closes: include Closes #<n>. State what changed, why, and the test evidence.
  6. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.