om-verify-in-repo

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

2.6k|159|Updated Mar 8, 2021
One-click install
npx skills add https://github.com/go-musicfox/go-musicfox --skill om-verify-in-repo-go-musicfox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: om-verify-in-repo
Source: https://github.com/go-musicfox/go-musicfox/tree/main/.agents/skills/om-verify-in-repo
Command: npx skills add https://github.com/go-musicfox/go-musicfox --skill om-verify-in-repo-go-musicfox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Autonomous issue-fixing pipelines waste effort and create conflicts when they act on issues that are already fixed, already claimed by another agent, already covered by an open PR, or not actually bugs. This Skill acts as a read-only triage gate that stops the chain cleanly before any code changes happen. ## 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 assignees, in-progress labels, and robot claim comments to detect work owned by another actor, with tightened 30/60-minute stale-lock windows so expired locks never block progress. - Real-bug validation: Briefly inspects the affected code path to confirm the reported behavior is a genuine, still-unfixed defect rather than documented behavior or user error. - Use Case: A flow runner checks out a repo on an isolated branch for GitHub issue #1234; this Skill verifies the issue is open, unclaimed, and unfixed, then either emits NO_ACTION_NEEDED with evidence or green-lights the root-cause step. ## Quick Start Ask the agent to verify whether GitHub issue 1234 in the current repository is a real, still-unfixed defect before starting the autofix chain.

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 check if a GitHub issue is already fixed 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 a merged PR or commit already addresses it, stop the chain with a NO_ACTION_NEEDED verdict citing the link or hash.

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

Check three signals: assignees other than the current user, an in-progress label, and a recent robot-prefixed claim comment. This Skill treats labels older than 60 minutes without activity as stale and ignores them.

Does this triage step modify issues, labels, or code?

No, it is strictly read-only. It only reads files, runs read-only git commands, and calls read-only tracker operations; claiming, labeling, branching, and committing all happen in later chain steps like om-fix.

What happens when the verification step decides no action is needed?

It outputs the literal token NO_ACTION_NEEDED on its own line followed by a short evidence paragraph citing commits, PRs, or files. The flow runner reads that token and stops the chain cleanly without running later steps.

When should issue triage stop an autofix chain?

Stop when the issue is closed, already fixed by a merged PR or commit, covered by an open PR, claimed by another actor with a live lock, or when the reported behavior is documented, intentional, or a usage error rather than a real bug.