local-verify

Run linting, testing, and artifact generation checks locally before pull request submission.

3|2|Updated May 12, 2026
One-click install
npx skills add https://github.com/kriscendobot/garden --skill local-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-verify
Source: https://github.com/kriscendobot/garden/tree/main/skills/local-verify
Command: npx skills add https://github.com/kriscendobot/garden --skill local-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates the inefficiency of discovering lint, test, or build failures on CI servers by running the project's full verification suite locally before any code is pushed.

Core Features & Use Cases

  • Environment Parity: Ensures local verification matches CI behavior by managing git configurations and environment shims, preventing local-pass/CI-fail discrepancies.
  • Automated Gatekeeping: Executes a sequence of format, build, lint, codegen, test, and docgen steps, failing the process if any step is incomplete or if generated artifacts are stale.
  • Use Case: Use this skill to automatically validate a complex TypeScript project locally, ensuring that all linting, type-checking, and code generation are correct before submitting a pull request.

Quick Start

Run the local-verify skill to execute the full verification suite against the current project worktree.

Frequently Asked Questions about local-verify

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

FAQPage Schema
How do I run local verification checks before submitting a pull request?

Local pre-PR verification prevents CI server failures by executing the full suite—format, build, lint, codegen, test, and docgen—directly on your worktree. It ensures generated artifacts are not stale and catches discrepancies before code is pushed.

Why does my project pass linting and tests locally but fail on CI?

Environment parity issues cause local-pass and CI-fail discrepancies. This verification harness manages git configurations and environment shims locally to ensure your worktree matches CI behavior exactly, preventing unexpected server-side build failures.

What is the best way to enforce a CI contract locally before pushing code?

Enforce a CI contract locally using a deterministic, no-LLM verification harness. It captures lint, test, and build failures as immutable git blobs across your worktree, guaranteeing environment parity and strict automated gatekeeping before submission.

Does this local verification tool work with TypeScript project worktrees?

Yes, this local verification tool works with TypeScript project worktrees. It automatically validates complex TypeScript projects locally, ensuring all linting, type-checking, and code generation are correct before submitting a pull request.

How do automated gatekeeping checks handle stale generated artifacts?

Automated gatekeeping checks handle stale generated artifacts by executing a sequence of format, build, lint, codegen, test, and docgen steps. The process explicitly fails if any step is incomplete or if generated artifacts are outdated.

Do I need any external dependencies to run deterministic pre-PR verification?

No external dependencies are required to run deterministic pre-PR verification. The harness operates as a standalone no-LLM script suite, relying solely on your project's existing git worktree and standard local development environment configurations.