# Lint Suite

> Run project linters and fix findings repo-wide

- Skill: `emaraschio/lint-suite` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add emaraschio/lint-suite`
- Raw SKILL.md: https://api.skillmd.com/api/skills/emaraschio/lint-suite/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: emaraschio (https://skillmd.com/u/emaraschio)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/emaraschio/lint-suite

---

## Overview

Run project linters, apply fixes, and ensure the codebase meets formatting and
style requirements before merging changes.

## Steps

1. **Execute linters**
    - Run the standard lint command with autofix enabled if available
    - Capture any remaining errors or warnings from the output
    - Identify files requiring manual attention
2. **Resolve findings**
    - Apply targeted fixes, keeping edits minimal and idiomatic
    - Refactor repeated issues such as unused variables or long functions
    - Update configuration or suppressions only when justified
3. **Verify cleanliness**
    - Re-run the lint command to ensure a zero-issue result
    - Spot-check key files for formatting and readability
    - Stage the changes with clear commit messages when satisfied

## Lint Checklist

- [ ] Linter executed with latest config
- [ ] Autofix results reviewed
- [ ] Manual issues resolved
- [ ] Final lint run passes cleanly
- [ ] Changes staged or ready for PR

## Guardrails

- Fix the underlying issue; do not disable rules to pass.
- Re-run the linter to verify a zero-issue result before finishing.
- Do not commit, push, merge, or run production scripts without consent.