skills.rest
MaiconGambini
MaiconGambiniCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

reviewing-code

Reviews pull requests, commits, and diffs against a structured code quality checklist.

Updated Jul 29, 2026
Search Tags:#type safety#testing#code review#checklist#pull request#security#react
One-click install
npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill reviewing-code-maicongambini
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewing-code
Source: https://github.com/MaiconGambini/opencode-harness-guide/tree/main/skills/reviewing-code
Command: npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill reviewing-code-maicongambini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews are often inconsistent, with reviewers missing security issues, type-safety gaps, or accessibility problems depending on their experience level. This Skill provides a systematic checklist and standardized output format so every review covers the same critical dimensions. ## Core Features & Use Cases - Structured Review Checklist: Covers type safety, clarity, React patterns, security, accessibility, and testing in one pass. - Standardized Output Format: Produces a summary, issues grouped by severity (Critical vs. Suggested), and a final approval status. - Priority-Based Triage: Ranks findings from critical security and breaking changes down to low-priority style preferences. - Use Case: When reviewing a teammate's pull request, apply the checklist to catch raw SQL queries, missing input validation, or untested bug fixes before merge. ## Quick Start Review the changes in this pull request against the code review checklist and report any critical or suggested issues.

Frequently Asked Questions about reviewing-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a pull request systematically?▼

Use a structured checklist covering type safety, clarity, security, accessibility, and testing. Group findings into critical issues that block merge and suggested improvements, then finish with a clear approval status.

What should a code review checklist include?▼

A code review checklist should cover type safety (no any types, minimal casting), clarity (descriptive names, early returns), security (input validation, no raw SQL), accessibility (semantic HTML, ARIA labels), and testing (behavior tests, tests for bug fixes).

How do I prioritize code review findings?▼

Rank findings by impact: critical issues like security flaws, type-safety violations, and breaking changes block merge; maintainability and readability issues are high priority; naming and style preferences are lower priority.

Does this review checklist apply to React codebases?▼

Yes, the checklist includes a React-specific section covering pure components, React Query for data fetching, and Suspense/Error boundaries. This section applies only when the reviewed code uses React.

What are the limitations of a checklist-based code review?▼

A checklist ensures consistent coverage but cannot judge architectural fit, business logic correctness, or runtime performance. Combine it with domain knowledge and automated testing for complete review coverage.

Related Skills

Explore More Software Engineering Skills→
hanzlahabibhanzlahabib
2

rcode-checkpoint-preview

Guide a human through a five-step code change review before checkpoint approval.

Community
Advanced
authrain-cloud-abdullahformuliauthrain-cloud-abdullahformuli

code-review-and-quality

Reviews code changes across correctness, readability, architecture, security, and performance before merge.

Community
Intermediate
DataDogDataDog
648

lint

Run Hatch-based lint, format, and quality checks on modified files.

Official
Advanced
saschadudkin-sketchsaschadudkin-sketch

code-review

Automate code review for rezidence4/DomHub repository changes.

Community
Advanced