validate Commands
Overview
The validate category contains 15 commands for validating repository contracts, dependencies, and compliance.
Commands
| Command | Description |
|---|---|
| validate | |
| validate artifacts | Validate that build artifacts exist for a module and its dependencies |
| validate books | Validate books.yml configuration |
| validate contracts | Validate repository contracts against JSON schemas |
| validate control-tags | Validate @control tags against OSCAL catalog |
| validate dependencies | Validate module dependencies from go.mod files against contracts |
| validate design | Check workspace.dsl syntax using Structurizr CLI (requires Docker) |
| validate go-tidy | Validate Go module dependencies are tidy |
| validate markdown | Validate markdown file syntax |
| validate module-files | Validate module file ownership |
| validate module-hierarchy | Validate module dependency graph structure |
| validate release | Validate changelog format and structure |
| validate release-version | Validate release version format |
| validate risk-catalog | Validate OSCAL catalogs against OSCAL 1.1.3 schema |
| validate risk-profile | Validate OSCAL profile documents against OSCAL 1.1.2 schema |
| validate specs | Validate Gherkin specifications against quality contracts |
| validate test-tags | Validate that all test tags are defined in the tag contract |
| validate version | Validate version format |
Common Use Cases
Pre-commit Validation
Dependency Validation
Documentation Validation
Key Features
- Comprehensive validation of repository contracts
- Go module dependency checking
- Gherkin specification validation
- OSCAL compliance validation
- Design and documentation verification
See Also
Tutorials | How-to Guides | Explanation | Reference
You are here: Reference — information-oriented technical descriptions of the system.