validate-a-cron-expression
Validate a cron expression against the exact scheduler dialect, time zone, calendar behavior, overlap, and operational intent. Use when scheduled execution timing must be predictable.
소스 정보
- 저장소
- protosphinx/sphinxstack
- 최근 소스 활동
- 2026년 7월 29일 13:55
- 감지된 SKILL.md 언어
- 영어
- 스타
- 3
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
파일 탐색기
2 개 파일SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- validate-a-cron-expression
- category
- code
- description
- Validate a cron expression against the exact scheduler dialect, time zone, calendar behavior, overlap, and operational intent. Use when scheduled execution timing must be predictable.
# validate-a-cron-expression
## When to use
- Use before creating or changing recurring scheduled work.
- Do not assume five-field and six-field cron dialects are equivalent.
## Preconditions
- Record scheduler, version, dialect, time zone, desired windows, holidays, duration, concurrency, and missed-run policy.
## Procedure
1. Parse with the exact scheduler implementation.
2. Generate future runs across ordinary, month-end, leap, daylight-saving, and year boundaries.
3. Compare every generated run to stated operational intent.
4. Check time zone source, clock, inclusive ranges, day-field semantics, and special tokens.
5. Define overlap, concurrency, catch-up, missed, retry, and duplicate behavior.
6. Test in a safe environment and record the next expected runs.
## Failure plan
- Use an explicit scheduler or calendar table when cron cannot express the rule safely.
## Worked example
A 02:30 local job has no run during a daylight-saving jump, so the team chooses UTC plus a business-calendar guard.
## Done
- A cron validation report records dialect, expression, time zone, generated runs, edge cases, and execution policy
- Month-end, leap, daylight-saving, overlap, missed-run, duplicate, and scheduler-version checks verify timing
GitHub에서 보기