fix

Name: fix
Author: facebook

Fix lint, formatting, and common code issues before passing CI.

Source

GitHub

Updated

2026-06-17

// securityCaution

Prompt only, no code
Open source

Summary

This skill appears to be a prompt-only workflow description with no required secrets and no declared remote endpoints, so overall risk is low. Its instructions suggest local command execution, but the material itself does not indicate extra privilege requests, data exfiltration, or obvious malicious behavior.

CredentialsLow risk

The material explicitly states that no keys or environment variables are required, and the README does not request any login, token, or external credential, so credential exposure and misuse risk is low.

Network egressLow risk

No remote endpoint is declared, and the content only references running `yarn prettier` and `yarn linc` locally; the material does not describe sending user data to external services.

Code executionCaution

The README explicitly instructs running local commands `yarn prettier` and `yarn linc`, which implies local code/process execution. This is a normal capability for a developer-oriented skill, but users should still note that these commands invoke project-local scripts and dependencies.

Data accessCaution

Per the instructions, it operates on repository files: `yarn prettier` modifies changed files and `yarn linc` reads project contents for checks. This access scope is consistent with the stated lint/formatting purpose, with no sign of overbroad authorization in the material.

Supply chainCaution

The material is marked open-source and sourced from GitHub, which helps auditability; however, the provided repository link has an unclear relationship to the skill name/description, and the listed community adoption is 0 stars with unknown maintenance status, leaving some source credibility uncertainty.

Recommendations

Use it only in a trusted repository and isolated dev environment, and verify what the `prettier`/`linc` scripts actually do in `package.json` first.
Review local uncommitted changes before running it to avoid formatting commands modifying unintended files.
If the skill source and repository link do not clearly match, verify the publisher identity and code provenance first.
Run with least privilege and, when possible, in an environment without sensitive credentials.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "fix" skill from askskill:
1. Download https://raw.githubusercontent.com/facebook/react/main/.claude/skills/fix/SKILL.md
2. Save it as ~/.claude/skills/fix/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Fix code before commit

Prompt

Please check this project for lint errors, formatting inconsistencies, and obvious syntax issues, then provide directly applicable fixes so it is more likely to pass CI before commit.

Expected

A file-by-file set of fixes or patches covering formatting, lint, and basic code issues.

Resolve formatting and lint failures

Prompt

Here is the CI failure log. Identify the issues and update the code, prioritizing formatter and linter failures, and explain the reason for each change.

Expected

Specific fixes for the reported errors, with explanations and recommendations for passing checks.

Clean up legacy code style

Prompt

Please clean up style issues in this legacy code, fixing naming, indentation, unused variables, and obvious low-risk problems while avoiding business logic changes.

Expected

A cleaner, more consistent version of the code with fewer warnings, plus notes on untouched higher-risk issues.

// docs

Fix Lint and Formatting

Instructions

Run yarn prettier to fix formatting
Run yarn linc to check for remaining lint issues
Report any remaining manual fixes needed

Common Mistakes

Running prettier on wrong files - yarn prettier only formats changed files
Ignoring linc errors - These will fail CI, fix them before committing