What problem does it solve?
Linear backlogs drift over time: issues lose labels, sit in the wrong project, carry inconsistent priorities, or stay open after their work already shipped. This Skill runs a structured housekeeping pass over the evlog team's Linear backlog so it stays readable and trustworthy without manual triage effort.
Core Features & Use Cases
- Mechanical fixes applied directly: Corrects missing projects, labels, and inconsistent priorities via
linear__save_issue when sibling issues or issue history provide unambiguous evidence.
- Decision surfacing: Items requiring judgement (stale triage, possible duplicates, shipped-but-open work without verifiable proof) are written up as findings with evidence and the exact question to resolve.
- Grounded verification: Enumerates the real issue surface with
linear__list_issues before claiming anything is missing, and requires linked PRs, schedules, or issue history before closing shipped work.
- Use Case: On a bi-weekly schedule, run a backlog pass that fixes a feature request missing its label, closes an issue whose work shipped in a merged PR, and reports three stale triage items for Hugo to decide on.
Quick Start
Run a Linear maintenance pass over the evlog team backlog and report the applied fixes and open decisions.