agentleFS
joris887joris887/exosuit/.claude/skills/fix-issue/SKILL.md

fix-issue

Skill9 starsChanged 3 months agoMITView on GitHub

Fix a GitHub issue following project coding standards. Creates branch, implements fix with TDD, and prepares PR.

  • Commits and pushes

53 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 8 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

  • GitHubSkill

    refactor

    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

  • SentrySkill

    write-tests

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

    Also in 3 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 6 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

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 8

    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:

    Read the issue description carefully

    line 27
  2. Distinctive:

    Check for related issues or PRs

    line 28
  3. Distinctive:

    Use Glob and Grep to find related files

    line 54
  4. Distinctive:

    Write a failing test that reproduces the issue

    line 61
  5. Distinctive:

    Verify the test fails for the right reason

    line 62
  6. Distinctive:

    Verify the test passes

    line 64
  7. Distinctive:

    Run full test suite (use project's test command from CLAUDE.md)

    line 65
  8. Distinctive:

    Ensure code passes linting and type checking

    line 69

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

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

fix-issue

Fix GitHub issue $ARGUMENTS following project coding standards.

1. Get Issue Details

gh issue view $ARGUMENTS

2. Understand the Problem

  • Read the issue description carefully
  • Check for related issues or PRs
  • Identify acceptance criteria

3. Create Feature Branch

Detect the default branch dynamically:

DEFAULT_BRANCH=$(grep -oP '^\- \*\*Default branch:\*\* \K\S+' CLAUDE.md 2>/dev/null)
if [ -z "$DEFAULT_BRANCH" ]; then
    DEFAULT_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@')
fi
if [ -z "$DEFAULT_BRANCH" ]; then
    for branch in main master develop; do
        if git show-ref --verify --quiet "refs/heads/$branch"; then DEFAULT_BRANCH="$branch"; break; fi
    done
fi
git checkout $DEFAULT_BRANCH
git pull origin $DEFAULT_BRANCH
git checkout -b fix/issue-$ARGUMENTS

Note: This skill is a standalone quick-fix flow (issue → branch → TDD fix → PR). For fixes that are part of an active sprint, use /story-cycle instead — it integrates with the sprint branch and quality gates.

4. Search for Relevant Code

  • Use Glob and Grep to find related files
  • Understand the current implementation
  • Identify what needs to change
  • <IF condition="docs/adr/ contains accepted ADR files">Check docs/adr/ for accepted decisions that constrain the fix approach — the fix must respect existing architectural decisions</IF>

5. Implement Fix (TDD)

  1. Write a failing test that reproduces the issue
  2. Verify the test fails for the right reason
  3. Implement the minimal fix
  4. Verify the test passes
  5. Run full test suite (use project's test command from CLAUDE.md)

6. Verify Fix

  • Ensure code passes linting and type checking
  • Review changes for quality

7. Commit and Push

git add .
git commit -m "$(cat <<'EOF'
fix: resolve issue #$ARGUMENTS

[Description of what was fixed and how]

Closes #$ARGUMENTS

Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"
git push -u origin fix/issue-$ARGUMENTS

8. Create PR

gh pr create --title "fix: resolve issue #$ARGUMENTS" --body "$(cat <<'EOF'
## Summary
Fixes #$ARGUMENTS

## Changes
- [List of changes made]

## Testing
- Added test to reproduce issue
- All tests passing

## Checklist
- [x] Issue reproduced with failing test
- [x] Fix implemented
- [x] All tests pass
- [x] Code follows project standards

Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"

Output the PR URL when complete.

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.