Code Review
Steps
- Identify the changed files or requested review scope.
- Read
references/findings-format.mdbefore producing review output. - Inspect behavior, tests, compatibility, security, docs, and maintenance risk before style preferences.
- If the review scope includes security-sensitive code, configuration, dependencies, shell execution, filesystem writes/deletes, network/auth/TLS behavior, secrets/env handling, Docker helpers, or CI/security tooling, consult
$security-auditand the smallest matching security reference; keep this skill's findings format. - Verify claims against concrete file and line references whenever possible.
- When code review is the final response, use the exact structure in
references/findings-format.md; do not add, remove, rename, or reorder sections. - When another skill embeds this review, preserve findings, open questions, testing gaps, and summary facts in the caller's output format.
References
- Read
references/findings-format.mdfor review priorities, output format, and what to say when no issues are found.
Source: alexfalkowski/bin — distributed by TomeVault.