verify

agentage's avatarfrom agentage

Run project verification checks (type-check, lint, test). Use this skill when the user asks to verify the project, run checks, or validate code quality.

⭐1stars🔀0forks📁View on GitHub🕐Updated Jan 4, 2026
[Testing and QA]

When & Why to Use This Skill

The Verify Project skill is a comprehensive quality assurance tool designed to automate the validation of software projects. It streamlines the development workflow by executing critical checks including TypeScript type-checking, ESLint linting, Jest unit testing, and Playwright E2E testing. By consolidating these verification steps into a single command, it ensures code integrity, maintains high quality standards, and prevents regressions throughout the development lifecycle.

Use Cases

  • Pre-Commit Validation: Automatically run linting and type-checks to ensure code meets project standards before committing changes to version control.
  • Continuous Integration Simulation: Mirror CI/CD pipeline checks locally to identify and fix build or test failures before pushing code to a shared repository.
  • Regression Testing: Execute a full suite of unit and end-to-end tests after significant refactoring to guarantee that existing functionality remains intact.
  • Build Verification: Validate that the project compiles and builds successfully across different environments, ensuring the application is ready for deployment.
  • Code Quality Auditing: Use as a gatekeeper during code reviews to verify that new contributions pass all automated quality gates and testing requirements.
nameverify
descriptionRun project verification checks (type-check, lint, unit tests, e2e tests, build). Use this skill when the user asks to verify the project, run checks, or validate code quality.

Verify Project Skill

Purpose

Run comprehensive project verification checks including type-checking, linting, unit tests, e2e tests, and build validation.

When to Use

  • User asks to verify project
  • User asks to run checks/tests
  • Before committing/pushing changes
  • After code changes
  • Before creating a PR

Steps

  1. Run unit tests & build verification

    npm run verify

    This runs: type-check, lint, test, and build

  2. Run e2e tests (optional, recommended before release)

    npm run test:e2e

  3. Report results

    • ✅ All passed
    • ❌ Show failures and fix them

Available Scripts

Core Verification

  • npm run verify - runs type-check + lint + test + build
  • npm run type-check - TypeScript validation
  • npm run lint - ESLint check
  • npm run lint:fix - Auto-fix linting issues
  • npm run test - Run Jest unit tests
  • npm run test:e2e - Run Playwright e2e tests
  • npm run build - Build all packages

Quality Gates

  • ✅ Type check must pass
  • ✅ Linting must pass (no warnings)
  • ✅ All unit tests must pass
  • ✅ Build must succeed
  • ✅ E2E tests should pass (before release)