agentleFS
yu-iskwyu-iskw/coding-agent-fabric/.claude/skills/fix-issue/SKILL.md

fix-issue

Skill1 starsChanged 9 months agoApache-2.0View on GitHub

Fix a GitHub issue end-to-end. Use when given an issue number to fix, implementing bug fixes, or addressing reported problems.

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

  • 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

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 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.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search for relevant code:

    line 33
  2. Distinctive:

    Don't refactor unrelated code

    line 60
  3. Distinctive:

    Keep changes focused and reviewable

    line 61
  4. Distinctive:

    Verify the fix works (should pass with fix)

    line 68
  5. Distinctive:

    Run the verification cycle:

    line 73

“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 GitHub Issue

Purpose

A complete workflow for fixing GitHub issues from understanding the problem to creating a pull request.

Arguments

  • $ARGUMENTS: GitHub issue number (e.g., 123 or #123)

Workflow

1. Understand the Issue

gh issue view $ARGUMENTS

Analyze:

  • What is the reported problem?
  • What is the expected behavior?
  • What is the actual behavior?
  • Are there reproduction steps?

2. Research the Codebase

Search for relevant code:

# Search for keywords from the issue
grep -r "keyword" src/

# Find related files
find . -name "*.ts" | xargs grep -l "relatedTerm"

Understand:

  • Which files are involved?
  • What is the current implementation?
  • Where does the bug originate?

3. Create Feature Branch

git checkout -b fix/issue-$ARGUMENTS-<brief-description>

4. Implement the Fix

Apply the minimum necessary change to resolve the issue:

  • Fix the root cause, not symptoms
  • Don't refactor unrelated code
  • Keep changes focused and reviewable

5. Add/Update Tests

Create tests that:

  • Reproduce the original bug (should fail without fix)
  • Verify the fix works (should pass with fix)
  • Cover edge cases

6. Verify the Fix

Run the verification cycle:

pnpm lint
pnpm test
pnpm build

Or invoke the verifier subagent for comprehensive validation.

7. Commit Changes

git add <specific-files>
git commit -m "fix(scope): brief description

Fixes #$ARGUMENTS"

8. Create Pull Request

git push -u origin HEAD

gh pr create --title "fix(scope): description" --body "$(cat <<'EOF'
## Summary
Fixes #$ARGUMENTS

## Problem
[Description of the issue]

## Solution
[How this PR fixes it]

## Testing
- [ ] Added test case for the bug
- [ ] All tests pass
- [ ] Manually verified the fix

## Changes
- [List specific changes]
EOF
)"

Quick Reference

TaskCommand
View issuegh issue view <number>
List issuesgh issue list
Create branchgit checkout -b fix/issue-<n>-<desc>
Link PR to issueInclude Fixes #<n> in commit message
Close issue via PRInclude Closes #<n> in PR body

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.