@cobusgreyling/loop-init 1.1.0

package/starters/minimal-loop-claude/.claude/agents/loop-verifier.md

@@ -0,0 +1,35 @@
+---
+name: loop-verifier
+description: Independent checker for loop-produced changes. Rejects unless tests pass and scope is minimal. Never implement fixes.
+model: inherit
+---
+
+You are the **checker** in a maker/checker split. Your job is to **reject** unless evidence is strong.
+
+## 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 the implementer's claim that tests passed — run them.
+- If you cannot run tests (env issue) → ESCALATE_HUMAN.

package/starters/minimal-loop-claude/.claude/skills/loop-triage/SKILL.md

@@ -0,0 +1,46 @@
+---
+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).

package/starters/minimal-loop-claude/LOOP.md

@@ -0,0 +1,32 @@
+# Loop Configuration — Minimal Triage (Claude Code)
+
+## Active Loops
+
+| Pattern | Cadence | Status | Command |
+|---------|---------|--------|---------|
+| Daily Triage | 1d | L1 report-only | `/loop 1d Run $loop-triage` |
+
+## Human Gates
+
+- No auto-fix until L2 checklist complete
+- All high-risk paths: human review required (see docs/safety.md denylist)
+
+## Worktrees
+
+- Use `isolation: worktree` when spawning implementer sub-agents (L2+).
+- One worktree per fix attempt; discard after verifier REJECT.
+
+## Connectors (MCP)
+
+- MCP optional for L1 report-only loops.
+- For L2+: GitHub MCP to read CI/issues; scope connectors to read + comment only until trusted.
+
+## Budget
+
+- Max sub-agent spawns per run: 0 (L1)
+- Review STATE.md daily
+
+## Links
+
+- Pattern: [daily-triage](../../patterns/daily-triage.md)
+- Checklist: [loop-design-checklist](../../docs/loop-design-checklist.md)

package/starters/minimal-loop-claude/README.md

@@ -0,0 +1,42 @@
+# Minimal Loop Starter — Claude Code
+
+Clone this into your project root to run a **report-only daily triage loop** (L1 readiness).
+
+## Quick Start
+
+1. Copy files into your repo:
+
+   ```bash
+   cp -r starters/minimal-loop-claude/.claude/skills/loop-triage .claude/skills/
+   cp starters/minimal-loop-claude/.claude/agents/loop-verifier.md .claude/agents/
+   cp starters/minimal-loop-claude/STATE.md.example STATE.md
+   cp starters/minimal-loop-claude/LOOP.md .
+   ```
+
+2. Customize `STATE.md` project name.
+
+3. Start the loop (Claude Code):
+
+   ```bash
+   /loop 1d Run $loop-triage. Read STATE.md first. Append high-priority and watch items. Update Last run timestamp. Do not auto-fix anything in week one.
+   ```
+
+4. Read `STATE.md` each morning for 1–2 weeks. Tune the triage skill.
+
+5. When triage quality is good, add `minimal-fix` from `templates/SKILL.md.minimal-fix` and enable small auto-wins with the verifier agent (`isolation: worktree` on implementer tasks).
+
+## What's Included
+
+| File | Purpose |
+|------|---------|
+| `STATE.md.example` | State spine template |
+| `.claude/skills/loop-triage/SKILL.md` | Triage skill |
+| `.claude/agents/loop-verifier.md` | Checker sub-agent for L2+ |
+| `LOOP.md` | Loop config doc for your team |
+
+## Next Steps
+
+- [Loop Design Checklist](../../docs/loop-design-checklist.md)
+- [Daily Triage pattern](../../patterns/daily-triage.md)
+- [Claude Code example](../../examples/claude-code/daily-triage.md)
+- Run `npx @cobusgreyling/loop-audit .` for readiness score

package/starters/minimal-loop-claude/STATE.md.example

@@ -0,0 +1,12 @@
+# Loop State — My Project
+
+Last run: never
+
+## High Priority (loop is acting or waiting on human)
+
+## Watch List
+
+## Recent Noise (ignored this run)
+
+---
+Run log: —

package/starters/minimal-loop-codex/.codex/agents/verifier.toml

@@ -0,0 +1,15 @@
+name = "verifier"
+description = "Rejects loop fixes unless tests pass and scope is minimal. Never implements fixes."
+instructions = """
+You are the checker in a maker/checker split. Default stance: REJECT until proven otherwise.
+
+Checklist (all must pass for APPROVE):
+1. Scope — only relevant files; no denylist paths
+2. Intent — addresses the stated target
+3. Tests — you ran them and report pass/fail with output
+4. No cheating — no disabled tests or skipped assertions
+5. Risk — recommend human review for medium+ risk even if tests pass
+
+Output verdict: APPROVE | REJECT | ESCALATE_HUMAN with evidence.
+"""
+reasoning_effort = "high"

package/starters/minimal-loop-codex/.codex/skills/loop-triage/SKILL.md

@@ -0,0 +1,46 @@
+---
+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).

package/starters/minimal-loop-codex/LOOP.md

@@ -0,0 +1,32 @@
+# Loop Configuration — Minimal Triage (Codex)
+
+## Active Loops
+
+| Pattern | Cadence | Status | Automation prompt |
+|---------|---------|--------|-------------------|
+| Daily Triage | 1d | L1 report-only | `Run $loop-triage. Read STATE.md. Report only.` |
+
+## Human Gates
+
+- No auto-fix until L2 checklist complete
+- All high-risk paths: human review required (see docs/safety.md denylist)
+
+## Worktrees
+
+- Codex provides a built-in worktree per thread — use it for L2+ fix attempts.
+- One fix per worktree; verifier subagent must APPROVE before proposing a PR.
+
+## Connectors (MCP)
+
+- MCP optional for L1 report-only loops.
+- For L2+: GitHub connector to read CI/issues; write scope limited to comments until trusted.
+
+## Budget
+
+- Max sub-agent spawns per run: 0 (L1)
+- Review STATE.md daily + Codex Triage inbox
+
+## Links
+
+- Pattern: [daily-triage](../../patterns/daily-triage.md)
+- Checklist: [loop-design-checklist](../../docs/loop-design-checklist.md)

package/starters/minimal-loop-codex/README.md

@@ -0,0 +1,49 @@
+# Minimal Loop Starter — Codex
+
+Clone this into your project root to run a **report-only daily triage loop** (L1 readiness).
+
+## Quick Start
+
+1. Copy files into your repo:
+
+   ```bash
+   cp -r starters/minimal-loop-codex/.codex/skills/loop-triage .codex/skills/
+   cp starters/minimal-loop-codex/.codex/agents/verifier.toml .codex/agents/
+   cp starters/minimal-loop-codex/STATE.md.example STATE.md
+   cp starters/minimal-loop-codex/LOOP.md .
+   ```
+
+2. Customize `STATE.md` project name.
+
+3. Create an **Automation** in the Codex app (Automations tab):
+
+   | Field | Value |
+   |-------|--------|
+   | Cadence | Daily (e.g. `1d`) |
+   | Environment | Local checkout or background worktree |
+   | Prompt | See below |
+
+   ```
+   Run $loop-triage. Read STATE.md first. Append high-priority and watch items.
+   Update Last run timestamp. Week 1: report only — do not modify source files.
+   ```
+
+4. Review findings in the Codex Triage inbox + `STATE.md` for 1–2 weeks.
+
+5. When triage quality is good, add `minimal-fix` from `templates/` and enable small auto-wins with the verifier subagent in an isolated worktree.
+
+## What's Included
+
+| File | Purpose |
+|------|---------|
+| `STATE.md.example` | State spine template |
+| `.codex/skills/loop-triage/SKILL.md` | Triage skill |
+| `.codex/agents/verifier.toml` | Checker sub-agent for L2+ |
+| `LOOP.md` | Loop config doc for your team |
+
+## Next Steps
+
+- [Loop Design Checklist](../../docs/loop-design-checklist.md)
+- [Daily Triage pattern](../../patterns/daily-triage.md)
+- [Codex example](../../examples/codex/daily-triage.md)
+- Run `npx @cobusgreyling/loop-audit .` for readiness score

package/starters/minimal-loop-codex/STATE.md.example

@@ -0,0 +1,12 @@
+# Loop State — My Project
+
+Last run: never
+
+## High Priority (loop is acting or waiting on human)
+
+## Watch List
+
+## Recent Noise (ignored this run)
+
+---
+Run log: —

package/starters/post-merge-cleanup/.claude/agents/loop-verifier.md

@@ -0,0 +1,35 @@
+---
+name: loop-verifier
+description: Independent checker for loop-produced changes. Rejects unless tests pass and scope is minimal. Never implement fixes.
+model: inherit
+---
+
+You are the **checker** in a maker/checker split. Your job is to **reject** unless evidence is strong.
+
+## 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 the implementer's claim that tests passed — run them.
+- If you cannot run tests (env issue) → ESCALATE_HUMAN.

package/starters/post-merge-cleanup/.claude/skills/post-merge-scan/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: post-merge-scan
+description: >
+  Scan recent merges to main for follow-up cleanup: TODOs, deprecations,
+  broken doc links, stale flags. Use in post-merge cleanup loops.
+user_invocable: true
+---
+
+# Post-Merge Scan Skill
+
+## Output per merge
+
+```markdown
+### PR #N — title (merged DATE)
+- Follow-ups found: (list with file:line)
+- Risk: low | medium | high
+- Effort: small | medium | large
+- Suggested loop action: minimal-fix | ticket | escalate-human | skip
+```
+
+## What to look for
+
+- `TODO` / `FIXME` introduced in merge
+- Deprecated APIs still referenced
+- Broken internal doc links
+- Stale feature flags marked for removal
+- Unused imports or dead code clusters (small only)
+
+## Rules
+
+- Only scan merges from the last 7 days unless state says otherwise.
+- Large refactors → ticket, not auto-fix.
+- Medium+ risk paths → escalate-human.
+- Be concise — this runs off-peak, not during active dev hours.

package/starters/post-merge-cleanup/.codex/agents/verifier.toml

@@ -0,0 +1,15 @@
+name = "verifier"
+description = "Rejects loop fixes unless tests pass and scope is minimal. Never implements fixes."
+instructions = """
+You are the checker in a maker/checker split. Default stance: REJECT until proven otherwise.
+
+Checklist (all must pass for APPROVE):
+1. Scope — only relevant files; no denylist paths
+2. Intent — addresses the stated target
+3. Tests — you ran them and report pass/fail with output
+4. No cheating — no disabled tests or skipped assertions
+5. Risk — recommend human review for medium+ risk even if tests pass
+
+Output verdict: APPROVE | REJECT | ESCALATE_HUMAN with evidence.
+"""
+reasoning_effort = "high"

package/starters/post-merge-cleanup/.codex/skills/post-merge-scan/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: post-merge-scan
+description: >
+  Scan recent merges to main for follow-up cleanup: TODOs, deprecations,
+  broken doc links, stale flags. Use in post-merge cleanup loops.
+user_invocable: true
+---
+
+# Post-Merge Scan Skill
+
+## Output per merge
+
+```markdown
+### PR #N — title (merged DATE)
+- Follow-ups found: (list with file:line)
+- Risk: low | medium | high
+- Effort: small | medium | large
+- Suggested loop action: minimal-fix | ticket | escalate-human | skip
+```
+
+## What to look for
+
+- `TODO` / `FIXME` introduced in merge
+- Deprecated APIs still referenced
+- Broken internal doc links
+- Stale feature flags marked for removal
+- Unused imports or dead code clusters (small only)
+
+## Rules
+
+- Only scan merges from the last 7 days unless state says otherwise.
+- Large refactors → ticket, not auto-fix.
+- Medium+ risk paths → escalate-human.
+- Be concise — this runs off-peak, not during active dev hours.

package/starters/post-merge-cleanup/.grok/skills/post-merge-scan/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: post-merge-scan
+description: >
+  Scan recent merges to main for follow-up cleanup: TODOs, deprecations,
+  broken doc links, stale flags. Use in post-merge cleanup loops.
+user_invocable: true
+---
+
+# Post-Merge Scan Skill
+
+## Output per merge
+
+```markdown
+### PR #N — title (merged DATE)
+- Follow-ups found: (list with file:line)
+- Risk: low | medium | high
+- Effort: small | medium | large
+- Suggested loop action: minimal-fix | ticket | escalate-human | skip
+```
+
+## What to look for
+
+- `TODO` / `FIXME` introduced in merge
+- Deprecated APIs still referenced
+- Broken internal doc links
+- Stale feature flags marked for removal
+- Unused imports or dead code clusters (small only)
+
+## Rules
+
+- Only scan merges from the last 7 days unless state says otherwise.
+- Large refactors → ticket, not auto-fix.
+- Medium+ risk paths → escalate-human.
+- Be concise — this runs off-peak, not during active dev hours.

package/starters/post-merge-cleanup/LOOP.md

@@ -0,0 +1,22 @@
+# Loop Configuration — Post-Merge Cleanup
+
+## Active Loops
+
+| Pattern | Cadence | Status | Command |
+|---------|---------|--------|---------|
+| Post-Merge Cleanup | 1d | L1 report-only week one | See README |
+
+## Human Gates
+
+- Architectural debt → create ticket, do not fix
+- Feature flag removal → human approval
+- Multi-file refactors → escalate
+
+## Budget
+
+- Max sub-agent spawns per run: 2 (L2)
+- Run off-peak (evening / overnight)
+
+## Links
+
+- Pattern: [post-merge-cleanup](../../patterns/post-merge-cleanup.md)

package/starters/post-merge-cleanup/README.md

@@ -0,0 +1,34 @@
+# Post-Merge Cleanup Starter
+
+Scaffold for the [Post-Merge Cleanup](../../patterns/post-merge-cleanup.md) loop (L1 report → L2 small fixes).
+
+## Quick Start
+
+```bash
+# Grok
+npx @cobusgreyling/loop-init . --pattern post-merge-cleanup --tool grok
+
+# Or manual copy
+cp -r starters/post-merge-cleanup/.grok/skills/post-merge-scan .grok/skills/
+cp starters/post-merge-cleanup/post-merge-state.md.example post-merge-state.md
+cp starters/post-merge-cleanup/LOOP.md .
+```
+
+Start (Grok):
+
+```
+/loop 1d Run post-merge-scan on merges to main (last 7d). Update post-merge-state.md. Small doc/link fixes only in worktree. Escalate refactors.
+```
+
+## Files
+
+| File | Purpose |
+|------|---------|
+| `post-merge-state.md.example` | Cleanup backlog from recent merges |
+| `.grok/skills/post-merge-scan/` | Scan skill |
+| `LOOP.md` | Cadence and gates |
+
+## Safety
+
+- No large refactors without human ticket
+- Denylist: feature flags, auth paths — see [safety.md](../../docs/safety.md)

package/starters/post-merge-cleanup/post-merge-state.md.example

@@ -0,0 +1,22 @@
+# Post-Merge Cleanup State — YOUR_PROJECT
+
+Last run: not yet run
+Status: report-only (week 1)
+
+## Pending Cleanup (from recent merges)
+
+- (none yet — first run will populate)
+
+## Completed (last 14d)
+
+- (none)
+
+## Deferred (human decision)
+
+- (none)
+
+## Denylist paths
+
+- auth/
+- payments/
+- infra/

package/starters/pr-babysitter/.claude/agents/loop-verifier.md

@@ -0,0 +1,35 @@
+---
+name: loop-verifier
+description: Independent checker for loop-produced changes. Rejects unless tests pass and scope is minimal. Never implement fixes.
+model: inherit
+---
+
+You are the **checker** in a maker/checker split. Your job is to **reject** unless evidence is strong.
+
+## 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 the implementer's claim that tests passed — run them.
+- If you cannot run tests (env issue) → ESCALATE_HUMAN.

package/starters/pr-babysitter/.claude/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/.codex/agents/verifier.toml

@@ -0,0 +1,15 @@
+name = "verifier"
+description = "Rejects loop fixes unless tests pass and scope is minimal. Never implements fixes."
+instructions = """
+You are the checker in a maker/checker split. Default stance: REJECT until proven otherwise.
+
+Checklist (all must pass for APPROVE):
+1. Scope — only relevant files; no denylist paths
+2. Intent — addresses the stated target
+3. Tests — you ran them and report pass/fail with output
+4. No cheating — no disabled tests or skipped assertions
+5. Risk — recommend human review for medium+ risk even if tests pass
+
+Output verdict: APPROVE | REJECT | ESCALATE_HUMAN with evidence.
+"""
+reasoning_effort = "high"