Sweep and patch outdated dependencies
Run dependency audit every 6 hours, auto-patch safely, escalate risky updates to dependency-sweeper-state.md.
Prompt
/loop 6h Run dependency-triage for outdated and vulnerable packages. Update dependency-sweeper-state.md. Patch-only auto-fix in worktree with loop-verifier. Escalate major bumps and denylisted packages
claude-code
Source: cobusgreyling ↗graded C · 50/100 — how grades work (Safety Score v2) →
Similar loops
All maintenance loops →B
/scheduleMaintenancelow risk
Watch published docs for link rot against the Internet Archive
Collect external links from docs weekly, archive dead ones via Wayback Machine, open a PR with replacements and a report of unfixed links.
/schedule weekly — outbound link-rot sweep with archived replacements.
Setup: add the Wayback Machine MCP server (npx -y mcp-wayback-machine, no API key for reads).
Each run, at most 12 turns:
1. Collect every external http(s) link in docs/ and README.md into one list. If the list is
empty, report "no external links" and STOP.
2. Request each URL once (HEAD, then GET only on a 405). Never retry a host more than twice and
never request the same host more than 10 times in a run — this is a health check, not a crawl.
3. For each link returning 4xx/5xx or failing to resolve, call the Wayback MCP for the newest
snapshot before today. Record: original URL, status, snapshot URL, snapshot date.
4. Replace only links that have a snapshot; leave the rest untouched and list them for a human.
5. VERIFY before finishing: re-request every replacement snapshot URL and confirm it returns 200.
Drop any replacement that does not.
6. Open a PR with the diff plus a table of every change and every unfixed dead link.
EXIT when the PR is open, or when step 1 finds no links, or at 12 turns — whichever comes first.
Do not edit link targets that still return 200. Do not push to main. Do not delete a dead link
without a working archived replacement; report it instead.
C
/scheduleMaintenancelow risk
Weekly tech debt report
Every Friday, compile a trend report of debt signals — TODO count, lint suppressions, type coverage, largest files — so the team sees drift before it compounds.
/schedule every Friday at 4pm, measure TODO/FIXME count, eslint-disable and ts-ignore counts, type coverage, and the five largest source files; append the numbers with week-over-week deltas to reports/tech-debt.md and call out the single worst trend in one paragraph
C
/loopMaintenancemedium risk
TODO burn-down
Chip away at the oldest TODO comments in the codebase, one per pass: either resolve it properly or convert it into a tracked issue.
/loop 30m find the oldest TODO or FIXME comment in the codebase, and either implement it (with a test) if it takes under 50 changed lines, or open a GitHub issue capturing its context and delete the comment; report which TODO you handled; stop when none remain