organize-linear-tasks

Linear backlog audits detect ghost tasks by cross-referencing recent git activity against open issues, then offers to mark code-completed items as Done. It also flags stale tickets with no recent activity for removal or metadata correction.

A Linear backlog audit surfaces likely duplicate issues for merge or relate decisions and flags unclear tasks needing rewritten titles or descriptions. Interactive approvals are required per cleanup stage before applying deletions or updates via GraphQL.

Yes, Linear task triage supports resumable sectioning, allowing you to resume progress by specifying a section argument. This enables weekly maintenance across Todo, In Progress, Backlog, In Review, and Done states.

Yes, auditing Linear issues requires curl, git, and python3 dependencies. The audit uses git for cross-referencing commit history and python3 for processing batch data gathered from Linear MCP tools to detect ghost tasks and staleness.

Completed tasks remain open in Linear when ghost tasks appear done in code commits but lack corresponding status updates. The audit detects these by cross-referencing recent git activity and offers to mark them Done through GraphQL mutations.