Reviewing Code
Systematically evaluate code changes for security, correctness, performance, and spec alignment. Use when reviewing PRs, assessing code quality, or verifying implementation against requirements.
Security Assessment
About Reviewing Code
The 'Reviewing Code' skill is designed to help developers systematically evaluate code changes in a thorough and efficient manner. It focuses on key aspects such as security, correctness, performance, spec alignment, and maintainability. By applying this skill during the code review process, users can identify critical issues, ensure adherence to specifications, and improve overall code quality. This skill is invaluable for development teams looking to maintain high standards and prevent regressions or bugs in the codebase.
The skill offers two primary review strategies: Sequential and Parallel. For small pull requests (PRs), a sequential review method is suggested, where the reviewer evaluates the code step-by-step across different quality dimensions. In contrast, larger PRs are handled using a parallel approach, where multiple agents review different aspects (e.g., security, UI, API contracts) simultaneously to ensure comprehensive coverage. The review process is highly structured, with clear guidelines for identifying critical, important, and optional issues, and the report format helps teams communicate findings effectively.
This skill is ideal for teams of all sizes working on software projects that require regular code reviews. It is particularly useful for developers, senior engineers, and code reviewers who are focused on ensuring security, code quality, and proper implementation of requirements. It is also beneficial for teams working with complex systems where multiple code changes affect different parts of the application, such as large PRs or projects with multiple contributors.
FAQ
How do I determine whether to use sequential or parallel review?
Use the sequential review for smaller pull requests with fewer than 5 files. For larger pull requests with more than 5 files, use the parallel review strategy to divide the review tasks among specialists.
What should I focus on when reviewing for security?
When reviewing for security, ensure input validation and sanitization, check authentication and authorization, validate sensitive data handling, and verify against common vulnerabilities such as SQL injection or cross-site scripting (XSS).
Can this skill be used for reviewing frontend code?
Yes, the 'Reviewing Code' skill includes a focus on UI/UX requirements, which makes it suitable for reviewing frontend code, particularly in terms of design spec alignment, accessibility, and performance.
Is there a recommended tool for generating reports?
The skill provides a report structure template, which can be manually filled after completing the review process. There is no specific tool mentioned for automatic report generation.
Install Reviewing Code
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
CaptainCrouton89/.claude