home / skills / yellinzero / aico / aico-code-review
This skill provides structured code reviews to catch correctness, security, performance, and readability issues early and before merging.
npx playbooks add skill yellinzero/aico --skill aico-code-reviewReview the files below or copy the command above to add this skill to your agents.
---
name: aico-code-review
description: |
Request structured code review to catch correctness, security, performance, and readability issues. Reviews should happen early and often.
Use this skill when:
- Completing a task and need quality check
- After major feature implementation
- Before merging to main branch
- When stuck and need fresh perspective on code
- User asks for "code review", "review my code", "check my code"
- Subagent-driven workflow needs spec compliance or quality review
Review categories: Correctness, Tests, Security, Performance, Readability, Error Handling
Severity levels: Critical (fix now), Important (fix before proceeding), Minor (note for later)
---
# Code Review
## When to Request Review
**Mandatory:**
- After completing each task
- After implementing major feature
- Before merge to main
**Optional:**
- When stuck (fresh perspective)
- Before refactoring
- After fixing complex bug
## Review Checklist
| Category | Check |
| -------------- | ------------------------------- |
| Correctness | Does it do what it should? |
| Tests | Are there tests? Do they pass? |
| Security | Any vulnerabilities? |
| Performance | Any obvious bottlenecks? |
| Readability | Is code clear and maintainable? |
| Error Handling | Are errors handled properly? |
## Issue Severity
| Severity | Action |
| ------------- | -------------------------------- |
| **Critical** | Fix immediately, blocks progress |
| **Important** | Fix before proceeding |
| **Minor** | Note for later, can proceed |
## Review Output Template
```markdown
## Code Review: [Feature/Task Name]
### Files Modified
- `path/to/file.ts` - [what changed]
### Issues
**Critical:**
- [ ] [Issue description]
**Important:**
- [ ] [Issue description]
**Minor:**
- [ ] [Issue description]
### Assessment
- [ ] Ready to proceed
- [ ] Needs fixes (see issues above)
```
## Key Rules
- ALWAYS review after each task completion
- MUST fix Critical issues immediately
- MUST fix Important issues before proceeding
- Minor issues can be noted for later
- If reviewer is wrong, push back with technical reasoning
## Common Mistakes
- ❌ Skip review because "it's simple" → ✅ Review everything
- ❌ Ignore Critical issues → ✅ Fix immediately
- ❌ Proceed with Important issues → ✅ Fix first
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.
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.
What file formats or languages are supported?
Primary focus is TypeScript, but the checklist and guidance apply to other languages; include relevant context when submitting non-TypeScript code.
How are severities determined?
Severities map to impact: Critical blocks progress and must be fixed now, Important should be fixed before continuing, Minor can be noted and scheduled later.