mirror of https://github.com/davila7/claude-code-templates.git synced 2026-09-19 01:30:23 +08:00

Files

T

Daniel Avila 7f890b1b3b feat: add Loops component type with referenced components (#643 )

* 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>

2026-06-21 20:19:16 -04:00

2.0 KiB

Raw Permalink Blame History

name, description, category, interval, stop-condition, components, tags

name

description

Ticket-to-PR-Ready Loop

Loop Engineering — turn a backlog of issues into a steady stream of small, verified PRs without hand-holding each one.

🎯 Goal

Pick one actionable ticket, implement and verify the fix, and open a PR that a reviewer can approve quickly — then move to the next ticket.

⏱️ Schedule

Suggested interval: 30m.

▶️ Run it

/loop 30m "Take the next actionable open issue. Implement the fix in an isolated branch, add tests, verify, and open a conventional-commit PR linking the issue. If a ticket needs product decisions, label it for human review and skip. Continue until the queue is clear."

🔁 Iteration steps

Perceive — read the next open, actionable issue.
Reason — confirm scope; if it needs human/product input, label and skip.
Plan — outline the change and the test that proves it.
Act — implement with /fix-github-issue; commits follow conventional-commits.
Observe — run tests; on green, open a PR with /create-pr that links the issue.

🛑 Stopping condition

No actionable tickets remain — each is either a verified PR or flagged for human input.

🧩 Referenced components

command:git-workflow/fix-github-issue — implements the ticket fix.
command:git-workflow/create-pr — opens the linked PR.
hook:git/conventional-commits — enforces clean, conventional commit messages.

💡 Example

A "typo in error message" issue becomes a one-line fix with a snapshot test and a fix: correct auth error copy (#412) PR, all within a single pass.

2.0 KiB Raw Permalink Blame History