validate

Run linting, tests, and validation scripts before commits.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/SamyakJhaveri/loam --skill validate-samyakjhaveri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/SamyakJhaveri/loam/tree/main/seed/.claude/skills/validate
Command: npx skills add https://github.com/SamyakJhaveri/loam --skill validate-samyakjhaveri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-session validation loop ensures code changes do not harm the project by enforcing a two-wave gate before commits.

Core Features & Use Cases

  • Deterministic Wave 1 with linting, type checks, and diffs, executed without any LLM involvement.
  • Rule-based Wave 2 with tests and project-specific validation scripts to prevent regressions.
  • Writes .validation_passed sentinel with waves_passed to guard the commit gate.

Quick Start

Trigger validation for your current changes by running /validate before committing to ensure the gate passes.

Frequently Asked Questions about validate

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

FAQPage Schema
How do I enforce code quality checks before a git commit?

Pre-commit validation enforces code quality by running a two-wave gate of deterministic linting and rule-based tests before changes are committed. It writes a .validation_passed sentinel file to guard the commit gate.

Why use a two-wave validation gate for pre-commit checks?

A two-wave validation gate separates deterministic checks from rule-based validation. Wave 1 runs linting and type checks, while Wave 2 executes tests and project-specific scripts to prevent regressions.

What is the best way to prevent regressions during a git workflow?

Preventing regressions in a git workflow is achieved by running project-specific validation scripts and tests in Wave 2 of the validation gate, ensuring changes pass before committing.

Does the pre-commit validation gate work without LLM involvement?

The pre-commit validation gate works without LLM involvement during Wave 1, executing deterministic linting, type checks, and diffs to validate changes before proceeding to rule-based Wave 2.

Can I track validation success using a sentinel file in my git workflow?

You can track validation success using a .validation_passed sentinel file. The validation gate writes this file with the waves_passed status to guard the commit gate after both waves succeed.

What limitations exist when running rule-based validation scripts pre-commit?

Rule-based validation scripts in Wave 2 are limited to preventing regressions and executing project-specific checks. The gate requires both Wave 1 and Wave 2 to pass successfully before writing the sentinel file.