ot-verify-in-repo

Verifies whether a GitHub issue is a real, unfixed defect before an autofix chain proceeds.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Autonomous bug-fixing pipelines waste effort and create duplicate work when they attempt to fix issues that are already resolved, already claimed by another contributor, already covered by an open pull request, or not actually bugs. This Skill acts as a read-only triage gate that stops the chain early in those cases. ## Core Features & Use Cases - Duplicate and in-flight detection: Searches open and closed PRs plus base-branch commit history for references to the issue, stopping the chain when a fix already exists. - Claim and lock awareness: Reads assignees, in-progress labels, and robot claim comments (with stale-lock windows) to avoid colliding with work owned by another actor. - Bug validity check: Briefly inspects the affected code path or tests to confirm the reported behavior is a genuine defect rather than intended behavior or a usage error. - Use Case: A flow runner checks out a repo on an isolated branch for issue #1234; this Skill fetches the issue, finds an open PR already referencing it, and emits the NO_ACTION_NEEDED token so no later fix steps run. ## Quick Start Run the ot-verify-in-repo skill with issue number 1234 to decide whether the autofix chain should proceed or stop.

Frequently Asked Questions about ot-verify-in-repo

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

FAQPage Schema
How do I check if a GitHub issue is already fixed before autofixing it?▼

Run this triage gate with the issue number; it searches open and closed PRs for references to the issue and greps the base branch commit history. If a fix is already in flight or merged, it stops the chain with NO_ACTION_NEEDED and cites the evidence.

How to detect if another agent is already working on a GitHub issue?▼

The skill checks three signals: assignees other than the current user, an in-progress label, and recent robot-prefixed claim comments. Locks older than 60 minutes with no activity are treated as stale and do not block the chain.

Does this skill modify the repository or the issue?▼

No, it is strictly read-only. It performs only file reading, code search, read-only git commands, and read-only tracker operations; claiming, labeling, branching, and committing all happen in later chain steps.

What happens when the issue is not actually a bug?▼

The skill briefly inspects the affected code path or tests, and if the behavior is documented, intentional, or a reporter-side usage error, it outputs NO_ACTION_NEEDED with a short evidence-backed explanation.

What configuration does the verify step need before running?▼

It loads .ai/agentic.config.json and the tracker descriptor generated by the ot-setup-agent-pipeline skill, resolving the base branch from config. If either file is missing, setup runs first before triage continues.