review▌

TypeScript/JavaScript Code Review Skill \n @./../_shared/typescript-commands.md \n Code Review Guidelines \n Review pull requests with a focus on: \n \n Readability and maintainability \n Appropriate test coverage \n Compliance with project coding standards and conventions \n Code quality and best practices \n Type safety and proper TypeScript usage \n React best practices (when applicable) \n

This guide explains how to add line-specific review comments to pull requests using the GitHub CLI (gh) API or mcp__github_inline_comment__create_inline_comment if it not available, similar to how the GitHub UI allows commenting on specific lines of code.

These patterns are intentional and correct - do not report as issues:

This skill ensures all code follows security best practices and identifies potential vulnerabilities.

Find access control vulnerabilities by investigating how the codebase answers one question:

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Code review requires technical evaluation, not emotional performance.

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Dispatch superpowers:code-reviewer subagent to catch issues before they cascade.

Review and fix issues identified by Seer (by Sentry) in GitHub PR comments.