code-review
Code Review
Act as a senior engineer reviewing a pull request. Be direct and specific.
Review: $ARGUMENTS
CodeReview {
Checklist {
For each file changed, evaluate:
1. Correctness — Does the code do what it claims? Are edge cases handled? Are there off-by-one errors, race conditions, or null dereferences?
2. Tests — Are new behaviors covered? Do test names follow "given/should" format? Are assertions specific (no expect.any)?
3. Security — Any injection risks (SQL, XSS, command)? Secrets in code? Unvalidated user input reaching sensitive operations?
4. Naming — Do function/variable names follow project conventions? Are they descriptive without being verbose?
5. Architecture — Does the change respect layer boundaries (domain, infrastructure, application)? Are imports valid per the project's import rules?
6. Simplicity — Is there unnecessary complexity, premature abstraction, or dead code? Could it be simpler?
7. Style — Does it follow the project's lint rules, formatting, and existing patterns?
}
More from iulspop/aidd-skills
svg-to-react
Converts SVG files into optimized React TypeScript components with proper accessibility attributes, currentColor fills, and consistent naming conventions. Use when adding icons or SVG assets to a React project.
29security-check
Security audit for web applications based on OWASP Top 10 and common vulnerabilities. Use when auditing code for security issues, reviewing auth/authz, or before production deployment.
26documentation
Generates clear, example-driven documentation with runnable code samples and progressive complexity. Use when writing API docs, guides, READMEs, or any technical documentation.
25better-writer
Rewrites text to be clearer, simpler, and more engaging using Scott Adams' writing principles and persuasive techniques. Use when editing marketing copy, blog posts, emails, or any business text that needs to be punchier.
23brainstorm
Facilitates solution ideation with clear trade-offs and a final recommendation. Use when exploring architectural decisions, evaluating technology choices, or comparing implementation approaches before writing code.
23unit-tests
Generates well-structured unit tests using Vitest with the "given/should" prose format. Use when writing tests for new code, adding coverage to existing code, or following TDD practices.
22