mirror of
https://github.com/davila7/claude-code-templates.git
synced 2026-09-19 01:30:23 +08:00
Daniel Avila
7f890b1b3b
* feat: add Loops component type with referenced components Introduce "loops" as a new first-class component type — autonomous agentic workflows (goal + interval + stop condition) inspired by Loop Engineering and the Forward Future Loop Library. A loop references other components (agents, skills, hooks, commands) and the dashboard renders those references as clickable cards on the loop detail page. - Add 10 starter loops under cli-tool/components/loops/ (engineering, evaluation, operations) - Catalog generator: scan loops + write per-component content files - Dashboard: new type in icons/types/data, /loops page, and a "Referenced Components" section on the loop detail page - CLI: --loop flag installs the loop to .claude/loops/ and auto-installs its referenced components - Docs: CLAUDE.md and cli-tool rule updated Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T9ynMiCHt8JwdMd8KjCkES * feat: add 8 more loops (goal/loop/schedule patterns) Expand the loops catalog to 18, drawing ideas from community "Loop Engineering" patterns. Adds loops across the three trigger verbs (/goal, /loop, /schedule) and emphasizes the verifier-in-the-loop and budget / anti-spin guardrails: - engineering/five-minute-maintainer-loop - engineering/build-test-fix-loop - engineering/anti-spin-build-loop - engineering/completion-contract-loop (goal) - engineering/goal-refiner-loop (goal) - engineering/adversarial-review-loop (cross-model) - operations/overnight-pr-routine-loop (schedule) - evaluation/human-approval-loop (human-in-the-loop) All referenced components verified to exist; catalog regenerated. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T9ynMiCHt8JwdMd8KjCkES --------- Co-authored-by: Claude <noreply@anthropic.com>
2.1 KiB
2.1 KiB
name, description, category, interval, stop-condition, components, tags
| name | description | category | interval | stop-condition | components | tags | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| production-error-sweep-loop | Triages production errors, finds the root cause, ships a verified fix, and repeats until the error budget is clean. | engineering | 15m | No unresolved high-severity production errors remain and each fix is verified in tests. |
|
|
Production Error Sweep Loop
Loop Engineering — keep an autonomous responder working the error queue, one root cause at a time, until production is quiet.
🎯 Goal
Continuously pull the top production error, find its root cause (not just the symptom), ship a tested fix, and verify the error stops recurring.
⏱️ Schedule
Suggested interval: 15m (or trigger on new error alerts).
▶️ Run it
/loop 15m "Take the highest-impact unresolved production error. Reproduce it, find the root cause, write a regression test, fix it, and open a PR. Continue until no high-severity errors remain."
🔁 Iteration steps
- Perceive — read the top error by impact (frequency × severity).
- Reason — reproduce and trace to the true root cause with the
debugagent. - Plan — design a minimal fix plus a regression test that fails first.
- Act — implement the fix; the
incident-responderagent documents impact and mitigation. - Observe — confirm the regression test passes, then open a PR with
/create-pr.
🛑 Stopping condition
The high-severity error queue is empty and every fix is covered by a passing regression test.
🧩 Referenced components
agent:expert-advisors/debug— root-cause analysis.agent:security/incident-responder— impact assessment and mitigation notes.command:git-workflow/create-pr— ships each fix for review.
💡 Example
A recurring null-pointer crash is traced to an unvalidated webhook payload; the loop adds a failing regression test, fixes the validation, verifies, and opens fix: validate webhook payload before parse.