Issue de-duplication sweep

Twice a week, scan new GitHub issues for duplicates of existing ones and link them with a polite comment and a duplicate label, closing nothing automatically.

prompt
→ Claude
/schedule every Tuesday and Friday at 10am, compare issues opened in the last 4 days against existing open issues; when one is a likely duplicate, comment with a link to the original and apply the `possible-duplicate` label, but never close anything yourself
claude-code

Implementation note

The never-close rule matters: false-positive closures burn goodwill with reporters, while a label plus link costs nothing when wrong.

Source: looprepo

More planning loops

loop-init, loop-audit, loop-cost CLI patterns

/ralphnew

Three starter CLI tools that turn loop design into a repeatable workflow: scaffold a loop with a goal, budget, and verify step; audit an existing loop design; and estimate cost before you run.

prompt
→ Claude
Starter CLI tools: `loop-init` scaffolds a loop (goal, budget, verify step), `loop-audit` reviews an existing loop design, `loop-cost` estimates spend before running.
planningmedium risk

Ralph the PRD backlog

The canonical Ralph loop: each iteration starts fresh, reads the PRD and guardrails, ships exactly one backlog item end-to-end, and records what it learned.

prompt
→ Claude
/loop start each iteration with fresh context: read PROMPT.md, prd.json, and .ralph/guardrails.md; pick the single highest-priority item in prd.json not marked done, implement it with tests, run the full check suite, commit and mark it done only if green; if blocked or a check fails twice the same way, append the lesson to .ralph/guardrails.md and move on; stop when every item is done or after 30 turns
planninghigh risk

Set agent continuation budget

/goalnew

Configure max turns before agent stops, preventing runaway loops and controlling execution cost.

prompt
→ Claude
/goal budget <n Set max continuation turns
planninglow risk