aico-code-review_skill

Overview

This skill provides structured, actionable code reviews focused on correctness, tests, security, performance, readability, and error handling. Use it to catch problems early, prioritize fixes by severity, and ensure code meets team standards before merging. Reviews are brief, repeatable, and designed to fit into fast, iterative workflows.

How this skill works

You submit code or a pull request context and the skill inspects modified files against a checklist covering Correctness, Tests, Security, Performance, Readability, and Error Handling. It categorizes findings by severity — Critical, Important, Minor — and returns a concise report with files modified, issues grouped by severity, and a clear assessment of readiness to proceed. The review recommends fixes or tests to add and can push back with technical reasoning when the reviewer’s assumptions are wrong.

When to use it

• After completing each task for a quality check
• After implementing a major feature before integration
• Before merging to main or a protected branch
• When you’re stuck and need a fresh perspective
• When a subagent workflow requires spec or quality compliance

Best practices

• Request reviews early and often rather than waiting until the end
• Attach failing tests or reproduction steps for correctness issues
• Prioritize Critical and Important items before proceeding
• Include minimal diff context or link to the pull request for focused feedback
• If you disagree with a finding, respond with technical evidence and tests

Example use cases

• Final check before merging a TypeScript feature branch
• Validating security and error handling after adding authentication logic
• Spotting performance regressions in a new data-processing routine
• Ensuring tests cover edge cases after fixing a complex bug
• Getting a quick readability and API-consistency pass on refactored modules