name	code-quality
description	Code quality principles covering comments, linter suppressions, and formatting. Use when writing or reviewing code to enforce self-documenting style, justified suppressions, and project-standard formatting.

Code Quality Skill

Use this skill when writing or reviewing code in the narrowed Codex scope.

Use comments for:

all main interfaces, types, and data structures, using short notes that clarify purpose, invariants, ownership, lifetime, valid states, or usage constraints
non-obvious design intent
complex algorithms where the approach is not immediately clear
TODOs with enough context to act on them later
test scenario setup where the behavior being exercised is otherwise hard to follow
public API documentation when required by the language or project

Avoid comments that restate the code or exist only to satisfy a comment quota.

Always explain why a suppression is necessary. Prefer fixing the code instead when the warning points to a real design issue.

Examples:

Apply the project's formatter to every modified file.

Prefer concrete findings over style-only commentary.
Raise style feedback only when it affects readability, maintainability, or project consistency.
Treat unexplained suppressions, stale comments, and missing formatting as quality defects.

Use references/code-review-checklist.md for the narrowed code-quality review checklist.

Use the reference docs for the detailed operating rules:

name	code-quality
description	Code quality principles covering comments, linter suppressions, and formatting. Use when writing or reviewing code to enforce self-documenting style, justified suppressions, and project-standard formatting.