lint
Linting
Linter detection
Check package.json devDependencies:
@biomejs/biome→npm run check/ fix:npm run check --writeoxlint→npm run lint/ fix:npm run lint --fixeslint(default) →npm run lint/ fix:npm run lint:fix
Workflow
- Detect linter from devDependencies
- Run lint command
- For fixes: run fix variant (only when requested)
- Report
file:linereferences for all errors
Rules
- Use project's
package.jsonscripts - Never use
npxdirectly - Don't auto-fix unless requested
Error Handling
- If no lint script found in
package.json→ checkscriptsfor alternative names (check,lint:check); report if none exist - If linter exits with parse errors → report each file-level parse error separately with
file:line - If linter config file is missing → report which config file is expected and stop
More from helderberto/skills
ship
Commit and push changes using atomic commits. Use when user asks to "ship", "commit and push", or requests committing and pushing changes. Don't use for creating pull requests or reviewing changes before committing.
45refactor-plan
Create structured refactoring plans. Use when user wants to plan a refactor, needs a refactoring strategy, or mentions breaking down large changes into small commits. Don't use for implementing code changes directly, small one-line fixes, or renaming a single variable.
44tdd
Guides test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants test-first development, or requests TDD workflow. Don't use for writing tests after implementation, adding tests to existing untested code, or one-off test fixes.
40coverage
Check test coverage for unstaged changes. Use when user asks to "check coverage", "/coverage", or wants to see which unstaged changes lack test coverage. Don't use for projects without lcov coverage output, running the full test suite without coverage, or checking coverage of already-committed changes.
38e2e
Write end-to-end tests for user flows using Cypress. Use when user asks to "write e2e tests", "/e2e", "add Cypress tests", or wants to test a user flow end-to-end. Don't use for unit tests, component tests, or projects using Playwright, Puppeteer, or other non-Cypress frameworks.
29perf-audit
Audit frontend bundle size and performance. Use when user asks to "audit performance", "/perf-audit", "analyze bundle", "check bundle size", or wants to find performance bottlenecks. Don't use for backend performance, database query optimization, or projects without a frontend build step.
29