setup-routines

For explicitly requested pstack, Benny or webhook setup/triage, read the Poteto adaptation.

Configure Claude Code routines: cloud sessions triggered by schedule, GitHub event, or API. Enforcement model: hooks and CLAUDE.md own standards; the prompt owns the task. Add /agent-watchdog for outputs; /visual-recap only when requested.

Templates

Template	Trigger	Result
pr-review	pull_request.opened	Review and inline comments
pr-feedback-resolve	pull_request.review_submitted	Fix/reply/resolve threads
issue-triage	issues.opened	Classify, label, investigate
weekly-health	weekly	Health report issue
docs-drift	weekly	Stale-doc PR/issue

Setup

1. Prerequisites: Claude Code web access, GitHub connected through /web-setup, and eligible plan.
2. Pick: hooks -> pr-review; feedback skill -> pr-feedback-resolve; triage -> issue-triage; quality gates -> weekly-health; reference docs -> docs-drift.
3. Web: at routines, create; name; paste routines/*.md and fill OWNER/REPO; select repo/environment; choose event/schedule/API trigger; remove unused connectors; save.
4. CLI schedule only: /schedule daily codebase health check at 9am. GitHub/API triggers use web.
5. Customize: project checks, labels, scope, and connector actions. Keep stable prompts; repository rules evolve. See REFERENCE.md for examples/API setup.
6. Test once manually: Web Run now or /schedule run; watch the returned session, inspect output, and tighten drift. See the reference for enforcement, triggers, and troubleshooting.

Routines must survive a closed laptop and pass the same PostToolUse/Stop gates as interactive work.