code-quality-management

Enforce Biome, ESLint, TypeScript, Vitest, and Playwright quality gates.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/d-oit/do-novelist-ai --skill code-quality-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality-management
Source: https://github.com/d-oit/do-novelist-ai/tree/main/.claude/skills/quality-engineer
Command: npx skills add https://github.com/d-oit/do-novelist-ai --skill code-quality-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies a comprehensive quality gate pipeline covering formatting, linting, type checking, unit tests, and end-to-end tests.

Core Features & Use Cases

  • Quality gates: orchestrates Biome, ESLint, TypeScript, Vitest, and Playwright checks.
  • CI readiness: ensures code meets quality standards before merging.
  • Daily workflow guidance: daily development hygiene checklist.

Quick Start

  1. Install necessary dev dependencies for Biome, ESLint, TypeScript, Vitest, and Playwright.
  2. Configure package.json scripts for lint, type-check, test, and end-to-end tests.
  3. Run a full quality gate sequence before committing.

Frequently Asked Questions about code-quality-management

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

FAQPage Schema
How do I set up automated code quality checks for a TypeScript React project?

Automated code quality checks combine formatting, linting, type checking, and testing. Install Biome for formatting, ESLint for React and TypeScript rules, configure TypeScript for type safety, set up Vitest for unit tests and Playwright for end-to-end tests, then orchestrate them through package.json scripts and Husky pre-commit hooks to enforce standards before code is committed.

What's the difference between Biome and ESLint for enforcing code quality?

Biome handles formatting and basic linting as a unified tool, while ESLint provides deeper rule customization for React and TypeScript-specific patterns. Using both together—Biome for consistency and ESLint for complex rules—creates a comprehensive quality gate that catches more issues than either alone.

How do I run quality checks in CI before merging code?

Configure package.json scripts for lint, type-check, test, and end-to-end tests, then add them to your CI pipeline. Husky pre-commit hooks with lint-staged run checks locally before commit, ensuring only code meeting all quality standards reaches CI and prevents merge until tests pass.

Can I use Playwright and Vitest together for comprehensive testing?

Yes. Vitest runs unit tests for individual functions and components, while Playwright runs end-to-end tests across the full application workflow. Together they provide both fast isolated testing and real-world user-flow validation as part of your quality gate pipeline.

Do I need to configure ESLint separately if I'm using Biome?

Yes. While Biome handles formatting and basic linting, ESLint adds React and TypeScript-specific rule enforcement that Biome doesn't cover. Configure both to work alongside each other, with Biome running first for consistency and ESLint catching deeper pattern violations.

What happens if code fails the quality gates—can I fix it automatically?

Yes. Lint-fix workflows automatically correct formatting and common linting violations before commit. Husky with lint-staged applies fixes locally, and you can configure scripts to run fix commands as part of your development workflow, reducing manual corrections.