📌 TL;DR
Claude Code Routines bundles “prompt + repo + trigger” into a recurring automated job.
It runs on Anthropic’s servers — your Mac can be off.
Here are 5 setups you can drop into your workflow today.
“I’m using Claude Code, but typing the same prompt over and over is annoying” — Routines is for you. It dropped yesterday (April 14) as a Research Preview, and I tried it right away. More practical than I expected.
💡 The Basics
A Routine has three parts:
| Prompt | What you want Claude to do |
| Repo + connectors | The codebase and external services to wire in |
| Trigger | Scheduled (cron) / API / GitHub event |
Set it up once and it runs without you. Because it executes on Anthropic’s servers, your machine can be powered off.
🛠️ 5 Practical Setups
1. Automated PR review
Trigger: GitHub — on PR open
Prompt: “Review the diff in this PR. Flag security issues, performance concerns, and style violations. Group comments by severity.”
Bake your team’s coding conventions into the prompt and Routine catches the obvious stuff before a human ever opens the PR. Saves your reviewers real time.
2. Post-deploy smoke test
Trigger: API — called from the CI/CD pipeline after a successful deploy
Prompt: “Production deploy just finished. Hit the main API endpoints, check responses, and ping Slack if anything is broken.”
That “is it actually working?” check after a deploy — automate it. No more anxiously refreshing dashboards after a 3 AM ship.
3. Doc drift detection
Trigger: Scheduled — every Monday at 9 AM
Prompt: “Diff the files changed last week against README and docs/. Flag anything where the docs probably need an update.”
Code shipped, docs didn’t — Routine catches it. A huge chunk of tech debt is just stale documentation, so this earns its keep fast.
4. Backlog grooming
Trigger: Scheduled — every Friday at 5 PM
Prompt: “Find GitHub Issues with no activity in 30+ days. Check whether they’re still relevant and clean up the dead ones.”
Stale issues pile up and the backlog stops meaning anything. A weekly auto-cleanup keeps it usable.
5. Dependency security check
Trigger: Scheduled — every day at 8 AM
Prompt: “Check the dependencies in package.json for reported vulnerabilities. Alert me if anything is critical or higher.”
Nobody runs npm audit by hand every day. Wire it into a Routine and you catch CVEs while they’re still fresh.
⚠️ Things to know
Daily run limits: 5 on Pro, 15 on Max, 25 on Team/Enterprise
Status: Research Preview — features may change or be restricted
Free plan: not supported. Pro or higher required
5/day on Pro sounds tight, but forcing yourself to pick the 5 most important Routines is a useful prioritization exercise. Start with the most repetitive, most annoying tasks you do.
💬 My take
Honestly, Routines is just “AI cron.” Same idea as a shell script in crontab — except the job is defined in natural language.
“Review this code” as a script gets ugly fast. As a Routine prompt it’s one line. That’s the actual value.
It’s a Research Preview though, so I’d keep it out of critical production paths and start with supporting roles. Automated PR review is the easiest first win.
❓ FAQ
Q. How is this different from GitHub Actions?
GitHub Actions runs predefined scripts. Routines lets an AI interpret a natural-language prompt and execute it. One line — “review this PR” — covers code analysis, issue triage, and posting comments without you wiring any of it up.
Q. What if a Routine messes up?
You can inspect the run output and execution logs. For anything sensitive, add guardrails right in the prompt — e.g., “run analysis only, do not commit.”
Q. Can one Routine span multiple repos?
Not yet — one Routine maps to one repo. To run the same logic across repos you set up a separate Routine for each.
🔗 References
📋 Official docs
→ Claude Code — Routines documentation
→ Introducing routines in Claude Code
📰 Coverage
Based on Anthropic’s official docs and public reporting. Routines is currently a Research Preview — features may change before GA. Details accurate as of writing (2026-04-15).
This post is part of an English mirror of a Korean dev experiments blog. Cross-posted for the global developer audience.