code-review-and-quality
A framework for conducting multi-dimensional code reviews across correctness, readability, architecture, security, and performance. It provides standardized checklists, categorization for feedback, and strategies for managing large changes and dependency additions.
Is code-review-and-quality safe to install?
Safe to install: our audit of code-review-and-quality's source files found 0 shell commands, 0 external URLs, no file writes (none risk). Every command and URL listed appears verbatim in the skill's source. This skill provides a structured methodology and checklist for code review. It does not execute code, perform network requests, or modify files.
How we audit skills: our security review methodology.
Who is this skill for?
Software engineers and AI agents performing code reviews on pull requests or feature implementations.
What can you do with it?
- Reviewing code before merging into the main branch
- Evaluating code produced by other agents or models
- Refactoring existing codebases
- Verifying bug fixes and associated regression tests
How good is this skill?
Quality score: 5/10. The skill provides a comprehensive, well-structured, and actionable framework for code review. It includes clear definitions, specific checklists, and guidance on handling common review scenarios.
What does the skill file contain?
# Code Review and Quality ## Overview Multi-dimensional code review with quality gates. Every change gets reviewed before merge — no exceptions. Review covers five axes: correctness, readability, architecture, security, and performance. **The approval standard:** Approve a change when it definitely improves overall code health, even if it isn't perfect. Perfect code doesn't exist — the goal is continuous improvement. Don't block a change because it isn't exactly how you would have written it. If it improves the codebase and follows the project's conventions, approve it. ## When to Use - B...
Frequently asked questions
What are the five axes of the review?
Correctness, readability and simplicity, architecture, security, and performance.
How should I categorize my feedback?
Use no prefix for required changes, 'Critical:' for blockers, 'Nit:' for minor style preferences, 'Optional:' or 'Consider:' for suggestions, and 'FYI' for informational comments.
What is the recommended size for a code change?
Aim for ~100 lines changed for easy review. Changes around 300 lines are acceptable if they represent a single logical unit. Changes reaching 1000 lines should be split.
How should I handle dead code?
Identify unused code, list it explicitly, and ask the author for confirmation before deletion.
Related skills
make-interfaces-feel-better
37.7KFrontend developers and designers using AI agents to review UI code or implement design system improvements
This skill provides design engineering principles for polishing user interfaces. It guides the agent in reviewing and implementing UI details such as typography, animations, border radii, optical alignment, and performance optimizations.
golang-code-style
33.3KGo developers and AI coding agents performing code reviews or writing new Go code
This skill provides a comprehensive set of Go code style conventions focused on clarity, maintainability, and idiomatic patterns. It covers variable declarations, control flow, function design, file organization, and string handling, serving as a guide for human-judgment-based code reviews that complement automated linters.
vue-best-practices
24.1KVue
This skill provides a structured workflow for Vue.js development, mandating the use of the Composition API, TypeScript, and specific architectural patterns. It requires developers to plan component boundaries, follow strict SFC structure, and apply core reactivity and data flow principles before implementing features.
swiftui-pro
21.8KSwiftUI developers seeking to improve code quality and ensure adherence to modern Apple development standards
The swiftui-pro skill reviews SwiftUI code for modern API usage, maintainability, and performance. It validates code against a set of local reference files covering accessibility, data flow, navigation, and Swift best practices.