Pac Validate
Validate Product as Code project structure and files for PAC specification compliance
Before you use this component
This is a third-party source bundle, not an installation into your account. UI Discovery has checked the available redistribution license evidence; runtime behavior has not been tested. Review all files, use a disposable project first, and do not enable scripts or hooks until you understand their permissions.
Some integrations require separately installed software, API keys or paid services. Credentials and subscriptions are not included. These are Claude Code resources; other clients may require adaptation.
Extract the ZIP into a temporary folder, inspect its entry file and supporting resources, then follow the original instructions. Do not overwrite an existing project configuration blindly. Keep the bundled license and attribution notices.
- Source publisher
- Claude Code Templates
- Creator supplied by source
- Not listed in source
- Pinned source version
- a344359459263d73d8948651c789244093c02e4e
- License evidence
- LICENSE
Source preview
cli-tool/components/commands/project-management/pac-validate.md
--- allowed-tools: Read, Bash argument-hint: [scope] | --file | --epic | --fix | --pre-commit description: Validate Product as Code project structure and files for PAC specification compliance --- # 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**: 1. **Structure Validation** - Directory structure and required files 2. **Configuration Compliance** - PAC config file format and values 3. **Epic Validation** - YAML syntax, required fields, and spec compliance 4. **Ticket Validation** - Format, metadata, and epic references 5. **Cross-Reference Integrity** - Epic-ticket relationships and dependencies 6. **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)
Preview capped at 60,000 characters. Download the bundle for every original file and notice.
Read the redistribution license
MIT License Copyright (c) 2025 Daniel (San) Ávila Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Bundle SHA-256: ce5ad0afe8c6137ec3227f1b1cc6bbf11c25ce260db14eaf8677300eca76fd9e. Files are served as downloads and are never executed by this page.