fix

Fixes code formatting with Prettier and checks remaining lint errors before committing.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/prabaljainn/my-claude-code-setup --skill fix-prabaljainn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/prabaljainn/my-claude-code-setup/tree/main/claude/skills/fix
Command: npx skills add https://github.com/prabaljainn/my-claude-code-setup --skill fix-prabaljainn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Lint errors and formatting inconsistencies cause CI failures and slow down code review. This Skill automates the pre-commit cleanup routine so your code passes CI checks on the first push. ## Core Features & Use Cases - Automated Formatting: Runs yarn prettier to fix formatting on changed files. - Lint Verification: Runs yarn linc to surface remaining lint issues that need manual fixes. - CI Readiness: Reports unresolved problems before you commit, preventing failed CI runs. - Use Case: Before committing a feature branch, invoke the skill to auto-format your changes and get a list of any lint errors that still need manual attention. ## Quick Start Ask the assistant to run the fix skill to format my changed files and check for remaining lint errors before I commit.

Frequently Asked Questions about fix

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

FAQPage Schema
How do I fix lint errors before committing code?▼

Run the fix skill, which executes yarn prettier to auto-format changed files and then yarn linc to check for remaining lint issues. Any errors that cannot be auto-fixed are reported so you can resolve them manually before committing.

How to auto-format changed files with Prettier in a yarn project?▼

Run yarn prettier, which formats only the files you have changed rather than the entire codebase. This keeps formatting fast and avoids unrelated diffs in your pull request.

Does Prettier fix all lint errors automatically?▼

No. Prettier only handles formatting such as spacing and line breaks. Lint errors reported by yarn linc, like unused variables or rule violations, must be fixed manually before the code will pass CI.

Why does CI fail even after running Prettier?▼

CI fails when lint errors remain after formatting. Prettier only fixes style, so you must run yarn linc afterward and manually resolve any reported issues before pushing your commit.

When should I run lint and format checks in my workflow?▼

Run them right before committing code. This catches formatting drift and lint violations early, ensuring your branch passes CI checks without extra fix-up commits.