FO

formatting-linting-and-commits

Standards for maintaining code quality and release workflows in a monorepo environment.

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.zip

Installs 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
Beginner

Key capabilities

  • Ensure code output is compatible with Prettier settings.
  • Follow ESLint guidance for TypeScript files.
  • Use conventional commit messages.
  • Utilize changesets for versioned changes.
  • Prefer workspace scripts (`turbo run …`) in monorepos.
  • Avoid per-package drift in tooling choices.

How it works

The skill defines repository hygiene standards, including Prettier and ESLint compliance, conventional commit messages, and changesets-friendly workflows. It emphasizes using workspace scripts in a pnpm/turbo monorepo.

Inputs & outputs

You give it
Code changes in a pnpm/turbo monorepo
You get back
Formatted code, lint-compliant TypeScript files, conventional commit messages, and versioned changes

When to use formatting-linting-and-commits

  • Format code per project standards
  • Lint TypeScript files
  • Generate conventional commit messages
  • Manage version changes with changesets

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.

When not to use it

  • When hand-formatting large sections of code instead of running formatters.
  • When disabling ESLint rules casually without explanation.
  • When not working in a pnpm/turbo monorepo environment.

Limitations

  • The skill is designed for pnpm/turbo monorepos.
  • The skill requires conventional commit messages.
  • The skill enforces Prettier and ESLint compliance.

How it compares

This skill establishes specific, enforced standards for code formatting, linting, and commit messages within a pnpm/turbo monorepo, ensuring consistency and maintainability across the project.

Compared to similar skills

formatting-linting-and-commits side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
formatting-linting-and-commits (this skill)05moNo flagsBeginner
dependency-upgrade265moReviewIntermediate
testing-workflow169moReviewIntermediate
fix56moNo flagsBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry