fix

Fix lint errors and formatting issues using yarn, prettier, and linc.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/Chai-Un/wedding --skill fix-chai-un
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/Chai-Un/wedding/tree/main/.agents/skills/fix
Command: npx skills add https://github.com/Chai-Un/wedding --skill fix-chai-un

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses lint errors and formatting issues to ensure code quality and CI readiness before committing.

Core Features & Use Cases

  • Automated formatting: Run yarn prettier to fix formatting across changed files.
  • Lint verification: Run yarn linc to identify and report remaining lint issues.
  • CI readiness: Ensure commits are clean and CI-friendly by surfacing needed fixes before push.
  • Use Case: Before creating a pull request for a bug fix, run the tooling to automatically correct formatting and catch lint errors.

Quick Start

Run yarn prettier to fix formatting, then yarn linc to check lint, and address any remaining issues before committing.

Frequently Asked Questions about fix

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

FAQPage Schema
How do I fix lint and formatting errors before a commit?

To fix lint and formatting errors before a commit, run yarn prettier to automatically format changed files, then run yarn linc to identify and report any remaining lint issues that need manual correction.

What is the best way to ensure my code passes CI formatting checks?

The best way to ensure code passes CI formatting checks is to run automated formatting and lint verification locally before submission, using yarn prettier to format files and yarn linc to surface remaining CI readiness issues.

Do I need yarn to run prettier and linc for code formatting?

Yes, you need yarn installed to run prettier and linc for code formatting, as the automated formatting and lint verification workflow leverages yarn scripts to execute these tools and report remaining issues.

Does running prettier automatically resolve all lint errors in my codebase?

Running prettier does not automatically resolve all lint errors, as it only fixes formatting issues across changed files; you must run yarn linc afterwards to identify and manually address remaining lint errors before committing.

Can I use this to verify lint issues before creating a pull request?

Yes, you can use this to verify lint issues before creating a pull request by running yarn linc to identify remaining problems after yarn prettier formats the code, ensuring your commits are clean and CI-friendly.