domains / families / devops / cron-doctor

cron-doctor

authentic

Diagnose and validate cron expressions before they ship. Catches the five silent death-traps: impossible dates that never fire, OR-semantics that fire too often, midnight spikes, uneven step drift, and leap-year February 29.

When to use

• Use when a user writes, edits, reviews, or deploys a cron expression — in a
• Use when debugging a job that "didn't fire" or "fired at the wrong time."
• Use when a user asks "what does this cron expression mean?" or "when will this
• Use when reviewing a CI/CD pipeline or infrastructure config that contains a
• Use when a user pastes a 5-field cron expression and asks for a sanity check.

When not to use

• This skill targets standard 5-field cron as implemented by Vixie cron, systemd
• Estimated annual fire counts assume a non-leap reference year; February 29
• This skill does not replace environment-specific validation, testing, or expert

Skill page

Source