mav-bp-linting

Standardize linting rules across TypeScript, Python, and Go projects.

10|2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/thermiteau/maverick --skill mav-bp-linting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mav-bp-linting
Source: https://github.com/thermiteau/maverick/tree/main/skills/mav-bp-linting
Command: npx skills add https://github.com/thermiteau/maverick --skill mav-bp-linting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Linting standards help teams automate code quality checks and prevent style drift.

Core Features & Use Cases

  • Linter selection guidance
  • Formatting vs linting separation
  • CI integration and rule configuration
  • Use Case: A project standardizes lint rules across modules to ensure consistent code quality.

Quick Start

Configure a project with a single source of truth for lint rules and enable automated checks in CI.

Frequently Asked Questions about mav-bp-linting

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

FAQPage Schema
How do I standardize ESLint rules across multiple TypeScript projects?

Standardize linting by defining a single source of truth for ESLint configuration and enforcing those rules automatically across all project modules to maintain consistent code quality.

What is the best way to separate code formatting from linting in CI pipelines?

Separating formatting from linting involves using dedicated tools for style formatting while reserving the linter strictly for error-level rule checks, ensuring CI pipelines enforce code quality without overlapping style violations.

Can I enforce consistent linting standards for Python and Go projects?

Yes, you can enforce consistent linting standards across Python and Go projects by selecting a central linter for each language and applying project-wide configuration guidance to automate code quality checks.

How do I configure CI pipelines to fail on linting errors automatically?

Configure CI pipelines to fail automatically by integrating linter checks that enforce error-level rules, ensuring code quality violations stop the build process before deployment.

Why should I separate formatting from linting in my code quality automation?

Separating formatting from linting prevents style debates from cluttering code reviews, allowing the linter to focus on catching logic errors and potential bugs while a formatter handles stylistic consistency.