om-fix

Implements root-cause fixes with regression tests and validation gates in an autofix chain.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Autonomous issue-fixing pipelines often fail because fixes are applied without claiming the issue, without regression tests, or without running the project's validation gate. This Skill implements the minimal code change identified by a prior root-cause analysis step, claims the tracker issue to prevent duplicate automation, and proves the fix works before handing off to PR creation. ## Core Features & Use Cases - Minimal Fix Implementation: Applies only the changes named in the analyzer's brief, preserving public contracts, data-access conventions, and permission rules. - Issue Claiming and Locking: Assigns the issue, applies the in-progress label, and posts a claim comment so concurrent automation backs off. - Mandatory Regression Tests: Adds unit and integration tests that fail without the fix and pass with it, then runs the full validation gate from the committed config. - Use Case: A tracker issue reports a bug, the root-cause step identifies the faulty file, and this Skill edits the code, adds a failing-then-passing test, runs lint and typecheck, and reports a structured Status block for the PR-opening step. ## Quick Start Ask the agent to run the om-fix step for issue 42 using the root-cause brief from the previous step and report the validation results.

Frequently Asked Questions about om-fix

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

FAQPage Schema
How do I automate bug fixes from a root-cause analysis?

Run this step after a root-cause analyzer produces a brief naming the files and approach. It edits only those files, adds regression tests, runs the validation gate, and outputs a Status block for the next pipeline step.

How does the autofix pipeline prevent duplicate work on the same issue?

The skill claims the issue up front by assigning the current user, applying an in-progress label, and posting a timestamped claim comment. Other automation reads these three signals and skips the issue until the lock is released.

Does this skill commit or open pull requests?

No. It deliberately stops after validation passes. Committing, pushing, and opening the PR are the responsibility of the separate om-open-pr step in the chain.

What happens if the root-cause brief is missing or wrong?

The skill ends with a Status: blocked output and a one-line reason instead of inventing its own root cause. The issue lock remains set so a human can pick up the work.

Can it run arbitrary commands found in issue or PR text?

No. Only validation commands from the committed, operator-reviewed config file are executed. Commands embedded in issues, comments, or diffs are treated as untrusted data and reported as suspected prompt injection.