What problem does it solve?
Teams often mark Linear issues complete based only on local edits, creating a gap between issue status and actual delivery. This Skill keeps issue tracking honest by verifying implementation evidence, code review state, and deployment before any status change.
Core Features & Use Cases
- Evidence-Based Status Updates: Reads the issue, linked work, and acceptance criteria, then compares them against actual implementation evidence before editing anything.
- Gap Reporting: Reports discrepancies between the issue description and the real change before modifying either side.
- Delivery Stage Distinction: Distinguishes local implementation, pushed code, merged code, and deployed behavior to prevent premature completion claims.
- Use Case: An engineer finishes a feature branch and asks to close the Linear issue. The Skill checks whether the pull request is merged and deployed, preserves links to the PR and tests, and only updates the issue status when the requested milestone is genuinely reached.
Quick Start
Ask the assistant to review Linear issue ENG-123 against the current pull request and update its status only if the acceptance criteria are actually met.