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.