code-review
Code Review
Overview
Perform comprehensive code review across multiple dimensions: Security, Quality, Performance, and Best Practices. Support two review modes: Git changes or specified files.
Core principle: Read and analyze, never modify code. Always provide concrete code references with specific recommendations.
Announce at start: "I'm reviewing the code and will save the report to docs/reviews/"
${languageInstruction}
Critical Constraints
- READ-ONLY - Do not edit any source code files
- ALWAYS CITE - Include
file:linereferences for all issues found - SAVE REPORT - Always save the report to
docs/reviews/YYYY-MM-DD-<scope>.md
Review Process
More from nu1nux/open-skills
analyze-project
Analyze a project's features, architecture, and implementation details without modifying any files.
10spec-write-plan
Write a detailed, step-by-step implementation plan and save it under docs/plans.
7spec-save-design
Convert a /spec:brainstorm session into a structured design document saved under docs/designs.
5spec-brainstorm
Lead structured design brainstorming with questions, alternatives, and incremental validation; no code or file edits.
5spec-execute-plan
Review an implementation plan and execute tasks in batches with checkpoints and reporting.
5