post-validator

Run build, lint, type-check, and test commands until zero errors and warnings remain.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures codebases can be built, linted, type-checked, and tested reproducibly by detecting tooling and iterating fixes until zero errors and zero warnings remain.

Core Features & Use Cases

  • Detects project tooling (build systems, linters, test runners) from package files and CI configs.
  • Orchestrates compile, lint, type-check, and test commands, reports issues with precise file paths and lines.
  • Iteratively applies fixes until a clean, green state is achieved in local development and CI pipelines.

Quick Start

Run the validator on your project to detect and fix build, lint, type-check, and test issues until zero errors or warnings remain.

Frequently Asked Questions about post-validator

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

FAQPage Schema
How do I automate build, lint, type-check, and test validation for a codebase?

Automate codebase validation by detecting project tooling from package files and CI configs, then orchestrating build, lint, type-check, and test commands. This process iterates fixes until achieving zero errors and zero warnings for a clean state.

How does CI parity validation ensure reproducible builds and deterministic tests?

CI parity validation ensures reproducible builds and deterministic tests by aligning local development commands with CI pipelines. It reports issues using exact file paths and line numbers, tracking applied fixes until the codebase reaches a strict clean state.

Can I use this validator across diverse codebases with different build systems and test runners?

Yes, the validator works across diverse codebases by automatically detecting project tooling, build systems, linters, and test runners from existing package files and CI configurations without requiring manual setup.

What is the best way to fix lint and type-check warnings reported with exact file paths and line numbers?

Fix lint and type-check warnings by running the validator to report issues with precise file paths and line numbers. It iteratively applies fixes and tracks changes until zero errors and zero warnings remain in the project.

Why does my CI pipeline fail when local builds and tests pass cleanly?

CI pipelines fail when local builds lack strict CI parity. The validator resolves this by aligning local development tooling with CI configurations, ensuring reproducible builds and deterministic tests pass identically in both environments.

Do I need specific dependencies installed to run project health validation?

No specific dependencies are required. The validator detects existing tooling directly from your project's package files and CI configs, orchestrating the build, lint, type-check, and test commands already present in your codebase.