Skill

fix-issue

This skill should be used when the user asks to "fix issue", "resolve issue", "address bug in issue", "fix

npx claudepluginhub tim-hub/powerball

Configuration

Model: sonnet

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Automatically analyze and fix the GitHub issue: $ARGUMENTS.

SKILL.md

Similar Skills

github-fix-issue

1.5k

Fixes GitHub issues end-to-end with GitHub CLI: views issue, researches context, plans fix, creates branch, implements/tests changes, submits PR.

claude-code-settings

issue

Implements features or fixes from GitHub, Linear, or GitLab issues by registering the issue, fetching details, applying safety guidelines, creating a branch, committing, and opening a PR.

1 file8 tools

issue

using-superpowers

178.4k

Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.

3 files

superpowers

Stats

Parent Repo Stars2

Parent Repo Forks0

Last CommitMar 23, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Automatically analyze and fix the GitHub issue: $ARGUMENTS.

Use gh issue view $ARGUMENTS to get the issue details. If the issue is not found or gh is not authenticated, stop and report the error.
Understand the problem described in the issue.
Search the codebase for relevant files.
Create and checkout a new branch: git checkout -b fix/<issue-number>-<short-slug> (derive slug from the issue title).
Use /openspec-propose skill to outline a plan to fix the issue, including which files to modify and what changes to make, save it to docs folder. Follow recommended solution if needs confirmation from user before proceeding.
Use /openspec-apply-change skill to implement the necessary changes to fix the issue. Write and run tests to verify the fix. Discover the test runner from package.json, Makefile, or project conventions.
Ensure code passes linting and type checking. Discover the linter from project config if not obvious.
Use the review skill to review all changes, address any feedback, and ensure the code meets quality standards. If unsure of how to implement the fix, ask user for guidance or clarification on the issue.
Use the /openspec-archive-change skill to archive the change once the issue is fixed and all changes are committed.
Use the commit skill to stage and commit the changes.
Use the gh cli to push the branch and open a PR. Reference the issue number in the PR body (e.g. Closes #$ARGUMENTS).