Use /loop and /schedule to run any Claude Code task automatically — recurring reviews, nightly audits, scheduled agents, and event-driven hooks.
Runs any prompt or slash command on a repeating interval inside your live Claude Code session. Self-pacing available — Claude decides when to fire next.
Creates remote scheduled agents that run on a cron schedule — even when Claude Code is closed. One-time or recurring. Notifies you on completion.
The /loop command keeps Claude running a task on repeat, so you can stay in flow while Claude monitors, reviews, or checks status in the background.
/loop 10m /review
/loop Run the marketing agent iteration and handle one action
/loop 2m Check if the CI build on branch feature/auth has passed yet
When you omit the interval (e.g., /loop Run the tests and fix failures), Claude Code dynamically decides when to wake up next based on what it's waiting for. It considers cache window expiry, expected task duration, and idle time — choosing intervals that minimize cost and latency.
The /schedule command creates remote scheduled agents that execute on a cron schedule. Unlike /loop, these run entirely in the background — even when Claude Code is closed.
/schedule run /security-review on this branch at 11pm tonight
/schedule run /deps every Monday at 9am and report outdated packages
/schedule list
| Scenario | Use | Why |
|---|---|---|
| Review as you code | /loop 10m /review | In-session; fires while Claude Code is open |
| Nightly security audit | /schedule | Background; runs even when you're offline |
| Wait for a 30-min build | /loop (self-paced) | Self-paces to avoid unnecessary wake-ups |
| Daily dependency check | /schedule | Cron-based; runs at a fixed time daily |
| Babysit a long migration | /loop (self-paced) | Monitors and acts on results in real time |
For true event-driven automation — triggering a Claude task when a specific shell event fires — use /update-config to add hooks to your settings.json. Hooks are shell commands that execute in response to Claude Code events.
/update-config add a hook that runs `echo "Tool complete"` after every tool call
Common hook patterns: run a linter after every file edit, send a Slack notification when Claude stops, auto-stage files after a successful build.
See /loop, /schedule, /update-config, and 19 more skills — searchable, with examples for each.
Open Claude Skills Browser →/loop 5m /review) or omit it to let Claude self-pace. Use it for watching a build, polling for status, or running a task repeatedly while you work./loop runs in your current live session — the task repeats while you're actively in Claude Code. /schedule runs remotely on a cron schedule, even when Claude Code is closed. Use /loop for active monitoring; use /schedule for background automation./update-config to add hooks to your settings.json. Hooks are shell commands that Claude Code executes automatically in response to events like tool calls completing or Claude stopping. This enables event-driven automation without manually running slash commands.