reviewing-code

WallysonGalvao's avatarfrom WallysonGalvao

Code review workflow for evaluating changes against standards. Use when reviewing pull requests, commits, or diffs.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 4, 2026
[Code Review]

When & Why to Use This Skill

This Claude skill automates the code review process by systematically evaluating pull requests, commits, and diffs against rigorous engineering standards. It ensures high-quality code delivery by focusing on type safety, security, accessibility, and architectural clarity, providing structured feedback that distinguishes between critical blockers and quality suggestions.

Use Cases

  • Automated Pull Request Audits: Streamline the PR process by automatically checking for type-safety violations, such as 'any' types or improper casting, before human review.
  • Security & Compliance Scanning: Identify potential vulnerabilities including raw SQL queries, exposed secrets, and missing input validation during the development phase.
  • Frontend Quality Control: Ensure React components follow best practices, including the use of React Query for data fetching and adherence to ARIA accessibility standards.
  • Maintainability Enforcement: Enforce consistent coding patterns like early returns, descriptive naming, and flat code structures to reduce technical debt across the codebase.
  • Testing Verification: Validate that bug fixes and new features are accompanied by appropriate behavioral tests to prevent regressions.
namereviewing-code
descriptionCode review workflow for evaluating changes against standards. Use when reviewing pull requests, commits, or diffs.

Code Review Standards

Systematic review for quality and consistency.

Review Checklist

Type Safety

  • No any types
  • Minimal as casting
  • E2E type coverage

Clarity

  • Descriptive names
  • Early returns
  • Flat code structure
  • No magic strings/numbers

React (if applicable)

  • Pure components
  • React Query for data
  • Suspense/Error boundaries

Security

  • Input validation
  • Query builders (no raw SQL)
  • No exposed secrets

Accessibility

  • Semantic HTML
  • ARIA labels
  • Keyboard navigation

Testing

  • Tests behavior
  • Bug fixes have tests

Output Format

## Summary
[What changed]

## Issues
### Critical (blocks merge)
- [Issue]: [Fix]

### Suggested (improve quality)
- [Issue]: [Fix]

## Status
✅ Approved | ⚠️ Minor changes | ❌ Needs work

Priority

  1. Critical: Security, type-safety, breaking changes
  2. High: Maintainability, readability
  3. Medium: Naming, minor refactoring
  4. Low: Style preferences