skills.rest
alvis
alvisCOMMUNITY
Explore all skills by this author →
Website𝕏@alvishttangGitHub

lint

Enforce coding standards mechanically across source files with scanning, batching, and verification.

4|1|Updated Jul 31, 2025
Search Tags:#code quality#typescript#static analysis#coding standards#formatting#dead code#lint
One-click install
npx skills add https://github.com/alvis/.agents --skill lint-alvis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/alvis/.agents/tree/main/plugins/coding/skills/lint
Command: npx skills add https://github.com/alvis/.agents --skill lint-alvis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ts-morph, and includes scripts (resource) and references (resource) components.

What problem does it solve? Keeping a codebase consistent with coding standards is tedious and error-prone when done by hand, especially across large or multi-language repositories. This Skill automates mechanical lint-error correction, standards enforcement, and consistent formatting across a selected scope of source files. ## Core Features & Use Cases - Scoped lint enforcement: Run against uncommitted changes by default, the whole repository, or a specific file, directory, or glob, with automatic exclusion of ignored, generated, and vendor files. - Pre-flight unused-code scan: Optionally detect and remove confirmed dead code before linting, with per-finding user confirmation. - Type-aware analysis: Runs package-wide TypeScript analysis to surface type-reuse candidates and shared-type extraction proposals, confirmed with you before any edit. - Extensible profiles: Framework plugins can extend it with a portable profile that adds standards, scanners, and exclusions without changing the report shape. - Use Case: Before opening a pull request, run the lint skill on your uncommitted changes to fix style violations, prune dead code, and verify project lint, type, and test checks all pass. ## Quick Start Ask the assistant to lint the uncommitted changes in this repository and fix any coding standards violations it finds.

Frequently Asked Questions about lint

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

FAQPage Schema
How do I lint only my uncommitted changes in a repository?▼

Run the lint skill with no arguments; it defaults to the repository root with --scope=uncommitted, covering unstaged, staged, and untracked files. You can also pass a file, directory, or glob as a specifier to narrow the target set.

How to enforce coding standards across multiple programming languages?▼

The skill applies generic standards to eligible source files including TypeScript, JavaScript, Python, Go, Rust, Ruby, Java, Kotlin, Swift, C, C++, C#, PHP, and shell scripts. It selects standards automatically based on discovered languages and runs project lint, type, and focused test checks after edits.

Can I extend linting with framework-specific rules?▼

Yes, a framework plugin can pass an absolute-path profile that narrows eligible files, adds standards and scanners, defines exclusions, and supplies a report label. The profile cannot replace generic standards, the generic scanner, verification, or the report shape.

Does the lint skill modify configuration files or install tooling?▼

No, it explicitly does not modify configuration files, install or update lint tooling, or author lint rules. It also skips binary, gitignored, generated, and vendor files, and behavior-changing repairs belong to the separate fix skill.

What happens when linting finds unused or dead code?▼

Unless --skip-unused is set, a pre-flight scan detects unused code project-wide and presents each finding for your Remove or Keep confirmation. Only confirmed-unused items are deleted, and scan, removed, and kept counts appear in the final report.

Why does the lint report show partial instead of success?▼

A partial status means some issues remain unresolved, such as pending shared-type extraction decisions or unknown analysis candidates. Success means violations were fixed, while compliant is reserved for a clean pass with no edits needed.

Related Skills

Explore More Software Engineering Skills→
EtanHeyEtanHey

catchup-recent

Review staged and unstaged Git changes with git status --short.

Community
Basic
0xjax0xjax

code-reviewer

Automate code reviews to identify security, performance, and quality issues.

Community
Intermediate
AbildtoftAbildtoft
2

kramme:verify

Run formatting, linting, type-checking, builds, and tests on affected code.

Community
Intermediate
Brite-NitesBrite-Nites

code-quality

Automate ESLint, Prettier, Ruff, and mypy configuration generation for multi-language projects.

Official
Advanced