AgentStack
SKILL verified MIT Self-run

Github Fix Issue

skill-feiskyer-claude-code-settings-github-fix-issue · by feiskyer

Fix GitHub issues end-to-end — from analysis through branch creation, implementation, testing, and PR submission. Use this skill whenever the user mentions fixing a GitHub issue, resolving a bug from an issue tracker, working on a GitHub issue number, or says things like "fix issue #123", "work on this issue", "resolve the bug in issue", or references a GitHub issue URL. Also trigger when the use…

No reviews yet
0 installs
10 views
0.0% view→install

Install

$ agentstack add skill-feiskyer-claude-code-settings-github-fix-issue

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Github Fix Issue? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Fix GitHub Issue

A structured workflow for analyzing, fixing, and submitting a PR for a GitHub issue. This skill uses the GitHub CLI (gh) for all GitHub interactions.

Workflow

1. Understand the Issue

  • Run gh issue view to get full issue details (title, body, labels, comments)
  • Read through the problem description carefully
  • If the issue is unclear or missing key details, ask the user clarifying questions before proceeding

2. Research Prior Art

Before jumping into code, gather context — understanding what's been tried or discussed prevents duplicate work and surfaces useful patterns:

  • Search the codebase for files and functions related to the issue
  • Check if related PRs exist with gh pr list --search ""
  • Look for scratchpads or notes from previous investigation
  • Read relevant source files to understand the current behavior

3. Plan the Fix

Think through how to break the issue into small, manageable tasks. Document your plan in a scratchpad file:

  • Name the file descriptively (include the issue reference)
  • Include a link back to the issue
  • List the specific changes needed and their order
  • Note any risks or edge cases

4. Implement

  • Create a new branch for the issue (e.g., fix/issue-123-description)
  • Work through the plan in small steps
  • Commit after each meaningful change — small commits are easier to review and revert

5. Test

Thorough testing prevents the fix from introducing new problems:

  • Write unit tests that describe the expected behavior
  • Run the full test suite to catch regressions
  • If UI changes were made and browser automation (e.g., Puppeteer MCP) is available, use it to verify visually
  • Fix any failing tests before moving on

6. Open Pull Request

  • Push the branch and open a PR with gh pr create
  • Reference the issue in the PR description (e.g., "Fixes #123")
  • Request a review

gh Command Reference

# View issue details
gh issue view 123

# Create a branch
git checkout -b fix/issue-123-description

# Open a PR that closes the issue
gh pr create --title "Fix: description" --body "Fixes #123"

# Request review
gh pr edit 456 --add-reviewer username

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.