Receber por email
← Voltar para o catálogo

run-linters

Run linters after code changes to verify code quality. Use this skill after completing code modifications to catch and fix any linting issues.

367estrelas
Atualizado há 4 meses

Ver no GitHub ↗

Como adicionar

/plugin marketplace add aiskillstore/marketplace

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/run-linters/svg)](https://www.skillteca.com.br/skills/run-linters)

Skills relacionadas

Ver todas de Segurança →

Alerta por categoria

Receba novas skills de Segurança toda segunda

1 email curto, só com as skills novas de Segurança. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Run Linters

Execute linters after code changes are complete to ensure code quality and consistency.

When to Use

  • After completing a set of code changes (not after each small edit)
  • Before creating a commit or PR
  • When asked to verify code quality

Step 1: Run Linters

Execute the linters command which auto-detects active linters in the current repository and runs them with proper configurations:

linters

Step 2: Analyze Results

  • If no issues: Report success and proceed
  • If issues found: Continue to Step 3

Step 3: Fix Issues

For each issue reported:

  1. Read the affected file
  2. Understand the linting error
  3. Fix the issue using Edit tool
  4. Re-run linters to verify the fix

Repeat until all issues are resolved.

Important Rules

  • Do NOT run after every small change - wait until a logical set of changes is complete
  • Fix all issues before reporting completion
  • If a linting rule seems incorrect, ask the user before disabling it
Compartilhar X LinkedIn