validate

Audit Hali PRs against doctrine and quality standards.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/irvinesunday/Hali --skill validate-irvinesunday
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/irvinesunday/Hali/tree/main/.claude/skills/validate
Command: npx skills add https://github.com/irvinesunday/Hali --skill validate-irvinesunday

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Doctrine and quality guardianship for Hali PRs: ensures changes align with product doctrine, contract fidelity, test coverage, observability, and security, and prevents unsafe merges.

Core Features & Use Cases

  • Doctrine-aligned PR reviews: assesses adherence to Hali's architectural and doctrinal standards.
  • Contract fidelity & test adequacy: evaluates schema/contract changes and test coverage.
  • Observability & security checks: identifies gaps and provides actionable remediation.
  • Merge-readiness assessment: blocks work when standards are not met and guides remediation.

Quick Start

Provide the PR number to run full doctrine and quality validation, for example, /validate pr=247

Frequently Asked Questions about validate

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

FAQPage Schema
How do I automate PR review for contract fidelity and test adequacy?

Automate PR review by auditing code changes against quality doctrine to check contract fidelity, test adequacy, and correctness. Provide a PR number to run full validation and generate a contract-first report with actionable next steps.

What is doctrine-aligned PR validation and when do I need it?

Doctrine-aligned PR validation prevents PR drift by auditing changes against architectural and doctrinal standards. You need it to ensure code changes align with product doctrine, contract fidelity, test coverage, observability, and security before merge.

Does PR validation check observability and security for mobile and NLP pull requests?

Yes, PR validation checks observability and security for mobile and NLP pull requests. It applies to PRs across Auth, Schema, CIVIS, NLP, and mobile, identifying gaps and providing actionable remediation to ensure merge readiness.

How do I run a merge-readiness assessment to prevent unsafe PR merges?

Run a merge-readiness assessment by providing the PR number to execute full doctrine and quality validation. It blocks work when standards are not met, explicitly detailing findings and guiding remediation to prevent unsafe merges.

What is the best way to prevent PR drift across Auth and Schema changes?

The best way to prevent PR drift across Auth and Schema changes is applying rigorous doctrine checks. Auditing code changes against quality doctrine ensures correctness and contract fidelity, producing a contract-first report with explicit findings.