claude-code-routines

The community collection of ready-to-use Claude Code Routines. Battle-tested automation prompts you can install in one command.

Claude Code Routines let you put Claude on autopilot — scheduled tasks, GitHub event triggers, and API webhooks that run on Anthropic's cloud. But writing a good routine prompt from scratch is hard. This project gives you proven, community-tested routines so you don't reinvent the wheel.

What are Claude Code Routines?

Claude Code Routines are automated Claude Code sessions that run on Anthropic's cloud infrastructure. You define a prompt, connect your repos and tools (Slack, Linear, GitHub, Google Drive), and set a trigger:

• Schedule — run hourly, daily, weekly
• GitHub event — run on PR opened, release published, issue created
• API webhook — trigger from your deploy pipeline, monitoring tools, or any HTTP request

Routines run autonomously with no manual approval. They can push code, open PRs, post to Slack, create issues, and more. Available on Pro (5/day), Max (15/day), and Team/Enterprise (25/day) plans.

Quick Start

# Browse all available routines
npx claude-code-routines

# See a routine's full prompt and setup instructions
npx claude-code-routines show pr-reviewer

# Copy prompt to clipboard + get step-by-step install guide
npx claude-code-routines install daily-standup

# Search by keyword
npx claude-code-routines search security

No dependencies. No install. Just npx and go.

Available Routines

Code Review

| Routine | Trigger | Description | |---------|---------|-------------| | pr-reviewer | pull_request.opened | Reviews every PR with a structured checklist — correctness, security, performance, tests, readability. Leaves inline comments and posts a summary verdict. |

Security

| Routine | Trigger | Description | |---------|---------|-------------| | security-scan | Daily | Nightly security audit — dependency vulnerabilities, hardcoded secrets, OWASP Top 10 code patterns, permission review. Opens GitHub issues for findings. |

Documentation

| Routine | Trigger | Description | |---------|---------|-------------| | changelog-generator | Weekly | Generates a human-readable changelog from merged PRs, grouped by category (features, fixes, breaking changes). Opens a PR to update CHANGELOG.md. | | docs-drift | Weekly | Finds documentation that references changed APIs, removed features, or old defaults. Opens PRs to fix stale docs. | | release-notes | release.published | Generates polished release notes on every GitHub release — grouped by category with contributor credits and upgrade guides. |

DevOps

| Routine | Trigger | Description | |---------|---------|-------------| | deploy-verifier | API webhook | Post-deploy smoke tests — health checks, critical path verification, error log scan, latency check. Posts go/no-go verdict to Slack. |

Project Management

| Routine | Trigger | Description | |---------|---------|-------------| | bug-triage | issues.opened | Auto-triages new bug reports — identifies likely cause in codebase, labels by severity and area, detects duplicates, posts structured triage comment. | | stale-issue-cleaner | Daily | Labels stale issues (30+ days), auto-closes abandoned ones (44+ days), respects pinned/security labels, posts daily summary to Slack. |

Maintenance

| Routine | Trigger | Description | |---------|---------|-------------| | dependency-updater | Weekly | Checks for outdated dependencies across npm/pip/cargo/go, opens PRs grouped by risk level (patch/minor/major), includes changelogs and test results. |

Team

| Routine | Trigger | Description | |---------|---------|-------------| | daily-standup | Weekday mornings | Posts a development summary to Slack — yesterday's merged PRs, open reviews, new issues, CI status. So standup meetings focus on decisions, not status updates. |

How to Install a Routine

Option 1: Via CLI (/schedule)

# In Claude Code, run:
/schedule daily security scan at 2am
# Then paste the routine prompt when asked

Option 2: Via Web UI

1. Go to claude.ai/code/routines
2. Click New routine
3. Run npx claude-code-routines show <name> to get the prompt
4. Paste the prompt, select your repo, configure the trigger
5. Click Create

Option 3: Via Desktop App

1. Open the Schedule page
2. Click New task → New remote task
3. Paste the routine prompt and configure

Each routine in this collection includes the exact trigger type, GitHub event, filters, and connectors you need. Run npx claude-code-routines show <name> for the full setup guide.

CLI Reference

npx claude-code-routines                  # List all routines (default)
npx claude-code-routines list             # List all routines
npx claude-code-routines show <name>      # Full prompt + setup instructions
npx claude-code-routines install <name>   # Copy to clipboard + guided setup
npx claude-code-routines search <query>   # Search by name, description, or tag
npx claude-code-routines help             # Show help

Aliases: ls = list, info = show, add = install

Contributing

We welcome community routines! Here's how to add yours:

1. Create a routine file

Add a JSON file to routines/ following this format:

{
  "name": "my-routine",
  "title": "My Routine",
  "description": "What it does in one sentence.",
  "category": "category-name",
  "trigger": {
    "type": "schedule",
    "frequency": "daily",
    "event": "pull_request.opened",
    "filters": {}
  },
  "recommended_schedule": "Daily at 2am",
  "connectors": ["github", "slack"],
  "prompt": "The full prompt Claude runs each time...",
  "tags": ["relevant", "tags"]
}

2. Write a great prompt

The prompt is the most important part. It runs autonomously with no human approval, so:

• Be explicit about what to do and what NOT to do
• Define what success looks like
• Handle edge cases (empty results, errors, no changes needed)
• Include output format examples
• Keep it focused — one routine, one job

3. Open a PR

We'll review the prompt quality, test it, and merge it.

Trigger Types

| Type | How it works | Best for | |------|-------------|----------| | Schedule | Runs on a cron schedule (hourly, daily, weekly) | Maintenance, reporting, audits | | GitHub | Fires on repo events (PR opened, release published, issue created) | Code review, triage, release notes | | API | HTTP POST to a per-routine endpoint with bearer token | Deploy verification, alert response, CI integration |

A single routine can combine multiple triggers. For example, a PR review routine can run nightly AND react to every new PR.

FAQ

Do routines use my Claude Code subscription? Yes. Routines draw from the same usage as interactive sessions, plus a daily cap: Pro 5/day, Max 15/day, Team/Enterprise 25/day.

Can I customize these prompts? Absolutely. These are starting points. Copy the prompt, modify it for your team's conventions, and deploy.

Do I need to install anything? No. npx claude-code-routines runs directly. No global install needed.

Can I use these with GitHub, GitLab, Bitbucket? Routines currently support GitHub repositories. GitLab and Bitbucket support may come as Anthropic expands the feature.

What connectors are supported? Slack, Linear, Google Drive, GitHub, and more. Check your connected services at claude.ai Settings → Connectors.

Related Resources

• Claude Code Routines Documentation
• Introducing Routines in Claude Code (Blog)
• Claude Code Overview
• MCP Connectors
• Claude Code Skills
• Claude Code Hooks

Keywords

Claude Code Routines, Claude Code automation, Claude Code scheduled tasks, Claude Code GitHub triggers, Claude Code API triggers, Claude Code PR review bot, Claude Code security scanner, Claude Code changelog generator, Claude Code daily standup, Claude Code deploy verification, Anthropic Claude Code, AI automation, AI code review, AI DevOps, routine templates, routine prompts, Claude Code examples, Claude Code tutorial, how to use Claude Code Routines, best Claude Code Routines

License

MIT — use these routines however you want.