code-quality-fix

Fix ESLint, Prettier, and import issues in JavaScript/TypeScript projects.

1|1|Updated Jun 28, 2025
One-click install
npx skills add https://github.com/DarkMonkDev/WitchCityRope --skill code-quality-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality-fix
Source: https://github.com/DarkMonkDev/WitchCityRope/tree/main/.claude/skills/code-quality-fix
Command: npx skills add https://github.com/DarkMonkDev/WitchCityRope --skill code-quality-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm, npx, eslint, prettier, git, and includes scripts (resource) components.

What problem does it solve?

Manually addressing ESLint errors, formatting inconsistencies, and import organization is a tedious, time-consuming task that distracts developers from core feature work.

Core Features & Use Cases

  • Automated Linting Fixes: Automatically resolves ESLint auto-fixable errors and warnings, such as missing semicolons, quote styles, and spacing issues.
  • Prettier Formatting: Applies consistent code formatting across TypeScript/JavaScript, JSON, and Markdown files.
  • Import Organization: Organizes import statements for improved readability and consistency.
  • Use Case: After a coding session, run this Skill to automatically clean up all auto-fixable ESLint and Prettier issues in your modified files, ensuring your code is pristine before committing.

Quick Start

Auto-fix all code quality issues in changed files.

Frequently Asked Questions about code-quality-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically fix ESLint and Prettier issues in my JavaScript or TypeScript project?

ESLint auto-fix and Prettier formatting automatically resolve linting errors, formatting inconsistencies, and organize imports. Run this Skill to clean up all auto-fixable issues in your codebase without manual intervention, ensuring consistent code quality before committing.

Can I fix code quality issues only in changed files instead of the entire codebase?

Yes, the --changed-only option processes only modified files, making it faster for incremental fixes. This is useful after development sessions or before creating pull requests when you want to clean up just your changes.

What does the --dry-run option do when fixing code quality issues?

The --dry-run option previews all fixes without applying them, letting you review what will change before committing. It reports which issues would be fixed automatically and which require manual attention.

Does this work with monorepos and multiple TypeScript or JavaScript projects?

Yes, this Skill is applicable to monorepos and scales across multiple JavaScript and TypeScript projects. It enforces environment checks like package.json presence and node_modules availability to handle complex project structures.

What's the difference between auto-fixable ESLint errors and issues that need manual fixes?

Auto-fixable ESLint errors like missing semicolons and quote styles are resolved instantly by this Skill. Issues requiring manual fixes are reported with exit codes so you can address them separately before your code meets quality standards.

Can I integrate code quality fixes into my Git workflow?

Yes, use the --no-verify option to bypass pre-commit hooks, or run this Skill after merges or when quality checks fail. It works seamlessly in development workflows to maintain clean code at any stage.