agentsclimarketplace

Fix issue

Skill yu-iskw/coding-agent-fabric/.claude/skills/fix-issue

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

Install
npx -y skills add yu-iskw/coding-agent-fabric --skill fix-issue

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 8 commands, including `gh issue view $ARGUMENTS` and 7 more.

SKILL.md

2.4 KB, 590 tokens by cl100k_base, as published. Nobody here has run it

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.