refresh-issue

To sync Linear issues with code and documentation, you can use an automated workflow that examines current code, tests, and docs to verify implementation status. It aligns issue descriptions and acceptance criteria, then updates the issue with a structured review summary.

Checking if a Linear issue is fixed or obsolete involves examining relevant code files and documentation to determine implementation status. An automated verification process compares issue requirements against the latest codebase state to confirm relevance.

Aligning issue tracker descriptions with code state requires analyzing code files, tests, and documentation to determine current implementation status. Automated issue verification compares requirements against the latest documentation and updates the tracker with a structured review summary.

Linear issue tracking supports automated verification of acceptance criteria by examining code, tests, and documentation. This workflow determines if an issue is fixed, partially fixed, obsolete, or blocked, then updates issue status and comments with a structured review summary.

You need to refresh issue tracker data against the latest codebase when preparing to start work on a ticket. This ensures the ticket's description, acceptance criteria, and file references accurately reflect current code and documentation, preventing stale tasks and rework.

Linear issue descriptions fall out of sync with current code when the codebase and documentation evolve without updating the tracker. Automated issue verification examines code files and tests to detect this drift, then aligns descriptions and acceptance criteria with the actual implementation status.