Describe a Schedule in English and Let Claude Write the Cron Expression
Cron syntax is one of those things you look up every single time. Stop Googling — describe the schedule in English and Claude writes the expression.
"Write a cron expression for: every weekday at 9:30 AM"
Claude gives you the expression and explains what each part means:
30 9 * * 1-5
# ┬ ┬ ┬ ┬ ┬
# │ │ │ │ └─ Monday through Friday
# │ │ │ └─── Every month
# │ │ └───── Every day of month
# │ └─────── 9 AM
# └──────────── 30 minutes
This works for any schedule complexity:
# Simple schedules
"Every hour on the hour" → 0 * * * *
"Every day at midnight" → 0 0 * * *
"Every Sunday at 3 AM" → 0 3 * * 0
# Complex schedules
"Every 15 minutes during business hours (9-5) on weekdays"
→ */15 9-17 * * 1-5
"First day of every quarter at midnight"
→ 0 0 1 1,4,7,10 *
"Every other Tuesday at noon"
# Claude explains this can't be expressed in standard cron
# and suggests alternatives
You can also go the other direction — paste a cron expression you found and ask Claude to explain it:
"What does this cron expression do: 0 */6 * * 1-5"
# → "Every 6 hours on weekdays (midnight, 6am, noon, 6pm)"
When adding scheduled tasks to your project, Claude writes the full implementation:
"Add a scheduled task that sends weekly report emails every Monday at 8 AM"
# Claude writes the cron expression AND the Laravel scheduler entry,
# GitHub Actions schedule, or whatever your framework uses
Cron expressions are write-only code — easy to create, impossible to read. Let Claude write them so you describe the schedule and get the syntax right every time.
via Claude Code
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.