code review and quality

AI Community

Skill notes

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. Correctness

Does the code do what it claims to do? Does it match the spec or task requirements? Are edge cases handled (null, empty, boundary values)? Are error paths handled (not just the happy path)? Does it pass all tests? Are the tests actually testing the right things?

2. Readability & Simplicity

Can another engineer (or agent) understand this code without the author explaining it? Are names descriptive and consistent with project conventions? (No temp, data, result without context) Is the control flow straightforward (avoid nested ternaries, deep callbacks)? Is the code organized logically (related code grouped, clear module boundaries)? Are there any "clever" tricks that should be simplified?

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@addyosmani · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Understand the Context

Before looking at code, understand the intent:

02
Step 2: Review the Tests First

Tests reveal intent and coverage:

03
Step 3: Review the Implementation

Walk through the code with the five axes in mind:

04
Step 4: Categorize Findings

Label every comment with its severity so the author knows what's required vs optional: Prefix · Meaning · Author Action *(no prefix)* · Required change · Must address before merge Critical: · Blocks merge · Security vulnerability, data loss, broken functionality Nit: · Minor, optional · Author may ignore — formatting, style preferences

05
Step 5: Verify the Verification

Check the author's verification story:

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.