check-all

Automates linting, formatting, testing, and build verification for monorepo backend and frontend projects.

18|6|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/minh2004pd/chatbotfullpipeline --skill check-all
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-all
Source: https://github.com/minh2004pd/chatbotfullpipeline/tree/main/.claude/skills/check-all
Command: npx skills add https://github.com/minh2004pd/chatbotfullpipeline --skill check-all

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the full pre-push verification sequence to ensure code quality before commit.

Core Features & Use Cases

  • Backend lint & format, backend tests, and frontend verification (types, lint, and build) executed in order with automatic failure reporting.
  • Stop-on-first-failure workflow ensures quick feedback and prevents faulty pushes.
  • Use case: a developer pushes a feature branch and expects the pipeline to catch lint, format, and test regressions before merging.

Quick Start

Run the check-all skill to execute the full verification sequence across backend and frontend.

Frequently Asked Questions about check-all

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

FAQPage Schema
How do I automate pre-push verification for linting, formatting, and tests in a monorepo?

Pre-push verification for a monorepo is automated by executing lint, format, and test checks across backend and frontend. This skill runs the sequence automatically, ensuring failures halt the push before merging.

What is the best way to run frontend type-check and build checks before pushing code?

Frontend type-check and build checks are executed as part of a full pre-push verification sequence. The skill automates these alongside backend tests, stopping immediately if any verification step fails.

How do I stop faulty pushes when backend tests or frontend linting fails?

Faulty pushes are stopped using a stop-on-first-failure workflow during pre-push verification. The skill runs backend lint, format, and tests, then frontend checks, halting the push upon any regression.

Does this pre-push verification work with both backend and frontend projects?

Yes, pre-push verification works with both backend and frontend projects in a monorepo. It applies backend lint, format, and tests, followed by frontend type-check, lint, and build steps in order.

What steps are included in a full pre-push code quality verification pipeline?

A full pre-push verification pipeline includes backend lint and format, backend tests with coverage, and frontend type-check and build. These steps execute sequentially to catch regressions before code is pushed.