quality-tools

---

name: Quality Tools description: Tool definitions and usage patterns for code quality tools (ESLint, Prettier, tsc, linters). Agents reference this skill instead of inline tool definitions. version: 1.0.0

<best_practices> Run type checker before linter for faster feedback Verify with tests after auto-fixes Use project-specific configuration when available Report all issues with file:line locations Run incremental checks for large codebases Separate formatting from logic changes in commits </best_practices>

<anti_patterns> Auto-fixing without reviewing changes Review auto-fix changes, run tests after

<decision_tree name="tool_selection"> What type of quality check is needed? Use language-specific type checker (tsc, mypy, cargo check) Use linter (eslint, clippy, ruff) Use formatter (prettier, black, cargo fmt) Run in sequence: types → lint → format </decision_tree>

<related_skills> Run tests after quality fixes Integration with implementation workflow </related_skills>