agent-loop
Skill10 starsChanged 40 days agoMITView on GitHub
Use when the user says "loop", "반복", "쭉 돌려줘", or wants to run triage then resolve repeatedly until there are no agent-workable llmux issues/PRs left. Thin orchestrator over the agent-triage and agent-resolve skills; dry-run by default.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- Madheshvivekanandan/agent-looptheir own version, first seen Nov 8, 2026
- larchanka/skillstheir own version, first seen Nov 1, 2026
- nadavnaveh/skillstheir own version, first seen Oct 25, 2026
- Yuuqq/know-skillstheir own version, first seen Oct 20, 2026
- Artithea/agent-looptheir own version, first seen Oct 15, 2026
- leolin310148/tmacttheir own version, first seen Oct 13, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- joelhooks/joelclaw★ 65same name
- larchanka/skills★ 50same name
- leolin310148/tmact★ 4same name
- SiluPanda/codex-agent-loop★ 4same name
- nadavnaveh/skills★ 3same name
- Artithea/agent-loop★ 0same name
- edenbuilds/agentloop★ 0same name
- jaron-goh-centr/claude-skills★ 0same name
- Madheshvivekanandan/agent-loop★ 0same name
- Yuuqq/know-skills★ 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
- agent-resolveSkill
- agent-triageSkill
- buildSkill
- deploySkill
- releaseSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Mode: Default is DRY-RUN: run agent-triage's evaluation and print the resolve plan, change nothing.
- Very specific: line 33
Never re-triage an issue that already carries a needs-* / not-in-repo / agent-blocked label — a human must clear the label for it to …
“Common” is measured: kept by at least 6 in 10 of the 9 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
agent-loop — orchestrate triage → resolve until drained
agent-loop has no judgment of its own. It runs agent-triage once, then agent-resolve on the
resulting ready PRs one at a time, and stops on clear conditions. Labels are its memory — it
never re-evaluates issues already marked needs-* / not-in-repo / agent-blocked. Inherits
agent-resolve's boundary: it does not merge or 배포.
Steps
- Mode. Default is DRY-RUN: run agent-triage's evaluation and print the resolve plan, change
nothing. Act only if the user said "apply" / "실제로 해" / passed
--apply. - Run
agent-triageonce. (Labels issues, opens draft PRs for ready ones, skips already-labeled.) - Resolve. Over
ready-to-agentdraft PRs, oldest first, runagent-resolve— each in its own git worktree (per that skill), so resolves are isolated and may run in parallel. Verify each PR genuinely green (just check+ CI) independently before counting it done. Parallelize only across issues that touch disjoint modules; if their diffs would overlap, serialize them to avoid merge conflicts. - Stop when ANY:
- no
ready-to-agentdraft PRs remain (the user's "no issues/PRs left" condition), --max-iterationsreached (default 3),- 2 consecutive
agent-resolveruns end inagent-blocked, - an
agent-resolverun hit a kill-switch needing a human (needs-design/needs-human/ security / release).
- no
- Report a run summary: issues triaged (+ labels), PRs made review-ready, PRs blocked (+ why),
and exactly what is left for a human (review → merge →
deploy).
Anti-thrashing
Never re-triage an issue that already carries a needs-* / not-in-repo / agent-blocked label —
a human must clear the label for it to re-enter the pipeline. Without this, the same un-fixable issue
(e.g. the gpt-5.5 client-limitation one) gets re-evaluated to the same dead end every iteration.
Red flags — STOP
- Running in apply mode without explicit user opt-in.
- Re-triaging labeled issues (thrashing) — labels are memory.
- Merging or deploying —
agent-loopinheritsagent-resolve's human-gated boundary. - Running unbounded — always honor
--max-iterationsand the stop conditions.
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.

