fix

This skill acts as an automated quality assurance agent specifically for the React repository, designed to bridge the gap between local development and CI/CD success. Its primary role is to ensure that codebase contributions adhere to strict formatting and linting standards, which are prerequisites for merging code. By streamlining the cleanup process, it helps developers focus on logic rather than tedious syntax adjustments, significantly reducing the turnaround time for pull request reviews.

The target audience includes contributors to the React project, maintainers, and developers interacting with React-related internals. It is particularly useful during the final stages of a feature implementation or bug fix when local linting errors or formatting inconsistencies might otherwise block CI pipelines. The agent leverages standard tooling like Prettier and project-specific linting configurations to maintain code homogeneity across the large-scale repository.

• Executes project-specific formatting via yarn prettier, focusing on changed files to ensure efficiency and minimize unnecessary diff noise.

• Runs yarn linc to identify and report remaining linting violations that require manual intervention or specific architectural fixes.

• Validates code compliance against established project standards before commit, ensuring high-quality pull requests.

• Provides feedback loops for developers, flagging common pitfalls like running formatters on irrelevant files or ignoring critical linc errors that trigger CI failures.

• Users should trigger this skill whenever a build fails during local testing or before initiating a pull request.

• The agent expects a working development environment with Yarn configured.

• Input typically involves a staged or modified codebase; output includes corrected formatting or a generated report of manual tasks required to pass linting.

• Constraint: Always ensure that you have reviewed the changes made by the automated formatter, as global formatting rules may occasionally conflict with highly specific manual intent in complex component structures.

• Note: Always prioritize fixing linc errors, as these represent non-negotiable CI gates. Ignoring these will result in failed workflows, necessitating additional commits and repeated review cycles.