Agent skill · software engineering · sickn33
code-review-and-quality
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
Why this skill is useful
Adds a structured multi-axis review process that improves code quality assessment beyond standard practices.
What it needs
About 12k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Supporting material availability This catalog copy contains the inline guidance below, but does not include the following supporting paths. They are external prerequisites, not bundled files: <support-root>/references/security-checklist.md <support-root>/references/performance-checklist.md Obtain the required material from the declared upstream source, or from a user-provided installation of that source. Resolve each path relative to that installation, inspect its contents, and verify any applicable license and execution prerequisites. Do not run a command or claim a referenced procedure was followed until its required file exists. Do not fabricate the missing scripts or treat an unrelated file with the same name as equivalent. Independent steps fully documented here can proceed within the user’s authorized scope; report any dependent step as unavailable. 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 Before merging any PR or change After completing a feature implementation When another agent or model produced code you need to evaluate When refactoring existing code After any bug fix (review both the fix and the regression test) The Five-Axis Review Every review evaluates code across these dimensions: 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/code-review-and-quality