Automated summary
This skill runs Prettier formatting and then the project's lint check so issues are fixed before a commit or a CI run.
Strengths
- Very short, unambiguous three-step workflow
- Relies on the project's existing yarn scripts (prettier, linc) rather than invented commands
- Explicitly notes that linc errors will break CI
- Reports remaining manual fixes instead of pretending everything is resolved
Limitations
- Assumes `yarn prettier` and `yarn linc` already exist in package.json
- `yarn prettier` only formats changed files, so untracked files may be missed
- Describes no ESLint rules or config, so it won't help diagnose a specific lint finding
Use it right before committing or pushing, when you want to format the code and confirm it will pass CI.
Skip it on a project that doesn't use yarn or lacks the prettier and linc scripts.
Security analysis
SafeThe skill only instructs running standard yarn scripts (`yarn prettier` and `yarn linc`) for code formatting and linting. These are common development tasks with no destructive, exfiltrating, or obfuscated actions.
No concerns found
How this analysis is madeExamples
I'm about to commit — run prettier and linc and fix whatever lint errors remain.Format the files I changed with yarn prettier, then check lint and tell me what still needs manual fixes.CI failed on the lint step. Run yarn prettier then yarn linc and report the remaining issues.name: fix description: Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.
Fix Lint and Formatting
Instructions
- Run
yarn prettierto fix formatting - Run
yarn lincto check for remaining lint issues - Report any remaining manual fixes needed
Common Mistakes
- Running prettier on wrong files -
yarn prettieronly formats changed files - Ignoring linc errors - These will fail CI, fix them before committing
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/fix-lint-and-formatting-ms47vpv0/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/fix-lint-and-formatting-ms47vpv0' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/fix-lint-and-formatting-ms47vpv0/download' --output '.skill-downloads/fix-lint-and-formatting-ms47vpv0/SKILL.md.part' && mv '.skill-downloads/fix-lint-and-formatting-ms47vpv0/SKILL.md.part' '.skill-downloads/fix-lint-and-formatting-ms47vpv0/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/fix-lint-and-formatting-ms47vpv0/SKILL.md' && test -s '.skill-downloads/fix-lint-and-formatting-ms47vpv0/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/fix' && cp -R '.skill-downloads/fix-lint-and-formatting-ms47vpv0' '.claude/skills/fix'Cursor
test -f '.skill-downloads/fix-lint-and-formatting-ms47vpv0/SKILL.md' && test -s '.skill-downloads/fix-lint-and-formatting-ms47vpv0/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/fix' && cp -R '.skill-downloads/fix-lint-and-formatting-ms47vpv0' '.cursor/skills/fix'Codex
test -f '.skill-downloads/fix-lint-and-formatting-ms47vpv0/SKILL.md' && test -s '.skill-downloads/fix-lint-and-formatting-ms47vpv0/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/fix' && cp -R '.skill-downloads/fix-lint-and-formatting-ms47vpv0' '.agents/skills/fix'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/fix-lint-and-formatting-ms47vpv0'openskills read 'fix-lint-and-formatting-ms47vpv0'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/fix-lint-and-formatting-ms47vpv0/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.