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.