code-quality

Configure linting, test coverage thresholds, and CI quality gates.

4|2|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/saitarrun/devforge-ai --skill code-quality-saitarrun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/saitarrun/devforge-ai/tree/main/skills/code-quality
Command: npx skills add https://github.com/saitarrun/devforge-ai --skill code-quality-saitarrun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the common problem of inconsistent code quality, missed security vulnerabilities, and unreliable CI pipelines that result from a lack of standardized, enforced development standards across teams.

Core Features & Use Cases

  • Static Code Standards Enforcement: Configures linting, naming conventions, complexity limits, and DRY checks for JavaScript, TypeScript, Python, Go, and Java projects.
  • Testing & Coverage Setup: Implements a 70/20/10 testing pyramid with 80% global coverage thresholds (95% for critical paths) and F.I.R.S.T. test quality principles.
  • DevSecOps & CI Guardrails: Integrates SAST, SCA, and secret detection scans, plus blocking pre-commit hooks and GitHub Actions quality gates to prevent low-quality or vulnerable code from being merged.
  • Use Case: A development team can use this Skill to standardize code quality across their monorepo, automatically block PRs with lint errors or low test coverage, and catch security vulnerabilities before they reach production.

Quick Start

Use the code-quality skill to set up end-to-end code quality standards, including linting rules, test coverage thresholds, and blocking CI/CD quality gates for your project.

Frequently Asked Questions about code-quality

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

FAQPage Schema
How do I enforce code quality standards and CI guardrails across multiple programming languages?

You can enforce code quality standards by applying standardized linting, naming conventions, and complexity limits across JavaScript, TypeScript, Python, Go, and Java projects. This ensures consistent code and eliminates inconsistent formatting across diverse repositories.

How do I set up CI/CD quality gates to block pull requests with low test coverage?

You can set up CI/CD quality gates using GitHub Actions with blocking merge rules. This integrates a 70/20/10 testing pyramid and enforces 80% global coverage thresholds, or 95% for critical paths, to automatically block low-quality PRs.

What is the best way to integrate DevSecOps scans like SAST and secret detection into my workflow?

Integrating DevSecOps scans involves adding SAST, SCA, and secret detection directly into your pre-commit hooks and CI pipelines. This catches security vulnerabilities early and prevents vulnerable code from ever reaching production environments.

Can I use pre-commit hooks to run linting and prevent broken code from being committed locally?

Yes, you can configure blocking pre-commit hooks to run linting checks locally before code is pushed. This prevents broken CI pipelines by catching formatting errors and quality violations during local development.

Does this code quality approach support monorepo environments with varying coverage thresholds?

Yes, this approach supports monorepo environments by applying standardized rules while allowing specific 95% coverage thresholds for critical paths. It maintains a standard 80% global baseline while enforcing strict quality gates across different modules.

Why should I implement F.I.R.S.T. test quality principles instead of just basic test coverage?

Implementing F.I.R.S.T. test quality principles ensures your tests are Fast, Independent, Repeatable, Self-validating, and Timely. This provides reliable test suite setup beyond simple coverage metrics, preventing flaky tests and broken CI pipelines.