lint-fixer
Fix lint issues with project lint workflow
Lint failures slow down code reviews and block releases. This skill runs the project lint workflow and guides fixes while keeping code behavior unchanged.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "lint-fixer". Please fix lint errors after my last commit
Expected outcome:
- Ran npm run lint and grouped issues by tool
- Applied Biome and oxlint auto fixes
- Left two tsgo type errors for manual review
- Re ran lint and confirmed style issues are resolved
Using "lint-fixer". My CI pipeline is failing on lint
Expected outcome:
- Identified 5 style issues from Biome
- Auto fixed formatting issues
- Found 2 secretlint warnings requiring review
- Remaining issues need manual TypeScript attention
Using "lint-fixer". Check if there are any secrets in my code
Expected outcome:
- Ran secretlint as part of npm run lint
- No credentials or secrets detected
- All other lint checks passed
- Code is safe to commit
Security Audit
SafePure documentation skill with no executable code. Contains only markdown documentation and JSON metadata files. The static findings are all false positives triggered by tool names, license identifiers, and hash fields in documentation - not actual malicious code or command execution. This skill describes a legitimate lint-fixing workflow.
Risk Factors
🌐 Network access (1)
📁 Filesystem access (1)
⚙️ External commands (10)
Quality Score
What You Can Build
Pre merge lint cleanup
Fix style and lint errors before opening a pull request.
Team lint consistency
Apply standard lint fixes after shared refactors across the codebase.
Reduce CI lint failures
Guide contributors to resolve lint errors that block the CI pipeline.
Try These Prompts
Run npm run lint, list failures by tool, fix safe issues, and re run lint to confirm.
Run npm run lint, focus on tsgo errors, explain each fix, and keep behavior unchanged.
Run npm run lint, review secretlint results, and remove any detected secrets safely.
Run npm run lint, apply Biome and oxlint auto fixes, then re run lint and summarize remaining issues.
Best Practices
- Review auto fixes before committing changes to ensure they match intent
- Re run npm run lint after each fix round to track progress
- Run npm run test after lint passes to verify no breakage
Avoid
- Changing runtime behavior just to satisfy lint rules
- Ignoring secretlint findings without reviewing them
- Skipping the final lint rerun before committing