coding-standards

Unify coding standards by applying a common baseline instruction during planning, development, and code reviews. This ensures consistent quality and testing policies across projects while still allowing project-specific references through optional directories.

Trigger coding quality and testing standards checks when planning, creating, or modifying code and test code, or during code reviews. Do not trigger it when simply reading code for understanding or editing documentation only.

The best way to enforce consistent code review guidelines is to apply a shared baseline instruction across all projects during the review phase. This aligns team quality expectations while permitting extended guidance via optional reference directories.

You need a valid SKILL.md file with frontmatter containing a name and description to set up team coding standards. Optional directories such as scripts, references, and assets can be included for extended project-specific guidance.

You can add project-specific coding and testing references using optional directories without breaking the shared baseline. The common instruction applies universally, while these directories provide extended, tailored guidance for individual projects.

Code review quality varies across projects without a common baseline instruction. Applying unified coding and testing standards during planning, development, and reviews enforces a consistent quality baseline, reducing discrepancies between project outputs.