code-quality

Automate code quality tooling setup for Python and JavaScript/TypeScript projects.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/rarestg/rarestg-skills --skill code-quality-rarestg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/rarestg/rarestg-skills/tree/main/skills/code-quality
Command: npx skills add https://github.com/rarestg/rarestg-skills --skill code-quality-rarestg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents the common pain point of adding code quality tooling late in a project, which often results in massive, unmanageable fix-it commits. It ensures formatting, linting, and type checking are set up from the start.

Core Features & Use Cases

  • Ecosystem Detection: Automatically identifies Python or JavaScript/TypeScript projects.
  • Tool Setup: Configures linters (Ruff, Biome), formatters (Ruff, Biome), type checkers (mypy, tsc), and pre-commit hooks (pre-commit, lefthook).
  • Standard Command Contract: Ensures format, lint, typecheck, check, and check:fix commands are available.
  • Use Case: When starting a new Python project, use this skill to set up Ruff for linting/formatting and pre-commit hooks, ensuring all code adheres to standards from the very first commit.

Quick Start

Use the code-quality skill to set up linting and formatting for a new Python project.

Frequently Asked Questions about code-quality

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

FAQPage Schema
How do I set up code quality tooling for a new Python project?▼

To set up code quality for a new Python project, this configures Ruff for linting and formatting, mypy for type checking, and pre-commit hooks to enforce standards from the first commit.

What's the best way to automate linting and formatting in JavaScript and TypeScript?▼

Automating linting and formatting in JavaScript and TypeScript is handled by configuring Biome for formatting and linting, tsc for type checking, and lefthook for pre-commit hooks.

Why should I add pre-commit hooks at project initialization instead of later?▼

Adding pre-commit hooks at initialization prevents massive unmanageable fix-it commits later, ensuring a consistent code quality baseline and preventing future technical debt from the start.

Does this code quality setup provide standard commands for linting and type checking?▼

Yes, the code quality setup ensures standard command contracts are available, providing format, lint, typecheck, check, and check:fix commands to maintain coding standards across projects.

Can I use Ruff and Biome together for formatting and linting?▼

Yes, you can use Ruff for Python and Biome for JavaScript and TypeScript, as the setup automatically detects the ecosystem and configures the appropriate linters and formatters.