FO
formatting-linting-and-commits
Repo hygiene standards: Prettier+ESLint compliance, conventional commits, and changesets-friendly workflow in a pnpm/turbo monorepo. Use before submitting changes to keep CI green.
Install
mkdir -p .claude/skills/formatting-linting-and-commits && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13840" && unzip -o skill.zip -d .claude/skills/formatting-linting-and-commits && rm skill.zipInstalls to .claude/skills/formatting-linting-and-commits
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Repo hygiene standards: Prettier+ESLint compliance, conventional commits, and changesets-friendly workflow in a pnpm/turbo monorepo. Use before submitting changes to keep CI green.180 charsno explicit “when” trigger
About this skill
Formatting, Linting, and Commits
Format is not optional
- Keep output compatible with Prettier settings (single quotes, semicolons).
- Don’t hand-format large sections; run formatters instead.
Follow ESLint guidance
- Keep TypeScript ESLint rules passing; don’t disable rules casually.
- If you must suppress, keep it narrow and explain intent.
Conventional commits + release tooling
- Use conventional commit messages (commitlint enforced).
- Use changesets for versioned changes where appropriate.
Monorepo discipline
- Prefer workspace scripts (
turbo run …) where configured. - Avoid per-package drift in tooling choices.