Lint
My personal SDLC toolbelt for AI coding agents — PRD to ship.
npx -y skills add helderberto/agent-skills --skill lintAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Run linting and formatting checks. Use when user asks to "run linter", "/lint", "check linting", "fix lint errors", or requests code linting/formatting. Don't use for running tests or type-checking only.
SKILL.md
1.3 KB, as published. Nobody here has run it
Linting
Run the project's linter/formatter — detect it, don't assume a toolchain.
Detection
Prefer a task the project already defines, then fall back to the ecosystem tool:
| Ecosystem | Check | Fix |
|---|---|---|
| Node | package.json lint (eslint/biome) | lint:fix |
| Python | ruff check / flake8 | ruff check --fix |
| Go | golangci-lint run / gofmt -l | gofmt -w |
| Rust | cargo clippy / cargo fmt --check | cargo fmt |
| else | Makefile / CI lint target | — |
Workflow
- Detect the linter (project task first, then ecosystem default)
- Run the check command
- For fixes: run the fix variant (only when requested)
- Report
file:linereferences for all errors
Rules
- Prefer the project's defined task over a raw tool call
- Never invent a linter the project doesn't use
Error Handling
- If no linter or task found → report which config/task is expected and stop
- If the linter exits with parse errors → report each file-level parse error separately with
file:line - If the linter config is missing → report which config is expected and stop