ot-auto-fix-issue

Fixes or implements tracker issues end to end through chained bug-fix and feature-build workflows.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/triage-software/skills --skill ot-auto-fix-issue-triage-software
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ot-auto-fix-issue
Source: https://github.com/triage-software/skills/tree/main/skills/ot-auto-fix-issue
Command: npx skills add https://github.com/triage-software/skills --skill ot-auto-fix-issue-triage-software

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually driving a tracker issue from report to merged-ready PR requires many disconnected steps: verifying the bug, finding the root cause, writing the fix, opening the PR, reviewing it, and running UI QA. This Skill automates that entire pipeline from a single command, working in an isolated git worktree so your active checkout is never disturbed. ## Core Features & Use Cases - Dual-route execution: Classifies each issue as a bug or feature request, then drives the bug autofix chain (verify, root-cause, fix, open PR, auto-review, UI QA) or the feature route (spec writing, then spec implementation). - Brief mode: Accepts a plain problem description, files a well-formed tracker issue first via ot-prepare-issue, then continues on it automatically. - Concurrency-safe claim protocol: Uses a three-signal in-progress lock with stale-lock recovery, force overrides, and a continuous lock hand-off from issue to PR so work is never duplicated or left unclaimed. - Use Case: Run /ot-auto-fix-issue 1234 and the agent verifies the defect, isolates a worktree, implements a minimal fix with regression tests, opens a labeled PR, runs an automated review loop, and attaches UI evidence — reporting back with PR and issue reference lines. ## Quick Start Ask the agent to run ot-auto-fix-issue with an issue number like "fix issue 1234" or paste a plain problem description to have it filed and fixed automatically.

Frequently Asked Questions about ot-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?▼

Run ot-auto-fix-issue with the issue number, for example "fix issue 1234". The skill verifies the defect, finds the root cause, implements a fix with regression tests in an isolated worktree, opens a labeled PR, and runs an automated review loop.

Can I fix a bug from a plain problem description without filing an issue first?▼

Yes, brief mode accepts a free-form problem description instead of an issue id. The skill files a well-formed tracker issue via ot-prepare-issue first, then continues the normal fix chain on the filed issue.

Does ot-auto-fix-issue handle feature requests as well as bugs?▼

Yes, it classifies each issue label-first. Feature requests take a feature route that resolves or authors a spec via ot-auto-write-spec and then implements it with ot-auto-implement-spec, while bugs take the verify, root-cause, fix, and review chain.

What happens if someone else is already working on the issue?▼

A three-signal concurrency check (assignee, in-progress label, recent claim comment) detects existing ownership and stops the run, asking before overriding. The --force flag bypasses the stop but always posts an explicit override comment naming the previous owner.

Will ot-auto-fix-issue merge the PR or approve QA automatically?▼

No, the skill never merges PRs and never adds the qa-approved label. It leaves the PR in the review pipeline state, and the pipeline's separate review and QA gates own merge and QA approval decisions.

What are the limitations of the autonomous issue-fix workflow?▼

The run stops cleanly when triage finds no real defect, the feature is already built, or the ticket fails the Definition of Ready. It also requires the companion chain skills to be installed and a configured agentic.config.json; missing required skills halt the run.