From the author
Run targeted linting, formatting, and code quality checks on modified files. Use this to validate code style, type safety, security, and other quality metrics before committing. Supports running all checks or targeting specific checks on specific files for efficient validation.
Install
npx skills add Microck/ordinary-claude-skills --skill lint -a claude-code
Installs to .claude/skills/lint/ · Each command fetches the skill straight from GitHub with the open skills CLI.
No download: this skill’s licence (Custom or unclear) does not let us redistribute its files. The install commands fetch them from GitHub instead.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 78
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- ase-code-lintrse/aseLint source code for potential code quality problems. Use when the user wants to "lint" or "check" source code.Engineering★ 60
- rtl-lintinga5c-ai/babysitterRTL code quality checking and linting. Runs lint rules, identifies synthesis issues, detects inferred latches, and generates lint reports with waivers.Engineering★ 1.9K
- build-checkarcasilesgroup/ai-engineeringRun the project's objective quality gates — typecheck, lint, tests, and a production build, whatever this project actually uses — then diagnose any failure down to the file and root cause. Use before committing, opening a PR, or declaring work done, and whenever asked whether the code compiles, typechecks, lints, tests, or builds.Testing★ 61
- ase-spec-lintrse/aseLint the SpecBook-based specification (SPEC) for potential quality problems: its syntax, its formatting, its statements, the logical gaps of its model, and its completeness for an implementation. Use when the user wants to "lint" or "check" the "spec" or "specification".Planning★ 60
- trellis-checkfy-agent/fyagentComprehensive quality verification: spec compliance, lint, type-check, tests, cross-layer data flow, code reuse, and consistency checks. Use when code is written and needs quality verification, before committing changes, or to catch context drift during long sessions.Testing★ 219
- run-nx-checkseai-org/agent-toolkitRun nx format, lint, typecheck, test, and build on affected or specified projects, then fix unambiguous failuresTesting★ 66
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in