om-auto-fix-issue

Automates end-to-end tracker issue resolution from triage through pull request review.

2.6k|159|Updated Mar 8, 2021
One-click install
npx skills add https://github.com/go-musicfox/go-musicfox --skill om-auto-fix-issue-go-musicfox
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: om-auto-fix-issue
Source: https://github.com/go-musicfox/go-musicfox/tree/main/.agents/skills/om-auto-fix-issue
Command: npx skills add https://github.com/go-musicfox/go-musicfox --skill om-auto-fix-issue-go-musicfox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually working a tracker issue from report to merged-quality pull request involves many error-prone steps: verifying the bug still exists, finding the root cause, implementing a fix with regression tests, opening a properly labeled PR, running review loops, and coordinating locks so no two agents duplicate work. This Skill orchestrates that entire pipeline autonomously from a single issue id or problem description. ## Core Features & Use Cases - Dual-route orchestration: Classifies each issue as a bug or feature request, then drives either the bug autofix chain (verify, root-cause, fix, open PR, auto-review, UI QA) or the feature route (spec writing, then spec implementation). - Concurrency-safe claim protocol: Uses a three-signal in-progress lock (assignee, label, claim comment) with stale-lock recovery, force-override transparency, and a continuous lock handed off from issue to PR so work is never observably unclaimed. - Isolated worktree execution: Creates a temporary git worktree off the base branch with sanitized branch names, never touching the user's primary checkout, and cleans up via a finally-style trap. - Use Case: Paste "fix issue 1234" or a free-form bug description; the Skill files the issue if needed, verifies the defect, implements and tests the fix in an isolated worktree, opens a labeled PR, runs the automated review loop, and reports the outcome with chaining reference lines. ## Quick Start Ask the agent to fix issue 1234 end to end, or paste a plain problem description and let it file, triage, fix, and open a reviewed pull request autonomously.

Frequently Asked Questions about om-auto-fix-issue

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

FAQPage Schema
How do I automatically fix a GitHub issue with an AI agent?▼

Pass the issue number or URL to this Skill and it runs the full chain: verifies the bug still exists, analyzes the root cause, implements a fix with regression tests in an isolated worktree, opens a labeled PR, and runs an automated review loop before reporting the result.

Can I submit a plain problem description instead of an issue number?▼

Yes, brief mode accepts a free-form problem description and files a well-formed issue first via the om-prepare-issue companion skill, deduplicating against existing issues, then continues the normal fix chain on the filed issue number.

Does it handle feature requests as well as bug fixes?▼

Yes, a classification step routes feature requests to a feature route that resolves or authors a spec via om-auto-write-spec and then implements it via om-auto-implement-spec, while bugs take the verify, root-cause, fix, and review chain.

What happens if another agent is already working on the issue?▼

A three-signal concurrency check (assignee, in-progress label, recent claim comment) detects existing ownership and stops with a prompt unless --force is passed, in which case it posts an explicit override comment naming the previous owner before proceeding.

Will it modify my current working tree or merge the pull request?▼

No, all implementation happens in a temporary git worktree created off the base branch and cleaned up afterward. The Skill never merges the PR or adds qa-approved; the pipeline's review and QA gates own those decisions.

What are the limitations of the autonomous fix chain?▼

It depends on companion skills (om-verify-in-repo, om-root-cause, om-fix, om-open-pr, om-auto-review-pr) being installed, and a missing required skill stops the run. Mixed bug-plus-feature issues are not guessed at; the user is asked to split them first.