DateGuard -- Date/Time Anti-Pattern Scanner
DateGuard scans codebases for date/time anti-patterns, timezone bugs, naive datetime usage, hardcoded timestamps, non-ISO formats, incorrect epoch handling, DST-unsafe comparisons, locale-dependent parsing, and temporal storage issues. It uses regex-based pattern matching against 90 date/time-specific patterns across 6 categories, lefthook for git hook integration, and produces markdown reports with actionable remediation guidance. 100% local. Zero telemetry.
Commands
Free Tier (No license required)
dateguard scan [file|directory]
One-shot date/time quality scan of files or directories.
How to execute:
bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [target]
What it does:
- Accepts a file path or directory (defaults to current directory)
- Discovers all source files (skips .git, node_modules, binaries, images, .min.js)
- Runs 30 date/time quality patterns against each file (free tier limit)
- Calculates a date/time quality score (0-100) per file and overall
- Grades: A (90-100), B (80-89), C (70-79), D (60-69), F (<60)
- Outputs findings with: file, line number, check ID, severity, description, recommendation
- Exit code 0 if score >= 70, exit code 1 if date/time quality is poor
- Free tier limited to first 30 patterns (TZ + NF categories)
Example usage scenarios:
- "Scan my code for timezone issues" -> runs
dateguard scan .
- "Check this file for date anti-patterns" -> runs
dateguard scan src/server.ts
- "Find naive datetime usage" -> runs
dateguard scan src/
- "Audit date/time handling in my project" -> runs
dateguard scan .
- "Check for DST-unsafe date math" -> runs
dateguard scan .
Pro Tier ($19/user/month -- requires DATEGUARD_LICENSE_KEY)
dateguard scan --tier pro [file|directory]
Extended scan with 60 patterns covering timezone, formatting, epoch precision, and date arithmetic.
How to execute:
bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [target] --tier pro
What it does:
- Validates Pro+ license
- Runs 60 date/time patterns (TZ, NF, EP, DA categories)
- Detects epoch precision bugs (ms vs seconds confusion)
- Identifies DST-unsafe date arithmetic
- Full category breakdown reporting
dateguard scan --format json [directory]
Generate JSON output for CI/CD integration.
bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [directory] --format json
dateguard scan --format html [directory]
Generate HTML report for browser viewing.
bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [directory] --format html
dateguard scan --category EP [directory]
Filter scan to a specific check category (TZ, NF, EP, DA, CP, ST).
bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [directory] --category EP
Team Tier ($39/user/month -- requires DATEGUARD_LICENSE_KEY with team tier)
dateguard scan --tier team [directory]
Full scan with all 90 patterns across all 6 categories including comparison/parsing and storage/serialization.
How to execute:
bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [directory] --tier team
What it does:
- Validates Team+ license
- Runs all 90 patterns across 6 categories
- Includes comparison/parsing checks (string date comparison, == on Date objects)
- Includes storage/serialization checks (VARCHAR for dates, missing timezone in DB)
- Full category breakdown with per-file results
dateguard scan --verbose [directory]
Verbose output showing every matched line and pattern details.
bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [directory] --verbose
dateguard status
Show license and configuration information.
bash "<SKILL_DIR>/scripts/dispatcher.sh" status
Check Categories
DateGuard detects 90 date/time anti-patterns across 6 categories:
| Category |
Code |
Patterns |
Description |
Severity Range |
| Timezone Handling |
TZ |
15 |
Missing timezone in datetime creation, implicit local timezone, hardcoded offsets, timezone conversion without DST handling |
medium -- high |
| Naive Formatting |
NF |
15 |
Non-ISO date formats in APIs, locale-dependent parsing, ambiguous MM/DD vs DD/MM, toString() on dates |
low -- high |
| Epoch & Precision |
EP |
15 |
Millisecond vs second confusion, Y2038 risk, timestamps as strings, floating point timestamps, epoch 0 sentinels |
low -- medium |
| Date Arithmetic |
DA |
15 |
Manual +86400 day math, month arithmetic ignoring varying lengths, leap year bugs, DST-crossing calculations |
medium -- high |
| Comparison & Parsing |
CP |
15 |
Lexicographic date string comparison, Date == comparison, unparsed user input, timezone-unaware comparisons |
medium -- high |
| Storage & Serialization |
ST |
15 |
VARCHAR for timestamps in SQL, missing timezone in stored dates, JSON.stringify on Date, hardcoded date strings |
low -- high |
Tier-Based Pattern Access
| Tier |
Patterns |
Categories |
| Free |
30 |
TZ, NF |
| Pro |
60 |
TZ, NF, EP, DA |
| Team |
90 |
TZ, NF, EP, DA, CP, ST |
| Enterprise |
90 |
TZ, NF, EP, DA, CP, ST + priority support |
Scoring
DateGuard uses a deductive scoring system starting at 100 (perfect):
| Severity |
Point Deduction |
Description |
| Critical |
-25 per finding |
Severe temporal bug (Y2038, data loss from timezone) |
| High |
-15 per finding |
Significant quality problem (naive datetime, DST math) |
| Medium |
-8 per finding |
Moderate concern (ambiguous formats, missing timezone) |
| Low |
-3 per finding |
Informational / best practice suggestion |
Grading Scale
| Grade |
Score Range |
Meaning |
| A |
90-100 |
Excellent date/time handling |
| B |
80-89 |
Good handling with minor issues |
| C |
70-79 |
Acceptable but needs improvement |
| D |
60-69 |
Poor date/time quality |
| F |
Below 60 |
Critical temporal problems |
- Pass threshold: 70 (Grade C or better)
- Exit code 0 = pass (score >= 70)
- Exit code 1 = fail (score < 70)
Configuration
Users can configure DateGuard in ~/.openclaw/openclaw.json:
{
"skills": {
"entries": {
"dateguard": {
"enabled": true,
"apiKey": "YOUR_LICENSE_KEY_HERE",
"config": {
"severityThreshold": "medium",
"ignorePatterns": ["**/test/**", "**/fixtures/**", "**/*.test.*"],
"ignoreChecks": [],
"reportFormat": "text"
}
}
}
}
}
Important Notes
- Free tier works immediately with no configuration
- All scanning happens locally -- no code is sent to external servers
- License validation is offline -- no phone-home or network calls
- Pattern matching only -- no AST parsing, no external dependencies beyond bash
- Supports scanning all file types in a single pass
- Git hooks use lefthook which must be installed (see install metadata above)
- Exit codes: 0 = pass (score >= 70), 1 = fail (for CI/CD integration)
- Output formats: text (default), json, html
Error Handling
- If lefthook is not installed and user tries hooks, prompt to install it
- If license key is invalid or expired, show clear message with link to https://dateguard.pages.dev/renew
- If a file is binary, skip it automatically with no warning
- If no scannable files found in target, report clean scan with info message
- If an invalid category is specified with --category, show available categories
When to Use DateGuard
The user might say things like:
- "Scan my code for timezone issues"
- "Check my date/time handling"
- "Find naive datetime usage"
- "Detect DST-unsafe date math"
- "Are there any hardcoded timestamps?"
- "Check for missing timezone handling"
- "Audit my date/time practices"
- "Find ambiguous date formats"
- "Check for epoch precision bugs"
- "Scan for date/time anti-patterns"
- "Run a date/time quality audit"
- "Generate a date/time quality report"
- "Check if dates are stored properly in my database schema"
- "Find Date objects compared with == instead of getTime()"
- "Check my code for Y2038 risks"
1---2name: dateguard-23version: 1.0.04description: "Date/time anti-pattern scanner -- detects timezone bugs, naive datetime usage, hardcoded timestamps, non-ISO formats, incorrect epoch handling, DST-unsafe comparisons, and temporal anti-patterns"5homepage: https://dateguard.pages.dev6metadata:7 source: https://skillmd.com/skills/bishal-pdmsft/dateguard-28 openclaw:9 emoji: 📅10 primaryEnv: DATEGUARD_LICENSE_KEY11 requires:12 bins:13 - git14 - bash15 - python316 - jq17 configPaths:18 - ~/.openclaw/openclaw.json19 install:20 - id: lefthook21 kind: brew22 formula: lefthook23 bins:24 - lefthook25 label: Install lefthook (git hooks manager)26 os:27 - darwin28 - linux29 - win3230user-invocable: true31disable-model-invocation: false32---3334# DateGuard -- Date/Time Anti-Pattern Scanner3536DateGuard scans codebases for date/time anti-patterns, timezone bugs, naive datetime usage, hardcoded timestamps, non-ISO formats, incorrect epoch handling, DST-unsafe comparisons, locale-dependent parsing, and temporal storage issues. It uses regex-based pattern matching against 90 date/time-specific patterns across 6 categories, lefthook for git hook integration, and produces markdown reports with actionable remediation guidance. 100% local. Zero telemetry.3738## Commands3940### Free Tier (No license required)4142#### `dateguard scan [file|directory]`43One-shot date/time quality scan of files or directories.4445**How to execute:**46```bash47bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [target]48```4950**What it does:**511. Accepts a file path or directory (defaults to current directory)522. Discovers all source files (skips .git, node_modules, binaries, images, .min.js)533. Runs 30 date/time quality patterns against each file (free tier limit)544. Calculates a date/time quality score (0-100) per file and overall555. Grades: A (90-100), B (80-89), C (70-79), D (60-69), F (<60)566. Outputs findings with: file, line number, check ID, severity, description, recommendation577. Exit code 0 if score >= 70, exit code 1 if date/time quality is poor588. Free tier limited to first 30 patterns (TZ + NF categories)5960**Example usage scenarios:**61- "Scan my code for timezone issues" -> runs `dateguard scan .`62- "Check this file for date anti-patterns" -> runs `dateguard scan src/server.ts`63- "Find naive datetime usage" -> runs `dateguard scan src/`64- "Audit date/time handling in my project" -> runs `dateguard scan .`65- "Check for DST-unsafe date math" -> runs `dateguard scan .`6667### Pro Tier ($19/user/month -- requires DATEGUARD_LICENSE_KEY)6869#### `dateguard scan --tier pro [file|directory]`70Extended scan with 60 patterns covering timezone, formatting, epoch precision, and date arithmetic.7172**How to execute:**73```bash74bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [target] --tier pro75```7677**What it does:**781. Validates Pro+ license792. Runs 60 date/time patterns (TZ, NF, EP, DA categories)803. Detects epoch precision bugs (ms vs seconds confusion)814. Identifies DST-unsafe date arithmetic825. Full category breakdown reporting8384#### `dateguard scan --format json [directory]`85Generate JSON output for CI/CD integration.8687```bash88bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [directory] --format json89```9091#### `dateguard scan --format html [directory]`92Generate HTML report for browser viewing.9394```bash95bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [directory] --format html96```9798#### `dateguard scan --category EP [directory]`99Filter scan to a specific check category (TZ, NF, EP, DA, CP, ST).100101```bash102bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [directory] --category EP103```104105### Team Tier ($39/user/month -- requires DATEGUARD_LICENSE_KEY with team tier)106107#### `dateguard scan --tier team [directory]`108Full scan with all 90 patterns across all 6 categories including comparison/parsing and storage/serialization.109110**How to execute:**111```bash112bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [directory] --tier team113```114115**What it does:**1161. Validates Team+ license1172. Runs all 90 patterns across 6 categories1183. Includes comparison/parsing checks (string date comparison, == on Date objects)1194. Includes storage/serialization checks (VARCHAR for dates, missing timezone in DB)1205. Full category breakdown with per-file results121122#### `dateguard scan --verbose [directory]`123Verbose output showing every matched line and pattern details.124125```bash126bash "<SKILL_DIR>/scripts/dispatcher.sh" --path [directory] --verbose127```128129#### `dateguard status`130Show license and configuration information.131132```bash133bash "<SKILL_DIR>/scripts/dispatcher.sh" status134```135136## Check Categories137138DateGuard detects 90 date/time anti-patterns across 6 categories:139140| Category | Code | Patterns | Description | Severity Range |141|----------|------|----------|-------------|----------------|142| **Timezone Handling** | TZ | 15 | Missing timezone in datetime creation, implicit local timezone, hardcoded offsets, timezone conversion without DST handling | medium -- high |143| **Naive Formatting** | NF | 15 | Non-ISO date formats in APIs, locale-dependent parsing, ambiguous MM/DD vs DD/MM, toString() on dates | low -- high |144| **Epoch & Precision** | EP | 15 | Millisecond vs second confusion, Y2038 risk, timestamps as strings, floating point timestamps, epoch 0 sentinels | low -- medium |145| **Date Arithmetic** | DA | 15 | Manual +86400 day math, month arithmetic ignoring varying lengths, leap year bugs, DST-crossing calculations | medium -- high |146| **Comparison & Parsing** | CP | 15 | Lexicographic date string comparison, Date == comparison, unparsed user input, timezone-unaware comparisons | medium -- high |147| **Storage & Serialization** | ST | 15 | VARCHAR for timestamps in SQL, missing timezone in stored dates, JSON.stringify on Date, hardcoded date strings | low -- high |148149## Tier-Based Pattern Access150151| Tier | Patterns | Categories |152|------|----------|------------|153| **Free** | 30 | TZ, NF |154| **Pro** | 60 | TZ, NF, EP, DA |155| **Team** | 90 | TZ, NF, EP, DA, CP, ST |156| **Enterprise** | 90 | TZ, NF, EP, DA, CP, ST + priority support |157158## Scoring159160DateGuard uses a deductive scoring system starting at 100 (perfect):161162| Severity | Point Deduction | Description |163|----------|-----------------|-------------|164| **Critical** | -25 per finding | Severe temporal bug (Y2038, data loss from timezone) |165| **High** | -15 per finding | Significant quality problem (naive datetime, DST math) |166| **Medium** | -8 per finding | Moderate concern (ambiguous formats, missing timezone) |167| **Low** | -3 per finding | Informational / best practice suggestion |168169### Grading Scale170171| Grade | Score Range | Meaning |172|-------|-------------|---------|173| **A** | 90-100 | Excellent date/time handling |174| **B** | 80-89 | Good handling with minor issues |175| **C** | 70-79 | Acceptable but needs improvement |176| **D** | 60-69 | Poor date/time quality |177| **F** | Below 60 | Critical temporal problems |178179- **Pass threshold:** 70 (Grade C or better)180- Exit code 0 = pass (score >= 70)181- Exit code 1 = fail (score < 70)182183## Configuration184185Users can configure DateGuard in `~/.openclaw/openclaw.json`:186187```json188{189 "skills": {190 "entries": {191 "dateguard": {192 "enabled": true,193 "apiKey": "YOUR_LICENSE_KEY_HERE",194 "config": {195 "severityThreshold": "medium",196 "ignorePatterns": ["**/test/**", "**/fixtures/**", "**/*.test.*"],197 "ignoreChecks": [],198 "reportFormat": "text"199 }200 }201 }202 }203}204```205206## Important Notes207208- **Free tier** works immediately with no configuration209- **All scanning happens locally** -- no code is sent to external servers210- **License validation is offline** -- no phone-home or network calls211- Pattern matching only -- no AST parsing, no external dependencies beyond bash212- Supports scanning all file types in a single pass213- Git hooks use **lefthook** which must be installed (see install metadata above)214- Exit codes: 0 = pass (score >= 70), 1 = fail (for CI/CD integration)215- Output formats: text (default), json, html216217## Error Handling218219- If lefthook is not installed and user tries hooks, prompt to install it220- If license key is invalid or expired, show clear message with link to https://dateguard.pages.dev/renew221- If a file is binary, skip it automatically with no warning222- If no scannable files found in target, report clean scan with info message223- If an invalid category is specified with --category, show available categories224225## When to Use DateGuard226227The user might say things like:228- "Scan my code for timezone issues"229- "Check my date/time handling"230- "Find naive datetime usage"231- "Detect DST-unsafe date math"232- "Are there any hardcoded timestamps?"233- "Check for missing timezone handling"234- "Audit my date/time practices"235- "Find ambiguous date formats"236- "Check for epoch precision bugs"237- "Scan for date/time anti-patterns"238- "Run a date/time quality audit"239- "Generate a date/time quality report"240- "Check if dates are stored properly in my database schema"241- "Find Date objects compared with == instead of getTime()"242- "Check my code for Y2038 risks"