Routines (research preview) that run on Anthropic’s cloud with your computer off — 1-hour minimum interval, plus GitHub-event and API triggers. Triage, docs sync, nightly audits.
Compare every doc against the current code, fix what's stale, verify commands and links, and open a reviewable PR.
Whenever a documentation pass is needed, review the codebase in full and make sure all documentation reflects the current implementation. Update stale documentation, verify the changes, then open a pull request.
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
/schedulenew
Community schedule loop for ci, sourced from github. Verified exit condition, evaluator-gated.
/schedule "check the PR every 15 min" |
/schedulenew
Audit and prune pinned memory contexts to stay under 7, replacing competing invariants atomically and checking load count before each pin.
/goal that must load every session (it is then surfaced deterministically by load pinned ). Pin sparingly — keep a context at ≤7 pinned (prune at 10; the pinned load cap of 100 is a safety net, not the budget). Decisions/patterns/status are NOT pin material. Before pinning, call load pinned to check the count; when an invariant supersedes an old one, unpin the old in the same step ( update memory(memory id=<old , delivery mode="on recall") ) so two competing invariants are never both pinned
/schedulenew
Schedule recurring batch jobs and cleanup tasks using Dapr cron bindings, running on your defined cadence.
/Schedule | bindings.cron | Batch jobs, cleanup tasks |
/schedulenew
On every push to main, check whether changed code drifted from the docs in /docs and open a PR fixing anything out of date.
/schedule on every push to main, check whether the changed code drifted from the docs in /docs, and open a PR fixing anything out of date
/schedulenew
Re-invoke a specific PR review skill every 20 minutes until the review completes or you stop it.
/loop 20m /review-pr 1234 , to re-run that skill each iteration. {/ min-version: 2.1.196 /}As of v2.1.196, a scheduled fire only runs skills that Claude is [allowed to invoke on its own](/en/skills#control-who-invokes-a-skill). The following reach Claude as plain text instead of executing
Run the full end-to-end suite every night at 2am and wake up to a digest of failures with screenshots, suspect commits, and a flakiness verdict per test.
/schedule every day at 2am, run the full e2e suite against the staging build; for each failure, attach the trace or screenshot, list the commits since the last green run, and say whether the failure looks flaky or real; post the digest to e2e-reports/ as a dated markdown file
Every Monday morning, run the dependency vulnerability audit, open one PR fixing what auto-fix can handle safely, and file issues for the rest.
/schedule every Monday at 8am, run `npm audit`, open a single PR applying only non-breaking fixes with tests passing, and file one issue per remaining high or critical advisory with its CVE link and affected paths
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.
/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
Sponsored · ConnectMyEmailLoops that read your inbox.
Email is the missing tool in your harness. ConnectMyEmail gives Claude Code and Codex a clean MCP into Gmail, Outlook, iCloud and IMAP — triage, drafts, follow-ups, on a loop.
connectmyemail.com → /schedulenew
Every weekday at 9am, label new GitHub issues from the last 24 hours by area and priority and post a one-line summary on each.
/schedule every weekday at 9am, label new issues from the last 24h by area and priority, and post a one-line summary on each
Once a week, verify every command, path, and badge in the README actually works against the current codebase and open a PR fixing anything stale.
/schedule every Friday at 3pm, verify the README: run each documented setup and usage command in a clean checkout, check that referenced files and scripts exist, and open a PR correcting anything that fails or has drifted, with a note explaining each fix
Six weeks, one variable changed per post; measure replies, saves, and questions, and end with a winner or an honest null.
Find a repeatable weekly post format for [approved account, audience, and topic] through a six-week experiment. If the account, audience, or topic is missing, ask for it before drafting. Obtain approval before publishing anything externally. Each week, draft one short post about a real problem [person, product, or company] solves. Record substantive replies, saves, and questions after the same measurement window. Treat likes as secondary evidence. Keep the audience, topic area, cadence, and measurement window comparable. Change only one meaningful element each week, such as the opening, format, example, or call to action, based on the strongest signal from the previous post. Stop when one format materially outperforms the alternatives, the six-week experiment ends without a winner, approval is withheld, required metrics are unavailable, or the budget is exhausted. Never fabricate engagement data. Finish with every post, its measurements, the variables tested, the winning format or no-winner result, and the next recommendation.
Every Monday, list remote branches with no commits in 30 days, classify each as merged, abandoned, or unclear, and file a cleanup checklist issue — deleting nothing.
/schedule every Monday at 9am, list remote branches with no commits in the last 30 days; for each, note whether it is fully merged into main, who last touched it, and any open PR; post the list as a checklist in a single `branch-cleanup` issue, and do not delete any branch yourself
Review yesterday's changes each night and keep user-facing release history complete and accurate.
Each night, review changes from the previous day and update the changelog with anything users should know.
The two-layer answer to how do I run this overnight: /goal drives in-session work to done, while a scheduled Routine keeps recurring unattended work running on Anthropic's cloud with your laptop closed.
/schedule a Routine (runs on Anthropic cloud, laptop closed) for recurring unattended work, and use `/goal` for in-session iterate-to-done — the two-layer overnight pattern.
/schedulenew
In 2 weeks, open a PR removing the feature flag and its dead code branches.
/schedule in 2 weeks, open cleanup PR removing feature flag
/schedulenew
A scheduled Routine that runs each weekday at 9am to review the open pull requests assigned to you and leave a first-pass review on each, running in the cloud even with your computer off.
/schedule weekdays at 9am: review open PRs assigned to me, leave a first-pass