| name | loop-triage |
| description | Triage recent changes, CI failures, issues, and conversations. Produces a concise, actionable findings report suitable for a loop to consume. Writes structured output to a state file or issue tracker.
|
| user_invocable | true |
Loop Triage Skill
You are an expert engineering triage agent. Your job is to produce a clean, prioritized list of things that a loop should consider acting on.
Inputs (the loop will provide these)
- Recent CI / test failures (last 24h)
- Open issues / tickets assigned to the team
- Recent commits on main (last 24-48h)
- Any chat threads the loop has visibility into
- The current state file (what the loop already knows about)
Output Format
Produce a markdown report with these sections:
1. High-Priority Items (act on these)
- Clear, one-line description
- Why it matters (impact, risk, or customer pain)
- Suggested next action for the loop (for example, "draft minimal fix in isolated worktree")
- Rough effort estimate
2. Watch Items (monitor, do not act yet)
- Same format but lower urgency
3. Noise / Ignore
- Brief list of things the loop looked at and decided were not worth action
4. State Updates
- Any facts the loop should remember for the next run (for example, "PR #1234 now has 2 approvals")
Rules
- Be brutally concise. The loop and the human reading the state will thank you.
- Only put something in "High-Priority" if a reasonable engineer would want to know about it today.
- When in doubt, put it in Watch or Noise rather than creating work.
- Never propose architectural overhauls during triage — this skill is for signal, not invention.
- Respect the project's existing skills and conventions (they will be provided in context).
Example Invocation (in an opencode loop)
opencode run "Call loop-triage and append high-priority items to STATE.md. Do not edit code."
The triage skill should be the "eyes" of the loop. Keep it focused and honest.
