lint

Format and lint Python, frontend, Markdown, and YAML files in monorepos.

9|2|Updated Nov 29, 2024
One-click install
npx skills add https://github.com/bbvch-ai/aihub-core --skill lint-bbvch-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/bbvch-ai/aihub-core/tree/main/.claude/skills/lint
Command: npx skills add https://github.com/bbvch-ai/aihub-core --skill lint-bbvch-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually formatting and linting code across multiple scopes in a large monorepo is time-consuming and prone to human error, especially when enforcing consistent style rules across Python, frontend, Markdown, and YAML files.

Core Features & Use Cases

  • Cross-Scope Automation: Runs standardized formatting and linting workflows across all Python packages, frontend web scopes, Markdown files, and YAML configurations in the monorepo.
  • Auto-Fix & Repeat: Automatically applies safe fixes for common lint and formatting issues, then re-runs checks until zero errors remain.
  • Use Case: Before submitting a PR, use this skill to ensure all code, documentation, and configuration files meet project style guidelines without manually running separate commands for each scope.

Quick Start

Use the lint skill to format and lint all code, Markdown, and YAML files across the entire aihub-core monorepo until no errors remain.

Frequently Asked Questions about lint

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

FAQPage Schema
How do I automate code formatting and linting across a monorepo?

Automating monorepo code formatting and linting requires orchestrating tools like ruff, ESLint, mdformat, and yamlfix across all Python, frontend, Markdown, and YAML scopes. This eliminates manual style correction by running repeatable workflows that apply safe fixes until zero errors remain.

Can I use ruff and ESLint together for pre-commit validation in a monorepo?

Yes, ruff and ESLint can be orchestrated together for pre-commit validation in a monorepo. Standardized workflows apply ruff for Python packages and ESLint for frontend web scopes, ensuring consistent code style and lint rule compliance across different project scopes automatically.

What's the best way to format Markdown and YAML configurations before a PR?

Formatting Markdown and YAML configurations before a PR is best handled by automating mdformat and yamlfix. Running these tools across the monorepo standardizes documentation formatting and configuration styles without requiring manual file-by-file corrections.

Does automated linting fix formatting errors repeatedly until they pass?

Automated linting applies safe fixes for common formatting and lint issues, then re-runs validation checks repeatedly until zero errors remain. This auto-fix and repeat cycle ensures PR-ready code meets consistent style guidelines without manual intervention.

How do I prepare a monorepo for code review without running separate lint commands?

Preparing a monorepo for code review without separate lint commands involves orchestrating cross-scope formatting and linting in a single workflow. This automatically validates Python, frontend, Markdown, and YAML files to satisfy consistent code style and lint rule compliance requirements.

Why does manual monorepo formatting fail to enforce consistent code style?

Manual monorepo formatting fails to enforce consistent code style because it is time-consuming and prone to human error across multiple scopes. Automating ruff, ESLint, mdformat, and yamlfix orchestration eliminates manual style correction work and ensures error-free, repeatable compliance.