fix-github-issue

DCRepairCenter's avatarfrom DCRepairCenter

Workflow for analyzing and fixing GitHub issues. Use when given an issue number to investigate and resolve.

⭐0stars🔀1forks📁View on GitHub🕐Updated Jan 1, 2026
[Debugging]

When & Why to Use This Skill

This Claude skill automates the end-to-end process of resolving GitHub issues. It systematically fetches issue details, analyzes the codebase to identify root causes, implements fixes following specific coding standards, validates changes through linting and testing, and manages the submission process via conventional commits and pull requests. By streamlining the transition from issue report to verified patch, it significantly reduces the manual overhead for developers maintaining complex repositories.

Use Cases

  • Automated Bug Fixing: Quickly address reported bugs by providing the issue number, allowing the agent to handle the investigation, root cause analysis, and patch creation.
  • Codebase Maintenance: Streamline the process of resolving technical debt or minor improvements tracked in GitHub issues while ensuring all changes adhere to project-specific coding standards.
  • Standardized PR Workflow: Ensure all fixes undergo rigorous local validation—including linting, type checking, and unit testing—before being submitted as professional pull requests with conventional commit messages.
namefix-github-issue
descriptionWorkflow for analyzing and fixing GitHub issues. Use when given an issue number to investigate and resolve.

Fix GitHub Issue Skill

Analyze and fix GitHub issues systematically.

Workflow

  1. Get Issue Details

    gh issue view <issue_number>

  2. Understand the Problem

    • Read issue description and comments
    • Identify affected components
    • Determine root cause

  3. Search Codebase

    • Find relevant files
    • Understand current implementation
    • Check related tests

  4. Implement Fix

    • Follow coding standards (see code-writer skill)
    • Import contracts from rainze.core.contracts
    • Add bilingual comments

  5. Validate

    make lint      # Check linting
make typecheck # Check types
make test      # Run tests

  6. Commit & PR

    • Use conventional commit format
    • Reference issue number: Fixes #<number>
    • Create PR with description

Requirements

  • Follow CLAUDE.md coding standards
  • Run make check before committing
  • Include test for the fix when applicable