Housekeeping

Housekeeping

Scope

Review live work queues and recommend what the engineer should do next. Triage is a recommendation, not an action: every state change this skill produces — assigning, moving, closing, cancelling, re-prioritising — belongs to the engineer, so the output is a table they act on.

Use this skill for:

• Linear issue triage, assigned work, waiting issues, urgent-priority issues, and stale cleanup candidates.
• Pylon customer issues that need an engineer response, engineering follow-up, linked-ticket check, or stale close recommendation.
• GitHub pull requests where the engineer is a direct or team reviewer.

Do not use this skill for deep root-cause debugging, implementation, incident response, or broad roadmap planning unless the user explicitly asks to continue from a recommendation into that work.

Required Behavior

Every reviewed item must include an action recommendation. If evidence is insufficient, recommend the next inspection step rather than leaving the action blank.

Use these action labels:

• act-now: needs attention today.
• quick-win: likely under 15 minutes.
• todo: should be picked up in the next 1-2 weeks.
• backlog: real but can wait months.
• waiting: next move is outside the engineer or team.
• stale-candidate: likely safe to close or cancel, but needs human confirmation.
• no-action: no current action beyond monitoring; explain why.

Include confidence for each recommendation: high, medium, low, or unknown.

Workflow

1. Identify the current engineer in each system from the available connector, CLI, or authenticated API context. If identity cannot be determined for a system, say so and continue with the other systems.
2. Gather live data before recommending action. Do not rely on memory for current queues.
3. Inspect comments, latest activity, linked issues, checks, and review threads when status or ownership is ambiguous.
4. Cluster duplicates or related items before prioritizing.
5. Return recommendations ordered by urgency, then quick wins, then cleanup.
6. Present the recommendations as a decision table for the engineer to act on. Every action this skill recommends is a state change reserved for a human, so do not perform them. If a queue item needs a note left on it for someone else, that is a comment or a description edit — propose it, get a yes, then write; see linear-agent-writes.

Linear Review