Junior Engineer Review

Use this skill to review whether generated code can be understood, modified, debugged, and explained by a reasonably capable new team member.

Treat the main test as total cognitive load. Good code should feel obvious in its local file, make sense in the wider package structure, and avoid relying on hidden author intent.

Review Posture

• Prioritize readability, traceability, and safe modification over cleverness.
• Review the code as if the next maintainer has repository context, but not the agent's private reasoning.
• Prefer concrete findings tied to code locations over broad style opinions.
• Avoid blocking on subjective taste unless it materially affects comprehension, debugging, or change safety.
• Preserve useful elegance, but reject niche language features, compressed expressions, and clever flows that make the code harder to explain.

Review Process

Always run this review after code changes, even when the user did not ask for a separate review. When code changes are made, run this review as a resolution loop: