verify

Run format, typecheck, tests, and lint across monorepo packages.

562|80|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/kdlbs/kandev --skill verify-kdlbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/kdlbs/kandev/tree/main/.agents/skills/verify
Command: npx skills add https://github.com/kdlbs/kandev --skill verify-kdlbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual verification of code quality across the monorepo is time-consuming and error-prone. This Skill automates the full verification pipeline to ensure formatting, type correctness, and lint results are consistent before merges.

Core Features & Use Cases

  • Run format, typecheck, tests, and lint across all packages to enforce consistency.
  • Rebase workflows on main to maintain CI parity and catch regressions early.
  • Enable a repeatable verification process for PRs and feature branches.

Quick Start

Trigger a full verification on your feature branch to run format, typecheck, test, and lint across the monorepo.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I automate monorepo checks for formatting, lint, and typecheck before merging?

Automating monorepo checks involves running format, typecheck, lint, and tests across all packages. This pipeline enforces consistency by catching formatting issues, type errors, and lint problems before merges.

What is the best way to maintain CI parity when verifying a feature branch?

Maintaining CI parity involves rebasing your feature branch onto main before running verification. This approach catches regressions early by ensuring branch parity with the main codebase.

Can I run format, typecheck, and lint across all monorepo packages in parallel?

Yes, format, typecheck, and lint can run across all monorepo packages in parallel. Parallel verification catches issues early while significantly reducing overall pipeline execution time.

Does this automated verification process work for both local development and PR workflows?

Yes, the automated verification process applies to both local development and PR workflows. It runs defined format, test, and lint targets across packages to ensure consistency throughout the development lifecycle.

Why should I use an automated verification pipeline instead of manual code quality checks?

Manual code quality verification across a monorepo is time-consuming and error-prone. An automated pipeline provides a repeatable process ensuring format, type, and lint consistency for PRs and feature branches.