verification

Run type checks, linting, tests, and builds for post-change verification.

Updated Jun 17, 2025
One-click install
npx skills add https://github.com/kristijorgji/react_ts_vite_tailwind_sb --skill verification-kristijorgji
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/kristijorgji/react_ts_vite_tailwind_sb/tree/main/.agents/skills/verification
Command: npx skills add https://github.com/kristijorgji/react_ts_vite_tailwind_sb --skill verification-kristijorgji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After completing planned code changes, you must verify nothing is broken by running a fixed verification sequence.

Core Features & Use Cases

  • End-to-end verification that runs type checks, linting, tests, and builds in a deterministic order.
  • Applied to development workflows to catch regressions before delivery and ensure consistent releases.
  • Enables teams to enforce a final validation step after changes across the project.

Quick Start

Run the full verification sequence to ensure the codebase passes all checks and builds.

Frequently Asked Questions about verification

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

FAQPage Schema
How do I run end-to-end verification checks after making TypeScript code changes?

End-to-end verification of TypeScript code changes is automated by sequentially running type checks, linting, tests, and builds to detect regressions before delivery.

What steps are included in an automated post-change code verification sequence?

An automated verification sequence runs type checks, linting, tests, and builds in a deterministic order to enforce a final validation step and ensure consistent releases.

Do I need specific yarn scripts configured to automate typecheck and build verification?

Yes, automating verification requires yarn and specific standard project scripts: gen:i18n, typecheck, fix, lint, test, storybook:build, and build, requiring zero errors for success.

Can I include Storybook builds in my continuous integration regression checks?

Yes, Storybook builds are included in the continuous integration regression checks alongside type checks, linting, testing, and standard project builds to validate code health comprehensively.

Why does my code verification sequence fail during the typecheck or linting step?

A code verification sequence fails during typecheck or linting if any script returns an error, as the automated process enforces strict regression checks by requiring zero errors across all steps before proceeding to builds.

What is the best way to catch regressions before delivering a feature or bugfix?

The best way to catch regressions before delivery is applying an automated end-to-end verification sequence that runs type checks, linting, tests, and builds in a deterministic order to ensure code changes remain healthy.