@cobusgreyling/loop-init 1.1.0

package/starters/pr-babysitter/.codex/skills/pr-review-triage/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: pr-review-triage
+description: >
+  Triage open pull requests for CI status, review comments, and merge readiness.
+  Use in PR babysitter loops. Respects project review norms and required checks.
+user_invocable: true
+---
+
+# PR Review Triage Skill
+
+For each watched PR, report:
+
+## Per-PR Output
+
+```markdown
+### PR #N — title
+- CI: green | red (job names if red)
+- Reviews: approved N | changes requested | none
+- Blocking comments: (list actionable ones)
+- Ready to merge: yes | no — reason
+- Suggested loop action: none | minimal-fix | rebase | escalate-human
+```
+
+## Rules
+
+- "Ready to merge" requires all required checks + approvals per project policy.
+- Non-actionable nits → note but do not spawn fix.
+- If PR idle >4 days → suggest human handoff.
+- High-risk labels (security, breaking) → escalate-human always.

package/starters/pr-babysitter/.grok/skills/pr-review-triage/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: pr-review-triage
+description: >
+  Triage open pull requests for CI status, review comments, and merge readiness.
+  Use in PR babysitter loops. Respects project review norms and required checks.
+user_invocable: true
+---
+
+# PR Review Triage Skill
+
+For each watched PR, report:
+
+## Per-PR Output
+
+```markdown
+### PR #N — title
+- CI: green | red (job names if red)
+- Reviews: approved N | changes requested | none
+- Blocking comments: (list actionable ones)
+- Ready to merge: yes | no — reason
+- Suggested loop action: none | minimal-fix | rebase | escalate-human
+```
+
+## Rules
+
+- "Ready to merge" requires all required checks + approvals per project policy.
+- Non-actionable nits → note but do not spawn fix.
+- If PR idle >4 days → suggest human handoff.
+- High-risk labels (security, breaking) → escalate-human always.

package/starters/pr-babysitter/LOOP.md

@@ -0,0 +1,20 @@
+# Loop Configuration — PR Babysitter
+
+| Pattern | Cadence | Status |
+|---------|---------|--------|
+| PR Babysitter | 5m (work hours) | L2 assisted |
+
+## Limits
+
+- Max fix attempts per PR: 3
+- Auto-merge: **disabled**
+- Watched: PRs authored by team / label `loop-watch`
+
+## Human Gates
+
+- Security, auth, payments, infrastructure
+- PRs with >10 files changed in loop fix
+
+## Pattern
+
+[pr-babysitter.md](../../patterns/pr-babysitter.md)

package/starters/pr-babysitter/README.md

@@ -0,0 +1,36 @@
+# PR Babysitter Starter
+
+Scaffold for the [PR Babysitter](../../patterns/pr-babysitter.md) loop (L2 — assisted fixes with verifier).
+
+## Quick Start
+
+1. Copy into your repo:
+   ```bash
+   npx @cobusgreyling/loop-init . --pattern pr-babysitter --tool grok
+   # Or manual:
+   cp -r starters/pr-babysitter/.grok/skills/* .grok/skills/
+   cp starters/pr-babysitter/pr-babysitter-state.md.example pr-babysitter-state.md
+   cp starters/pr-babysitter/LOOP.md .
+   ```
+
+2. Customize skills with your review norms and required checks.
+
+3. Start (Grok):
+   ```bash
+   /loop 5m Check open PRs. Update pr-babysitter-state.md. For CI failures or actionable review comments on allowlisted PRs: worktree + minimal-fix + loop-verifier. Never merge — propose only. Escalate after 3 attempts per PR.
+   ```
+
+4. Sign PR comments: `🤖 Loop Engineering — PR Babysitter`
+
+## Files
+
+| File | Purpose |
+|------|---------|
+| `pr-babysitter-state.md.example` | Watcher state |
+| `.grok/skills/pr-review-triage/` | PR triage skill |
+| `LOOP.md` | Team loop config |
+
+## Safety
+
+- No auto-merge by default
+- Denylist: auth, payments, secrets — see [safety.md](../../docs/safety.md)

package/starters/pr-babysitter/pr-babysitter-state.md.example

@@ -0,0 +1,19 @@
+# PR Babysitter State
+
+Last run: never
+
+## Watched PRs
+
+<!-- - #1234 (branch-name)
+  Status: CI red | changes requested | ready
+  Attempts: 0/3
+  Last action: —
+  Human decision: —
+-->
+
+## Escalated (human required)
+
+## Resolved (last 7d)
+
+---
+Run log: —

package/templates/SKILL.md.loop-triage

@@ -0,0 +1,54 @@
+---
+name: loop-triage
+description: >
+  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 Linear board.
+user_invocable: true
+---
+
+# 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).
+
+## Example Invocation (in a Grok loop)
+
+```
+/loop 30m Call $loop-triage and append the high-priority items to STATE.md. For any high-priority item that looks like a small bugfix, open a worktree and spawn a minimal-fix sub-agent.
+```
+
+The triage skill should be the "eyes" of the loop. Keep it focused and honest.

package/templates/SKILL.md.minimal-fix

@@ -0,0 +1,45 @@
+---
+name: minimal-fix
+description: >
+  Produce the smallest possible code change that fixes a specific, well-scoped
+  issue (CI failure, reviewer comment, typo). Use only when the fix target is
+  explicit. Never refactor unrelated code.
+user_invocable: true
+---
+
+# Minimal Fix Skill
+
+You fix **one specific problem** with the **smallest diff** that could work.
+
+## Inputs
+
+- Exact failure message, reviewer comment, or issue description
+- File(s) implicated (if known)
+- Project build/test commands (from AGENTS.md or project skills)
+- Path denylist (from loop safety policy — never edit `.env`, `auth/`, `payments/`, secrets)
+
+## Process
+
+1. Reproduce or confirm the failure locally if possible.
+2. Identify the minimal root cause — not symptoms in distant files.
+3. Change only what is required. No drive-by refactors.
+4. Run tests/lint relevant to the change.
+5. Summarize: what changed, why, what you ran.
+
+## Output
+
+```markdown
+## Minimal Fix Proposal
+- Target: (issue/comment/failure)
+- Files changed: (list)
+- Diff summary: (1-3 bullets)
+- Tests run: (commands + result)
+- Risk: low | medium — if medium, recommend human review
+```
+
+## Rules
+
+- If fix requires >5 files or design change → stop and escalate.
+- If path is on denylist → stop and escalate.
+- Do not disable tests or weaken assertions to go green.
+- Do not mark yourself "done" — verifier decides.

package/templates/SKILL.md.verifier

@@ -0,0 +1,48 @@
+---
+name: loop-verifier
+description: >
+  Independent verification agent for loop-produced changes. Finds reasons to
+  reject. Runs tests. Confirms diff scope. Use after minimal-fix or any
+  implementer sub-agent — never in the same role as the implementer.
+user_invocable: true
+---
+
+# Loop Verifier Skill
+
+You are the **checker** in a maker/checker split. Your job is to **reject** unless evidence is strong.
+
+## Inputs
+
+- Implementer's proposal summary and diff
+- Original issue / CI failure / comment being addressed
+- Project test/lint commands
+- Allowed file scope (if specified by the loop)
+
+## Checklist (all must pass for APPROVE)
+
+1. **Scope**: Only relevant files changed; no denylist paths; no unrelated edits.
+2. **Intent**: Change clearly addresses the stated target — not a different problem.
+3. **Tests**: You ran tests (or equivalent) and report pass/fail with output snippet.
+4. **No cheating**: No disabled tests, skipped assertions, or commented-out checks.
+5. **Risk**: For medium+ risk, recommend human review even if tests pass.
+
+## Output
+
+```markdown
+## Verdict: APPROVE | REJECT | ESCALATE_HUMAN
+
+### Evidence
+- Tests: (command + result)
+- Scope check: (pass/fail + notes)
+
+### If REJECT
+- Reasons: (numbered, specific)
+- Suggested next step for implementer
+```
+
+## Rules
+
+- Default stance: REJECT until proven otherwise.
+- Do not trust implementer's claim that tests passed — run them.
+- If you cannot run tests (env issue) → ESCALATE_HUMAN.
+- Be concise. The loop and human read this under time pressure.

package/templates/STATE.md.template

@@ -0,0 +1,22 @@
+# Loop State — {{PROJECT_NAME}}
+
+Last run: (set by loop on each run)
+
+## High Priority (loop is acting or waiting on human)
+
+<!-- Format:
+- [ ] ID — one-line description
+  Loop action: what the loop did last
+  Human decision: (if any)
+-->
+
+## Watch List
+
+<!-- Items to monitor but not act on yet -->
+
+## Recent Noise (ignored this run)
+
+<!-- Brief list — helps tune triage skill -->
+
+---
+Run log: (timestamp) | findings | actions | escalations

package/templates/loop-budget.md.template

@@ -0,0 +1,22 @@
+# Loop Budget — YOUR_PROJECT
+
+## Daily limits
+
+| Loop | Max runs/day | Max tokens/day | Max sub-agent spawns/run |
+|------|--------------|----------------|--------------------------|
+| Daily Triage | 2 | 100k | 0 (L1) / 2 (L2) |
+| PR Babysitter | 288 | 2M | 3 |
+| CI Sweeper | 96 | 1M | 3 |
+| Dependency Sweeper | 4 | 500k | 3 |
+| Post-Merge Cleanup | 1 | 200k | 2 |
+
+## On budget exceed
+
+1. Pause all schedulers (`scheduler_delete` or disable automations)
+2. Append event to `loop-run-log.md`
+3. Notify human (Slack / issue / STATE.md High Priority)
+
+## Kill switch
+
+- Command or issue label: `loop-pause-all`
+- Resume only after human clears the flag in STATE.md

package/templates/loop-run-log.md.template

@@ -0,0 +1,22 @@
+# Loop Run Log — YOUR_PROJECT
+
+Append one entry per run. Prune entries older than 30 days.
+
+## Format
+
+```json
+{
+  "run_id": "2026-06-09T08:15:00Z",
+  "pattern": "daily-triage",
+  "duration_s": 45,
+  "items_found": 4,
+  "actions_taken": 1,
+  "escalations": 0,
+  "tokens_estimate": 52000,
+  "outcome": "report-only | fix-proposed | escalated | no-op"
+}
+```
+
+## Recent Runs
+
+<!-- Loop appends below this line -->

package/templates/pattern-template.md

@@ -0,0 +1,58 @@
+# {{PATTERN_NAME}} Loop
+
+**Goal**: {{ONE_SENTENCE_GOAL}}
+
+## Scheduling
+
+**Recommended**:
+- Grok: `{{GROK_COMMAND}}`
+- Claude Code: `{{CLAUDE_COMMAND}}`
+- Codex: {{CODEX_DESCRIPTION}}
+- GitHub Actions: see `examples/github-actions/{{FILE}}.yml`
+
+## Required Skills
+
+- `{{SKILL_1}}` — {{DESCRIPTION}}
+- `{{SKILL_2}}` — {{DESCRIPTION}}
+
+## State
+
+Filename: `{{STATE_FILE}}`
+
+```markdown
+<!-- Minimal example schema -->
+```
+
+## How the Loop Runs (Typical Cycle)
+
+1. {{STEP_1}}
+2. {{STEP_2}}
+3. {{STEP_3}}
+
+## Verification Strategy
+
+- {{VERIFIER_RULES}}
+
+## Human Handoff Points
+
+- {{GATE_1}}
+- {{GATE_2}}
+
+## Tool-Specific Notes
+
+**Grok Build TUI**: {{NOTES}}
+
+**Claude Code**: {{NOTES}}
+
+**Codex**: {{NOTES}}
+
+## Failure Modes & Mitigations
+
+| Failure | Mitigation |
+|---------|------------|
+| {{FAILURE}} | {{MITIGATION}} |
+
+## Success Metrics
+
+- {{METRIC_1}}
+- {{METRIC_2}}