21 ready-to-run loops that work while you sleep — free to browse. Each is a real prompt you run on your own machine with your own coding agent. Open one to read exactly what it does.
A weekly sweep that catches documentation drift, verifies what really works, and lands fixes as a PR.
Set up a weekly loop that keeps this project's documentation honest. Every Monday around 6am my local time, review what has changed since the previous sweep - the loop keeps track of where the last one ended - and compar
A daily reliability pass that traces your real production errors to root cause and opens a PR per verified fix.
Set up a daily loop that sweeps this project's production errors. Before creating anything, verify a concrete way to read them exists on this machine - logs, an error tracker, a URL, or gh - smoke-test it once, propose t
A daily guardian that scans your React app, fixes the worst issue, and opens a PR.
Set up a daily loop that keeps this React project healthy. Every morning around 6am my local time, scan the project with `npx react-doctor@latest`, pick the single most severe issue it reports, fix it, and verify the fix
A daily janitor that finds one provably safe cleanup in your codebase and lands it as a PR.
Set up a daily loop that keeps this codebase tidy, one proven cleanup at a time. Every morning around 7am my local time, survey for housekeeping debt - dead code, stale files and comments, unused dependencies, duplicatio
A weekly triage that reviews your open dependency PRs on real evidence and merges only what you've authorized.
Set up a weekly dependency-triage loop for this project. Before creating it, verify gh can see this repo's Dependabot or Renovate PRs and run one listing as a smoke test, then confirm with me whether the loop may merge l
A weekly guardian that finds your riskiest untested code path, adds one solid test, and opens a PR.
Set up a weekly loop that grows this project's test coverage where it matters most. Before creating it, verify the test suite actually runs on this machine - run it once as a smoke test and confirm how coverage is measur
A weekly sweep for dependency advisories, leaked secrets, and unpinned CI actions that lands only provably safe fixes.
Set up a weekly security-sweep loop for this project. Before creating it, verify the tools this sweep needs are available on this machine - the dependency advisory source (the audit command for this stack, or gh's adviso
A daily doctor that hunts your flaky tests and CI slowdowns and fixes or quarantines the worst offender.
Set up a daily loop that keeps this project's CI fast and trustworthy. Before creating it, verify this machine can read CI run history - gh for GitHub Actions, or the CI provider's API or logs - run one listing as a smok
A daily monitor that researches your project's market and delivers one dated report every morning.
Set up a daily market-research loop for this project. First look at the project to figure out what product it is and what market space it lives in, propose a research focus, and confirm it with me before creating the loo
An always-on loop that earns Reddit comment karma by posting genuinely helpful, value-only comments grounded in your own expertise and knowledge base.
Set up an open loop that earns comment karma on my Reddit account by posting genuinely helpful, pure-value comments grounded in my own expertise. Karma is the by-product of being useful, never the pitch. Setup is a guide
A weekly loop that distills your merged PRs into a changelog entry and social post drafts, held for your review.
Set up a weekly loop that turns this project's shipped work into a changelog and announcement drafts. Before creating it, verify this machine can see the week's merged PRs and commits - gh or the git log - run one listin
An always-on support-inbox triage that investigates every ticket against your real stack, replies or escalates, and turns tickets into product signals and eng fixes.
Set up a support-triage loop for this business. Setup is a guided conversation in four steps - confirm each step with me before creating the loop; never create a blind loop. ## Step 1 - The support source - Ask where cus
A daily morning digest of your product's key metrics that flags anomalies plainly and stays quiet otherwise.
Set up a daily loop that reports this product's key metrics every morning. Before creating it, ask which product-analytics stack the numbers live in - PostHog, an analytics warehouse, a database, a dashboard API - verify
A daily watch on your signup and conversion funnel that alerts on real drops with the evidence and stays quiet when healthy.
Set up a daily loop that watches this product's signup and conversion funnel. Before creating it, ask where the funnel data lives - product analytics like PostHog, an events table, an analytics API - verify read access o
A daily personalized briefing - weather, your calendar, and the topics you choose - delivered as one dated report each morning.
Set up a daily loop that delivers a personalized morning briefing. Setup is a short conversation - confirm each piece with me before creating the loop, and never create a blind loop. First agree what the briefing covers
A scheduled loop that checks Homebrew for outdated packages and upgrades only what you've pre-authorized, verifying your key tools still run.
Set up a scheduled loop that keeps this machine's Homebrew packages current, safely. Before creating it, verify Homebrew is installed and usable here - run `brew update` and `brew outdated` once as a smoke test - and con
A daily short lesson on a topic you choose, each one building on the last, delivered as a dated report on the calendar.
Set up a daily loop that teaches me one short lesson at a time on a topic I choose. Before creating it, ask what I want to learn - a language, a technical skill, a subject - and how deep to go, propose a rough learning a
A closed loop that watches what happens after something you just shipped and finishes itself once the outcome is confirmed. Works best pasted right after finishing the task you want tracked.
Look at what was just built or shipped in this session and set up a loop that tracks its aftermath. Before creating anything, verify a concrete way to observe the outcome exists on this machine - logs, metrics or MCP too
A closed loop that watches one specific change or experiment against a measurable finish condition, reports the verdict, and finishes itself. Paste it right after the change goes live.
Look at the specific change or experiment that just went live in this session - a shipped feature, an A/B test, a config or pricing change - and set up a closed loop that watches it to a measurable verdict. This is the m
A closed loop that stakes out one specific hard-to-reproduce bug, captures full context the moment it recurs, and finishes once it has the evidence.
Set up a closed loop that stakes out one specific hard-to-reproduce bug until it recurs with enough evidence to fix it. Describe the bug with me first - the symptom, where it shows up, what makes it intermittent - and be
A closed loop bound to one upcoming release that runs a daily readiness checklist, reports drift, and files a final go/no-go on release day before finishing.
Set up a closed loop that shepherds one specific upcoming release to its date. Confirm the release with me first - which version or milestone, and the target date - and before creating anything, verify this machine can r
Every loop runs on your machine via your own coding agent — the server never runs an LLM or your code.