fix-issue

Resolve GitHub issues sequentially by priority with automated code fixes.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/ximing/spark --skill fix-issue-ximing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-issue
Source: https://github.com/ximing/spark/tree/main/.claude/skills/fix.issue
Command: npx skills add https://github.com/ximing/spark --skill fix-issue-ximing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of fixing GitHub issues by automatically prioritizing, assigning, and resolving them using sub-agents, ensuring efficient bug fixing and issue management.

Core Features & Use Cases

  • Prioritized Issue Fixing: Automatically processes GitHub issues based on priority (P0 to P4).
  • Serial Processing: Fixes one issue at a time to ensure thoroughness and prevent parallel conflicts.
  • Sub-Agent Automation: Leverages sub-agents for the actual code fixes, including linting, testing, committing, and closing issues.
  • Use Case: Automatically clear your backlog of high-priority bugs (P0) by having the skill find, fix, and close them sequentially without manual intervention, only pausing for product clarification on complex functional changes.

Quick Start

Use the fix-issue skill to start fixing GitHub issues from priority P0.

Frequently Asked Questions about fix-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub issue resolution for high-priority bugs?

Automating GitHub issue resolution involves processing prioritized bugs serially using sub-agents. The system retrieves issues, executes code fixes, runs linting and unit tests, commits with references, and closes the resolved issues automatically.

What is the best way to fix GitHub issues sequentially without manual intervention?

Fixing GitHub issues sequentially requires a serial processing approach that handles one issue at a time to prevent parallel conflicts. Sub-agents execute the code fixes, type checking, and commits, pausing only for product clarification on complex functional changes.

Does automated bug fixing work with CI/CD pipelines and linting workflows?

Automated bug fixing integrates with CI/CD pipelines by enforcing code quality via linting, type checking, and unit testing. Sub-agents execute these validation steps before committing fixes and closing the referenced GitHub issues.

How are ambiguous functional changes handled during automated issue fixing?

Ambiguous functional changes during automated issue fixing trigger a request for product confirmation. The system pauses resolution to ask for clarification, ensuring complex bug fixes meet requirements before committing code.

Can I prioritize GitHub issues from P0 to P4 for automated code fixes?

Prioritizing GitHub issues from P0 to P4 for automated code fixes is supported natively. The system processes issues based on these predefined priority levels, starting with the highest priority bugs to clear the backlog efficiently.