om-verify-in-repo

Triage tracker issues read-only to decide whether an autofix chain should proceed.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/tkogut/agents-os-core --skill om-verify-in-repo-tkogut
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: om-verify-in-repo
Source: https://github.com/tkogut/agents-os-core/tree/main/global_skills/om-verify-in-repo
Command: npx skills add https://github.com/tkogut/agents-os-core --skill om-verify-in-repo-tkogut

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Autonomous autofix pipelines waste effort and create conflicts when they attempt to fix issues that are already resolved, already claimed by another agent, or not real bugs. This Skill acts as a read-only triage gate that stops the chain cleanly before any mutation happens. ## Core Features & Use Cases - Duplicate and shipped-fix detection: Searches open and closed PRs plus base-branch commit history for references to the issue, stopping the chain when a fix is already in flight or merged. - Claim and stale-lock awareness: Reads assignee, in-progress labels, and robot claim comments with tightened 30/60-minute windows to detect work owned by another actor without ever claiming anything itself. - Real-defect verification: Briefly inspects the affected code path to confirm the reported behavior is a genuine, still-unfixed bug rather than intended behavior or user error. - Use Case: A flow runner checks out a repo on an isolated branch for issue #1234; this Skill verifies no open PR references it, no one else holds a live claim, and the bug is real, then emits either a proceed verdict or the NO_ACTION_NEEDED stop token. ## Quick Start Run the om-verify-in-repo skill with issue number 1234 to check whether the autofix chain should proceed on this repository.

Frequently Asked Questions about om-verify-in-repo

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

FAQPage Schema
How do I verify a GitHub issue is still unfixed before autofixing it?▼

Search open and closed PRs for references to the issue number and grep the base branch commit history for the issue ID. If an open PR, merged PR, or commit already addresses it, stop the chain with a NO_ACTION_NEEDED verdict citing the link.

How does the skill detect that an issue is already in progress?▼

It checks three read-only signals: an in-progress label with assignees other than the current user, or a robot-prefixed claim comment newer than 30 minutes from another actor. Locks older than 60 minutes with no activity are treated as expired.

Can this skill claim, label, or comment on issues?▼

No. It is strictly read-only: no file edits, no commits, no label or assignment mutations, and no comments. Claiming happens later in the om-fix step of the autofix chain.

What happens when the issue turns out not to be a real bug?▼

The skill stops the chain with the NO_ACTION_NEEDED token when the behavior is documented or intentional, when the report reflects a usage or environment error, or when an existing test contradicts the report.

Does the triage gate require pipeline configuration to run?▼

Yes. It loads .ai/agentic.config.json and the tracker descriptor, running the om-setup-agent-pipeline skill if either is missing. The base branch comes from config and is never hard-coded.