spec-writing
This skill should be used when the user asks to "create a spec", "write a specification", "review a spec", "update a spec", "review spec organization", "split a spec", "add a page to spec", "remove a page from spec", "move requirements between pages", "add requirements", "review requirements", "update requirements", "delete requirements", "add tests", "add test cases", "review tests", "update tests", "delete tests", or needs guidance on spec structure, formatting, or spec writing best practices.
pre-commit
When setting up automated code quality checks on git commit. When project has .pre-commit-config.yaml. When implementing git hooks for formatting, linting, or validation. When creating prepare-commit-msg hooks to modify commit messages. When distributing a tool as a pre-commit hook.
holistic-linting
This skill should be used when the model needs to ensure code quality through comprehensive linting and formatting. It provides automatic linting workflows for orchestrators (format → lint → resolve via concurrent agents) and sub-agents (lint touched files before task completion). Prevents claiming "production ready" code without verification. Includes linting rules knowledge base for ruff, mypy, and bandit, plus the linting-root-cause-resolver agent for systematic issue resolution.
biome-js
This skill should be used when the user asks to "configure Biome", "extend biome config", "set up BiomeJS", "add biome overrides", "biome lint-staged", "fix biome errors", or mentions biome.jsonc, Biome linting, or Biome formatting configuration.
