Marketplace 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.

install

source · Clone the upstream repo

git clone https://github.com/aiskillstore/marketplace

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/aiskillstore/marketplace "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/cloud-officer/run-linters" ~/.claude/skills/aiskillstore-marketplace-run-linters && rm -rf "$T"

manifest: skills/cloud-officer/run-linters/SKILL.md

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:

Read the affected file
Understand the linting error
Fix the issue using Edit tool
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