code-quality-pipeline

Orchestrate code-quality workflows with Pareto-based auto-fixes and Vitest test generation.

Updated Oct 1, 2025
One-click install
npx skills add https://github.com/j0KZ/mcp-agents --skill code-quality-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality-pipeline
Source: https://github.com/j0KZ/mcp-agents/tree/main/starter-kit/template/.claude/skills/code-quality-pipeline
Command: npx skills add https://github.com/j0KZ/mcp-agents --skill code-quality-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a repeatable, automation-driven workflow for improving code quality, combining smart-reviewing, Pareto-based auto-fixes, and automated test generation.

Core Features & Use Cases

  • 5-Step Quality Pattern: Assessment, smart review, auto-fix, test generation, re-review
  • Auto-Fix with Pareto: Safe fixes applied automatically
  • Test Generation: Create tests to increase coverage
  • CI/CD Quality Gate: Pre-PR gates and post-change checks

Quick Start

Use the quick start workflow: Batch review changed files with strict severity, apply safe auto-fixes, then generate tests for updated code.

  • Tool: batch_review
  • Input: { "filePaths": ["file1.ts","file2.ts"], "config": { "severity": "strict" } }

Frequently Asked Questions about code-quality-pipeline

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

FAQPage Schema
How do I automatically improve code quality in TypeScript and JavaScript files?

Code-quality-pipeline orchestrates a 5-step workflow that assesses, reviews, auto-fixes, and generates tests for TypeScript and JavaScript files. It applies safe Pareto-based fixes automatically and creates tests to increase coverage, improving quality before pull requests.

Can I automate code review and fixes before merging pull requests?

Yes. Batch review changed files with severity configuration, apply safe auto-fixes with backups, then re-review results. The workflow integrates with pull request gates to catch issues before merge.

How do I generate tests automatically for updated code?

The pipeline generates tests using Vitest after applying auto-fixes to changed files. Tests are created to increase coverage on modified code, reducing manual test-writing overhead.

What's the best way to handle code quality checks when CI/CD tests fail?

Run the quality pipeline on changed files with strict severity settings to categorize issues by severity, apply safe fixes, and generate tests. This addresses quality gate failures systematically before redeployment.

Does this work for large-scale codebase audits?

Yes. Batch review multiple TypeScript and JavaScript files in a single workflow, apply severity-based fixes, and generate tests across the audit scope. It scales to significant refactors and comprehensive audits.

What safe fixes does the pipeline apply automatically?

The pipeline applies Pareto-based auto-fixes—high-impact, low-risk corrections identified by severity. All fixes include backups, ensuring changes are reversible if needed.