verify

Orchestrate build, type, lint, test, console log, and git status checks.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/Eotel/claude-marketplace --skill verify-eotel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/Eotel/claude-marketplace/tree/main/plugins/base/skills/verify
Command: npx skills add https://github.com/Eotel/claude-marketplace --skill verify-eotel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verification is the process of validating codebase health by performing a consistent set of checks to catch issues before they become problems.

Core Features & Use Cases

  • Build Check: Run the project build to ensure compilable state.
  • Type Check: Run TypeScript/type checker to identify type errors.
  • Lint Check: Run linter to surface style and potential issues.
  • Test Suite: Execute all tests and report results and coverage.
  • Console.log Audit: Identify stray console logs for production readiness.
  • Git Status: Show uncommitted changes to track ongoing work.

Quick Start

Run the verify skill to perform build, type check, lint, tests, console log audit, and git status in strict order.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I run a full codebase verification before merging a pull request?

Codebase verification runs build, type check, lint, test execution, console log audit, and git status in strict order to surface failures and regressions before merging.

What is included in an end-to-end codebase verification pass?

An end-to-end verification pass includes build checks, type checking, linting, test suite execution, console log auditing, and git status reporting to validate overall codebase health.

Does codebase verification check for stray console logs to ensure production readiness?

Yes, codebase verification includes a console.log audit that identifies stray console logs to ensure production readiness before deployment.

What's the best way to catch type errors and lint issues during ongoing development?

Running an automated verification pipeline catches type errors and lint issues during ongoing development by orchestrating TypeScript type checks and linter execution sequentially.

Why does my codebase verification pipeline report uncommitted git changes?

The verification pipeline reports uncommitted git changes to track ongoing work and ensure no local modifications are accidentally left out before a merge.