requesting-code-review

Evaluate code changes for quality and compliance before merging.

Updated Jul 8, 2022
One-click install
npx skills add https://github.com/limaon/dotfiles --skill requesting-code-review-limaon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/limaon/dotfiles/tree/main/.config/opencode/skills/requesting-code-review
Command: npx skills add https://github.com/limaon/dotfiles --skill requesting-code-review-limaon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables rigorous, early-stage code review to catch defects, improve quality, and ensure changes meet project standards before they are merged.

Core Features & Use Cases

  • Template-driven review: Uses standardized guidelines to assess code quality, testing, and documentation.
  • Early feedback: Provides actionable feedback to developers before integration.
  • Use Case: Before merging a feature branch, run the skill to validate alignment with the design and compliance with the plan, improving stability.

Quick Start

Use the requesting-code-review skill to initiate a review of the latest commit on the current branch.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I automate peer code review before merging a feature branch?

Automated peer code review evaluates changes for quality and compliance by checking architecture, tests, and plan alignment before merging. It uses template-driven guidelines to catch defects early and provide actionable feedback on feature branches and refactors.

What is template-driven code review and how does it improve pull requests?

Template-driven code review uses standardized guidelines to assess code quality, testing, and documentation in pull requests. It provides early, actionable feedback to developers before integration, ensuring changes meet design requirements and improving overall stability.

Can I use automated code review for refactoring tasks across different branches?

Yes, you can use automated code review for refactoring tasks across branches. It evaluates changes for quality and compliance, catching issues early and returning actionable feedback to ensure your refactors align with the project plan before merging.

What's the best way to validate code quality and test coverage before integration?

The best way to validate code quality before integration is running a template-driven review that checks architecture, tests, and documentation. It enforces requirements to review code quality and alignment with the plan, providing actionable feedback to developers.

Does automated code review check alignment with the original implementation plan?

Yes, automated code review checks alignment with the original implementation plan. It evaluates changes to ensure they meet project standards and design requirements, validating code quality, architecture, and tests before returning actionable feedback for merging.