loop-triage
Skill57 starsChanged 14 days agoMITView on GitHub
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.
9 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- AdriDob/OWNEXtheir own version, first seen Nov 1, 2026
- SUDARSHANCHAUDHARI/MyLooptheir own version, first seen Nov 1, 2026
- ayeshakhalid13/LoopEngineering-CrashCourseedited, first seen Oct 15, 2026
- rossinsilico/loop-anythingtheir own version, first seen Oct 11, 2026
- cobusgreyling/loop-engineeringedited, first seen Aug 13, 2026
- ayeshakhalid192007-dev/LoopEngineering-CrashCourseedited, first seen Jul 16, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 3
- cobusgreyling/loop-engineering★ 12k42% same
- ayeshakhalid13/LoopEngineering-CrashCourse★ 1689% same
- ayeshakhalid192007-dev/LoopEngineering-CrashCourse★ 1589% same
Wrote their own version · 6
- aiconnai/agentshield★ 21same name
- aiconnai/engram★ 3same name
- SUDARSHANCHAUDHARI/MyLoop★ 2same name
- AdriDob/OWNEX★ 1same name
- ba0918/claude-skills★ 0same name
- rossinsilico/loop-anything★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/ibex-harness.mdcCursor rule
- loop-budgetSkill
- loop-constraintsSkill
- loop-verifierSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 49
Only put something in "High-Priority" if a reasonable engineer would want to know about it today.
- Distinctive: line 50
When in doubt, put it in Watch or Noise rather than creating work.
- Distinctive: line 51
Never propose architectural overhauls during triage — this skill is for signal, not invention.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.