verify

Run build, type checks, lint, and security audits before PRs.

2|2|Updated Mar 21, 2025
One-click install
npx skills add https://github.com/MeshJS/governance --skill verify-meshjs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/MeshJS/governance/tree/main/.claude/skills/verify
Command: npx skills add https://github.com/MeshJS/governance --skill verify-meshjs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-PR verification loop to run build, type checks, lint, and security audits, ensuring code quality before PRs or merges.

Core Features & Use Cases

  • Runs builds, type checks, lint, and security audits before PRs.
  • Produces a structured pass/fail report to guide merge decisions.
  • Supports multiple modes (quick, full, pre-pr) to balance speed and depth.

Quick Start

Run the verify command with the desired mode (quick|full|pre-pr) to validate your changes before opening a PR.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I run pre-PR checks for build, lint, and type validation together?

Pre-PR checks are run by executing a verification workflow that automatically orchestrates build, type, lint, and security audit tasks to validate code changes before opening a pull request.

What is the best way to automate security audits and type checks before a pull request?

Automating security audits and type checks before a PR requires a verification tool that sequences these checks automatically, producing a structured pass or fail report to guide merge decisions.

Can I run a quick lint and build verification for multi-language codebases?

Yes, you can run quick verification modes across multi-language codebases, applying consistent build and lint checks as long as the project defines the necessary tooling scripts.

Does pre-PR verification work with existing build tools and type-check scripts?

Pre-PR verification works with existing build tools and type-check scripts by requiring the project to define its own tooling, then orchestrating those scripts during the validation sequence.

What is the difference between quick, full, and pre-pr verification modes?

Quick, full, and pre-pr modes balance speed and depth during verification; they orchestrate the sequence of build, type, lint, and security checks differently based on the required validation thoroughness.

Why do I need to define tooling scripts for automated code quality checks?

You need to define tooling scripts because the verification process relies on the project's existing build, type-check, and lint configurations to execute consistent checks across the codebase.