code-review - SKILL.md Agent Skill

name: code-review description: Perform code reviews (CR) for changed files in the current repository. Use when the user asks to review code, review changes, perform a code review, or mentions CR / code review.

Perform code reviews for changed files in the current repository.

Determine the scope of the code review:

Check the current working directory and project structure
Identify which files need review:
- If the user specifies specific files, review those
- If the user mentions a PR or branch, check the diff
- If unspecified, check git status / diff for recently changed files
- Search the codebase for recent changes if needed

For each file, systematically review:

Correctness: Does the code work as intended? Any logic errors or edge cases missed?
Type safety: Proper TypeScript types, avoid any, no unsafe assertions?
Code style: Follows project conventions (see AGENTS.md / CLAUDE.md)?
Consistency: Naming, imports, structure consistent with rest of codebase?
Performance: Any obvious performance concerns or unnecessary complexity?
Security: No hardcoded secrets, no unsafe patterns?
Maintainability: Clear, readable, properly commented where needed?

Reference the project's AGENTS.md / CLAUDE.md for:

Summarize the review findings with:

Format findings clearly using markdown with code references.

If the user requests fixes or you determine changes are necessary:

Create a todo list for the planned fixes
Apply fixes incrementally, keeping each change focused
Run project validation commands after changes:
- pnpm lint
- pnpm build
- pnpm dev (when relevant)

Be constructive and specific — avoid vague feedback
Cite file paths and line numbers when referencing issues
Prioritize: correctness > safety > maintainability > style
Follow the project's existing patterns over personal preferences
Do not modify test files to make tests pass (see Bug Fixing strategy in AGENTS.md)