linear-maintenance

Audits and cleans a Linear backlog by applying verifiable fixes and surfacing open decisions.

1.8k|61|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/HugoRCD/evlog --skill linear-maintenance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: linear-maintenance
Source: https://github.com/HugoRCD/evlog/tree/main/apps/evi/agent/skills/linear-maintenance
Command: npx skills add https://github.com/HugoRCD/evlog --skill linear-maintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about linear-maintenance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clean up a messy Linear backlog automatically?▼

Run a structured maintenance pass that lists all open issues, checks each against lenses like project, label, priority, and staleness, then applies unambiguous fixes directly. Anything requiring a judgement call is reported as a finding with supporting evidence instead of being guessed.

How to find Linear issues that are done but still open?▼

Check each open issue against its history, linked pull requests, and live schedules to verify the work already shipped. Only close the issue when that evidence is verifiable; otherwise record it as an open question rather than closing unilaterally.

What Linear API tools does this maintenance workflow use?▼

It uses linear__list_issues to enumerate the team's open surface across states and linear__save_issue to apply verified fixes. Absence of a label, project, or priority is always proven by listing, never by recall.

Can the skill close stale triage issues on its own?▼

No. Stale triage items, possible duplicates, and anything whose correct value is a matter of intent are surfaced as findings with evidence and the exact decision to make. Only mechanically verifiable fixes are applied directly.

What happens when a maintenance pass finds nothing wrong?▼

A quiet pass is reported as a real result with a single line saying so. The skill never invents fixes to fill a run and never reports a lens as clean without actually checking it.