Pac Validate
Validate Product as Code project structure and files for PAC specification compliance
npx claude-code-templates@latest --command project-management/pac-validate Scanned by NVIDIA SkillSpector
Automated static analysis (no LLM) · v2.12.0 · 2026-10-23
Partial analysis: some checks could not run on this component.
SkillSpector looks for patterns such as shell commands, credential access, network calls or unpinned dependencies. An observation is something worth reading in the files before you install, not a confirmed vulnerability. Components that run code locally, like hooks, MCP servers and security tooling, naturally show more of them.
No observations.
Learn more about NVIDIA SkillSpector.
Content
Validate PAC Structure
Validate Product as Code project structure and files for PAC specification compliance: $ARGUMENTS
Current PAC State
- PAC directory: !
ls -la .pac/ 2>/dev/null || echo "No .pac directory found" - Configuration: @.pac/pac.config.yaml (if exists)
- Epic count: !
find .pac/epics/ -name "*.yaml" 2>/dev/null | wc -l - Ticket count: !
find .pac/tickets/ -name "*.yaml" 2>/dev/null | wc -l
Task
Comprehensive validation of PAC project structure and specification compliance:
Validation Scope: Use $ARGUMENTS for specific files/epics or validate entire PAC structure
Validation Checks:
- Structure Validation - Directory structure and required files
- Configuration Compliance - PAC config file format and values
- Epic Validation - YAML syntax, required fields, and spec compliance
- Ticket Validation - Format, metadata, and epic references
- Cross-Reference Integrity - Epic-ticket relationships and dependencies
- Data Consistency - Timestamps, status transitions, and ID uniqueness
Output: Detailed validation report with compliance status, issues found, and specific recommendations for fixes. Use --fix to automatically resolve common issues.
Exit Codes: 0 (valid), 1 (errors found), 2 (configuration issues)