with one click
run-tests
Run ctest validation tests on a built product
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Run ctest validation tests on a built product
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Assess a pending NIST 800-53 control with OSCAL enrichment, CIS reverse lookup, and Linux hardening prioritization. Guides authors through understanding, automatability analysis, rule mapping, and validation.
Resolve XCCDF variable selections for a set of rules. Looks up which variables each rule depends on, reads their .var files, and guides the author to select a value key for each variable. Returns a list of var_name=key selections ready to add to a control file's rules list.
Open a pull request in the browser with prefilled title, description, and labels
Create a new product in ComplianceAsCode project
Create a template for checks and remediations
Create Automatus test scenarios to test the given rule.
| name | run-tests |
| description | Run ctest validation tests on a built product |
Run the ctest validation suite against built content in build/.
This skill uses mcp__content-agent__* tools when available (preferred — deterministic, structured results). When the MCP server is not configured, fall back to filesystem-based alternatives noted as Fallback in each step. See .claude/skills/shared/mcp_fallbacks.md for detailed fallback procedures. The skill must complete successfully either way.
Check that the build directory exists and contains content:
Use mcp__content-agent__list_built_products to check which products have been built and have artifacts available.
Fallback: Run ls build/ssg-*-ds.xml 2>/dev/null to check for built datastreams.
If no build artifacts found, inform the user:
build//build-product <product> firstRun the full test suite:
cd build && ctest -j$(nproc) --output-on-failure
This includes:
Test Results Summary
====================
Tests: ALL PASSED
Validation: COMPLETE
Test Results Summary
====================
Tests: FAILURES DETECTED
- X/Y tests passed
Failed Tests:
1. test-yaml-syntax-<product>
- File: linux_os/guide/.../rule.yml
- Error: Invalid YAML at line 15
2. test-oval-schema-<product>
- File: build/ssg-<product>-oval.xml
- Error: Element 'object': Missing required attribute 'id'
Suggested Fixes:
1. Check YAML syntax in the indicated file
2. Review OVAL generation for the affected rule
Ask if user wants additional lint checks:
find linux_os/guide -name "*.sh" -exec shellcheck {} \;
ansible-lint build/ansible/*-playbook-*.yml
yamllint linux_os/guide/
ruff check ssg/
# or
tox -e flake8
Ask if user wants build statistics:
cd build
make <product>-stats
This generates:
Validation Complete
===================
Test Status: ALL PASSED
Ready for:
- Automatus testing: /test-rule <rule_id>
- PR creation
Validation Complete
===================
Test Status: FAILURES DETECTED
- See details above
Action Required:
1. Fix the failing tests before proceeding
2. Re-run: /run-tests
Common fixes:
- YAML syntax: Check indentation and special characters
- OVAL errors: Review template usage in rule.yml
- Missing references: Add required identifiers