code-review

Run format, lint, typecheck, and tests in sequence via npm scripts.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/mkrlabs/specflow --skill code-review-mkrlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/mkrlabs/specflow/tree/main/examples/.claude/skills/code-review
Command: npx skills add https://github.com/mkrlabs/specflow --skill code-review-mkrlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill bundles all essential quality gates (format, lint, typecheck, and tests) and runs them in a single pass, helping you catch issues early and keep code healthy.

Core Features & Use Cases

  • Single-shot quality gate: Executes format, lint, typecheck, and tests in order, stopping on the first failure to allow quick remediation.
  • Pre-commit / pre-push readiness: Ideal for git workflows to ensure commits and pushes meet project quality gates.
  • Consistency across environments: Ensures the same checks run in local and CI environments.

Quick Start

Run the bundled script to execute all checks in one shot.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I run all code quality checks in one go before committing?

To run all code quality checks in one go, execute a bundled script that sequentially runs format, lint, typecheck, and tests, stopping on the first failure for quick remediation.

What code quality checks should I run for a pre-push workflow?

For a pre-push workflow, you should run format, lint, typecheck, and tests in sequence to ensure commits meet project quality gates before pushing code.

Do I need Prettier and ESLint configured to run automated quality checks?

Yes, running automated quality checks requires your project's development environment to have Prettier, ESLint, TypeScript, and the test framework configured and accessible via npm scripts.

What is the best way to catch formatting and linting issues early in development?

The best way to catch issues early is running a single-shot quality gate that executes format, lint, typecheck, and tests in order, stopping on the first failure for quick remediation.

Why does my code quality workflow stop on the first test failure?

A quality workflow stops on the first test failure to allow quick remediation, executing format, lint, typecheck, and tests sequentially to identify and fix issues efficiently.

Can I use a single script to ensure consistency across local and CI environments for typecheck and tests?

Yes, running a bundled quality gate script ensures the same format, lint, typecheck, and test checks run in both local and CI environments, maintaining consistency.