validate

Validate Syntaris harness integrity and user-project test health.

Updated Apr 24, 2026

Search Tags:#testing #validation #hooks #release #calibration #harness

Ready to run

npx skills add https://github.com/brianonieal/Syntaris --skill validate-brianonieal

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/brianonieal/Syntaris/tree/main/.claude/skills/validate
Command: npx skills add https://github.com/brianonieal/Syntaris --skill validate-brianonieal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the risk of shipping a broken Syntaris setup by validating the methodology layer and the user project tests in one pass.

Core Features & Use Cases

Harness validation: Checks hook syntax, install round-trips, cross-file references, calibration wiring, and gate-close behavior.
Project test execution: Detects common test frameworks and runs the user's test suite when present.
Release and regression checks: Use it before tagging, publishing, or after editing hooks, skills, or agents to catch failures early.

Quick Start

Use the validate skill to run the full Syntaris harness validation and any detected project tests.

Frequently Asked Questions about validate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify hook syntax and test suite health before a release?▼

Harness validation checks hook syntax, cross-file references, and calibration wiring to ensure clean parsing and preserved install round-trips. It performs gate-close validation by running detected project test suites and reporting deterministic pass or fail summaries.

What is the best way to check release readiness for hooks and calibration files?▼

Release readiness checks for hooks and calibration files involve validating harness integrity and user-project test health in one pass. This process requires every hook and cross-file dependency to parse cleanly, preventing broken setups by catching failures before tagging or publishing.

Can I run regression triage across skills and agents after editing configuration files?▼

Regression triage across hooks, skills, and agents requires validating harness integrity and running user-project test suites. This catches failures early after editing configuration files by ensuring every cross-file dependency parses cleanly and reporting deterministic pass or fail summaries.

How does project test execution detect and run my test framework during validation?▼

Project test execution detects common test frameworks present in the user setup and runs the test suite automatically. This works alongside harness validation to check hook syntax and calibration wiring, reporting a deterministic pass or fail summary.

Does harness validation work without external dependencies for gate-close checks?▼

Harness validation works without external dependencies to perform gate-close checks. It validates the methodology layer by ensuring every hook and cross-file dependency parses cleanly, preserving install round-trips and reporting deterministic pass or fail summaries.

Why does validation fail when cross-file dependencies do not parse cleanly?▼

Validation fails when cross-file dependencies do not parse cleanly because broken references compromise harness integrity. The validation process requires clean parsing of all hooks and calibration wiring to preserve install round-trips and ensure deterministic pass or fail summaries.