review-code

Review code changes for security, correctness, and maintainability issues.

3|3|Updated Jan 15, 2026

Search Tags:#architecture #code review #security #edge cases #maintainability #quality

Ready to run

npx skills add https://github.com/twikus/claude-configuration --skill review-code-twikus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-code
Source: https://github.com/twikus/claude-configuration/tree/main/claude-code-config/skills/workflow-review-code
Command: npx skills add https://github.com/twikus/claude-configuration --skill review-code-twikus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides engineers to perform expert-level code reviews focused on security, correctness, and maintainability, reducing noise and increasing impact.

Core Features & Use Cases

Security-focused evaluation: identify vulnerabilities, misconfigurations, and insecure patterns in code changes.
Correctness and edge cases: validate logic, null handling, input validation, and robust error handling.
Architecture and maintainability: assess single-responsibility adherence, abstractions, and test coverage for long-term health.
Structured feedback: deliver What + Why + How with concrete remediation steps.
Use Case: apply to pull requests across languages to drive higher-quality fixes and better-structured tests.

Quick Start

Provide the PR patch or diffs to the skill along with a short description of the goal. The skill will generate a concise, prioritized review checklist and proposed remediation steps.

Frequently Asked Questions about review-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I review a pull request for security vulnerabilities and logic errors?▼

To review a pull request for security vulnerabilities and logic errors, provide the PR patch or diffs along with a short goal description to generate a concise, prioritized review checklist with concrete remediation steps.

What is the best way to structure code review feedback for maintainability?▼

The best way to structure code review feedback for maintainability is to use a What, Why, and How format that explains the issue, its architectural impact, and proposed concrete remediation steps with clear priority labels.

Can I use automated code review to check edge cases and input validation across languages?▼

Yes, you can use automated code review to check edge cases and input validation across languages by applying the review process to pull requests and commits, validating logic, null handling, and robust error handling.

How do I assess architectural concerns and single-responsibility adherence in a code diff?▼

To assess architectural concerns and single-responsibility adherence in a code diff, evaluate abstractions and test coverage during the review to ensure long-term health and maintainability of the codebase.

Does this code review approach work for commits as well as pull requests?▼

Yes, this code review approach works for commits as well as pull requests, applying security-focused evaluation, correctness checks, and maintainability assessments across both types of code changes.

What are the limitations of using a structured checklist for code review?▼

A limitation of using a structured checklist for code review is that it requires providing the PR patch or diffs and a short description of the goal to generate accurate, prioritized feedback and proposed remediation steps.