skills.rest
aspiers
aspiersCOMMUNITY
Explore all skills by this author →
Website𝕏@adamspiersGitHub

code-linting

Run project-specific linters and apply auto-fixes to code changes.

15|2|Updated Aug 16, 2025
Search Tags:#automation#linting#pre-commit#code-quality#static-analysis#lint
One-click install
npx skills add https://github.com/aspiers/ai-config --skill code-linting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-linting
Source: https://github.com/aspiers/ai-config/tree/main/.claude/skills/code-linting
Command: npx skills add https://github.com/aspiers/ai-config --skill code-linting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lint code according to repository guidelines to ensure consistency, quality, and faster review.

Core Features & Use Cases

  • Discovers and runs the appropriate linters for the project (JavaScript/TypeScript, Python, Shell, etc.)
  • Applies auto-fix when available, then reports remaining issues for manual review
  • Use case: after creating or modifying code, you run linting before commits to catch issues early

Quick Start

Run the linting workflow on your changed code to ensure it conforms with project standards.

Frequently Asked Questions about code-linting

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

FAQPage Schema
How do I run linters on code changes before committing?▼

You can run project-specific linters on code changes before committing by using an automated workflow that discovers, executes, and applies auto-fixes for configured linters across multiple languages.

What does static analysis linting do for multiple programming languages?▼

Static analysis linting enforces code quality and consistency across languages like JavaScript, TypeScript, Python, and Shell by running project-configured linters and reporting unresolved issues for manual review.

Can I use pre-commit hooks to automate code quality checks?▼

Yes, you can automate code quality checks during pre-commit by running repository-guided linters that apply auto-fixes when available and report remaining errors directly in the changed files.

Does this linting workflow support both Python and JavaScript code?▼

Yes, the linting workflow supports multiple languages including Python, JavaScript, TypeScript, and Shell by discovering and running the appropriate linters configured for your repository.

Why do I need to lint code according to repository guidelines?▼

You need to lint code according to repository guidelines to ensure structural consistency, maintain code quality standards, and accelerate the code review process by resolving issues before they are committed.

What is the best way to handle remaining linting issues after auto-fix?▼

The best way to handle remaining linting issues after auto-fix is to review the reported output, which provides exact file paths and line numbers for manual correction of violations that could not be resolved automatically.

Related Skills

Explore More Software Engineering Skills→
Probably-GroupProbably-Group
3

linter

Detect and fix code style issues in recently edited files using project linters.

Official
Intermediate
zaiyemeiyou404zaiyemeiyou404

requesting-code-review

Automate code review with pre-commit security scans and quality checks.

Community
Advanced
martimramosmartimramos
1

forge-lang-typescript

Standardize TypeScript projects with type checks, Jest or Vitest tests, ESLint, and Prettier.

Community
Intermediate
ondrej-svecondrej-svec
18

redteam

Generate failing tests that expose code, architecture, and security weaknesses.

Community
Advanced