Rechercher

PythonReactSEOPDF
GitHub Skill

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.

aiskillstore☆ 122 Étoiles du dépôt6 Forks du dépôt

Installation

Suivez les instructions du dépôt pour votre agent. Consultez les fichiers et dépendances avant l’installation.

Voir la source ↗Guides

Instructions

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

Exemples

Consultez les exemples du dépôt source.

Voir la source ↗

Historique source

Date d’indexation
2026-01-20
Mise à jour de l’index
2026-01-28
Branch
main

Les dates concernent ce répertoire. Consultez le dépôt pour l’historique du code.

GitHub ↗

chat Comments (0)

chat_bubble_outline

No comments yet. Be the first to share your thoughts!