code-quality

Detect linting and formatting tools and generate compatible configurations.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/BrunoAMSilva/my-config --skill code-quality-brunoamsilva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/BrunoAMSilva/my-config/tree/main/coding/skills/code-quality
Command: npx skills add https://github.com/BrunoAMSilva/my-config --skill code-quality-brunoamsilva

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Projects often suffer from inconsistent code style, conflicting linter/formatter setups, and fragile CI quality checks that cause developer friction and wasted time. This Skill provides unified, context-aware guidance to detect existing tools and prescribe compatible configurations so teams can enforce reliable, automated code quality.

Core Features & Use Cases

  • Context-aware detection: Inspect package.json and config files to choose ESLint, Prettier, Biome, or oxc patterns that match the repository.
  • Decision guidance: Follow a decision tree for new projects, migrations, or mixed-tool setups (ESLint + Prettier, Biome, oxc).
  • Recommended configs & scripts: Provide starter configs, package.json scripts for lint/format/check, and CI integration patterns.
  • Editor and CI integration: Advise on format-on-save, LSP/editor plugins, pre-commit hooks, and GitHub Actions for automated checks.
  • Migration & edge cases: Strategies for monorepos, legacy tooling, and incremental migrations with minimal disruption.

Quick Start

Use the code-quality skill to inspect the repository for existing lint/format tools and generate a recommended configuration and scripts that integrate with CI and editors.

Frequently Asked Questions about code-quality

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

FAQPage Schema
How do I configure ESLint and Prettier together without rule conflicts?▼

To configure ESLint and Prettier without conflicts, use context-aware detection to apply recommended configurations that separate linting rules from formatting rules, ensuring compatible setups.

What is the best way to migrate a JavaScript project to Biome for linting and formatting?▼

Migrating to Biome for linting and formatting involves following a decision tree to replace existing ESLint and Prettier configs, generating starter configs, and updating package.json scripts incrementally.

How do I integrate linting and formatting checks into GitHub Actions CI/CD?▼

Integrate linting and formatting checks into CI/CD by adding package.json scripts for lint and format checks, then configuring GitHub Actions workflows to run these automated quality checks on pull requests.

Can I use oxc for linting in an existing TypeScript monorepo?▼

Yes, you can use oxc for linting in a TypeScript monorepo by applying migration strategies designed for legacy tooling and mixed-tool setups to minimize disruption across your packages.

Why does my code formatting break when switching between different editor plugins?▼

Formatting breaks when switching editor plugins due to conflicting linter and formatter configurations, which you can resolve by standardizing format-on-save settings and applying unified, context-aware tool configurations.

Do I need both ESLint and Prettier for a new JavaScript project?▼

You do not necessarily need both ESLint and Prettier for a new JavaScript project; a decision tree can help you choose a single unified tool like Biome or oxc to handle both linting and formatting.