skills.rest
EremesNG
EremesNGCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-review

Review code changes for correctness, conventions, and test coverage.

1|2|Updated Mar 24, 2026
Search Tags:#testing#checklist#conventions#quality-assurance#lint#code-review#merge-ready
One-click install
npx skills add https://github.com/EremesNG/oh-my-opencode-lite --skill code-review-eremesng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/EremesNG/oh-my-opencode-lite/tree/main/src/skills/code-review
Command: npx skills add https://github.com/EremesNG/oh-my-opencode-lite --skill code-review-eremesng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review code changes for correctness, quality, and adherence to project conventions.

Core Features & Use Cases

  • Evaluate correctness and edge cases in proposed changes.
  • Enforce project conventions, naming, and error handling to reduce defects.
  • Provide actionable feedback and a prioritized list of issues before merging.

Quick Start

Review the latest subagent output and generate a structured critique using the checklist.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I check code changes for correctness and project conventions before merging?▼

To check code changes for correctness and conventions before merging, apply a structured checklist that evaluates edge cases, naming, and error handling to generate a prioritized list of actionable issues.

What is the best way to review subagent output for quality assurance?▼

The best way to review subagent output for quality assurance is to analyze the proposed code against a structured checklist addressing correctness, simplicity, types, and tests to ensure it is merge-ready.

Can I use a code review checklist to enforce error handling and naming conventions across a repository?▼

Yes, you can use a code review checklist to enforce error handling and naming conventions across a repository by verifying proposed changes against project conventions to reduce defects before integration.

Does automated code review evaluate type safety and test coverage alongside simplicity?▼

Automated code review evaluates type safety and test coverage alongside simplicity by applying a structured checklist that verifies correctness, types, and tests to provide actionable feedback before merging.

When should I run a pre-merge quality check on my codebase?▼

You should run a pre-merge quality check on your codebase immediately after generating subagent outputs or when preparing explicit quality checks, ensuring all proposed changes are merge-ready and conform to conventions.

Related Skills

Explore More Software Engineering Skills→
gopforevergopforever

code_review

Spawn an architect subagent to analyze code changes and plan debugging strategies.

Community
Intermediate
Jamie-CuiJamie-Cui
28

finishing-a-development-branch

Finalize feature branches with pre-integration checks and merge strategy guidance.

Community
Intermediate
sobhanashinesobhanashine
1

qa-rampage

Run automated typechecking, linting, testing, and browser-based user journeys.

Community
Advanced
codejunkie99codejunkie99
101

gf-lint

Lint SystemVerilog code with Verilator and produce categorized warnings and errors.

Community
Intermediate