What problem does it solve? Manually driving a tracker issue from report to merged-quality PR involves many repetitive steps: verifying the bug, isolating a worktree, finding the root cause, implementing the fix, opening a PR, running review loops, and checking UI changes. This Skill orchestrates that entire chain autonomously from a single command, with claim locking so concurrent agents never collide. ## Core Features & Use Cases - Dual routing: Classifies each issue as a bug or feature request, then drives either the bug autofix chain (verify, root-cause, fix, open PR, review, UI QA) or the feature route (spec authoring then implementation). - Brief mode: Accepts a plain problem description, files a well-formed issue first via om-prepare-issue, then continues on it. - Concurrency-safe claims: Three-signal in-progress checks, stale-lock recovery, and a continuous lock handed off from issue to PR so work is never duplicated or left unclaimed. - Isolated worktrees: All changes happen in a temporary git worktree off the base branch, never disturbing the user's active checkout. - Use Case: Run it with "fix issue 1234" and it verifies the defect, implements a minimal fix with regression tests, opens a labeled PR, runs an automated review loop, and reports the PR link. ## Quick Start Ask the agent to fix issue 1234 end to end, or paste a plain problem description and let it file and resolve the issue automatically.
