verify

Run type-check, tests, and build checks for detected tech stacks.

Updated Aug 23, 2026

Search Tags:#automation #build #lint #test runner #ci #type-check #repo health

Ready to run

npx skills add https://github.com/escotilha/claude-public --skill verify-escotilha

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/escotilha/claude-public/tree/main/skills/verify
Command: npx skills add https://github.com/escotilha/claude-public --skill verify-escotilha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents shipping broken code by verifying that type-checking, tests, and builds succeed after changes.

Core Features & Use Cases

Automatic project detection: Identifies the project type (Node.js, Python, Go, or Rust) from common config files.
Run the right checks: Executes the applicable sequence for type-check, tests, and build (plus lint when available).
Actionable reporting: Produces a concise results summary table, while still showing failure details when issues occur.
Use case: After modifying a service in a mixed stack, run verification once to ensure the full quality gate (types + tests + build) stays green.

Quick Start

Run /verify all after you change code to get a single health report covering types, tests, and build.

Frequently Asked Questions about verify

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

FAQPage Schema

How do I run type-check, tests, and build checks across different repositories?▼

Automated project health verification detects the technology stack from config files and sequentially runs type-check, tests, and build checks. It supports Node.js, Python, Go, and Rust repositories to ensure quality gates stay green after code changes.

Does automated verification work with both Node.js and Go projects?▼

Yes, automated verification works with Node.js, Python, Go, and Rust projects. It detects the project type from common configuration files and executes the appropriate sequence of type-check, test, and build commands for the detected stack.

What's the best way to validate code changes before committing in a mixed stack?▼

Run a single verification command after modifying code to validate the full quality gate. It automatically detects the stack and produces a concise summary table of type-check, test, and build results with readable failure reporting for any issues found.

How does post-change validation handle test failures and build errors?▼

Post-change validation executes checks sequentially and provides readable failure reporting. It displays a concise summary table of overall results while showing specific failure details when type-check, test, or build issues occur, all without modifying files.

Can I run lint checks alongside type-check and build validation?▼

Yes, lint checks run alongside type-check, tests, and builds when available. The verification sequence automatically includes linting in the quality gate validation for supported repositories, adding it to the concise summary table report.

Will running automated quality gates modify my project files?▼

No, automated quality gates operate with read-only behavior and do not modify any project files. The verification process only runs type-check, tests, and build checks sequentially to report health status without altering the repository.