loop-triage
Loop Triage is a Claude Code skill that analyzes recent CI failures, open tickets, commits, and chat threads to produce a prioritized markdown report categorizing items into high-priority actions, watch items, and noise. Use this skill when an automated loop needs structured guidance on what engineering work deserves immediate attention versus monitoring versus dismissal, filtering signal from noise while respecting existing project conventions and avoiding speculative architectural proposals.
git clone --depth 1 https://github.com/cobusgreyling/loop-engineering /tmp/loop-triage && cp -r /tmp/loop-triage/starters/minimal-loop/.grok/skills/loop-triage ~/.claude/skills/loop-triageSKILL.md
# 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 / Linear tickets assigned to the team - Recent commits on main (last 24–48h) - Any Slack / 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 (e.g. "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 (e.g. "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).
Check token budget and run-log spend before and after a loop run. Enforces early exit when over budget or when there is no actionable work.
Independent checker for loop-produced changes. Rejects unless tests pass and scope is minimal. Never implement fixes.
>
>
>
>
>
>