skills.rest
daviddatuX25
daviddatuX25COMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Perform structured code-review passes and generate severity-based reports.

Updated Feb 17, 2026
Search Tags:#templates#checklist#quality-assurance#code-review#software-engineering#pull-request#production-readiness
One-click install
npx skills add https://github.com/daviddatuX25/SecureCAT-v2 --skill requesting-code-review-daviddatux25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/daviddatuX25/SecureCAT-v2/tree/main/.agent/skills/requesting-code-review
Command: npx skills add https://github.com/daviddatuX25/SecureCAT-v2 --skill requesting-code-review-daviddatux25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured code reviews help teams catch defects and design issues early by enforcing a formal review pass before merging or completing tasks.

Core Features & Use Cases

  • Checklist-based review passes that guide evaluators through code quality, architecture, and testing considerations.
  • Mandatory review triggers after each task, after major feature work, and before merging to ensure alignment with requirements.
  • Template-driven guidance and standardized feedback workflows, including how to raise, track, and close issues.
  • Broad applicability across languages and repositories, enabling consistent quality gates in diverse teams.

Quick Start

Initiate a structured code-review by supplying the implemented changes, the plan reference, and the base/head SHAs.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I perform a structured code review before merging a pull request?▼

A structured code review enforces a formal review pass before merging by evaluating code quality, architecture soundness, and testing thoroughness. You initiate the process by supplying the implemented changes, plan reference, and base/head SHAs.

What is included in a production-readiness checklist for new code changes?▼

A production-readiness checklist for new code changes includes evaluating code quality, architecture soundness, and testing thoroughness. It produces a report detailing strengths, issues by severity, recommendations, and a final readiness verdict.

When should I run a formal code-review pass on my feature branch?▼

You should run a formal code-review pass after each task, post-major feature work, or pre-merge. This ensures alignment with requirements and verifies production-readiness before changes are integrated.

Can I use a template-driven code review process across different programming languages?▼

Yes, template-driven code review passes apply across diverse languages and repositories. This broad applicability enables consistent quality gates for teams regardless of their specific technology stack.

What is the best way to track issues found during a pre-merge code review?▼

The best way to track issues found during a pre-merge code review is using standardized feedback workflows with template-driven guidance. The review report categorizes issues by severity to help raise, track, and close them effectively.

Related Skills

Explore More Software Engineering Skills→
tomasbassotomasbasso

requesting-code-review

Automate code reviews with structured templates and base/head SHAs.

Community
Intermediate
a-tabijia-tabiji

merge

Merge reviewed pull requests into main with squash merge and branch cleanup.

Community
Intermediate
DevelopersGlobalDevelopersGlobal
65

ci-cd-pipelines

Automate CI/CD pipelines with quality gates and deployment processes.

Official
Advanced
winsorllcwinsorllc

code-review

Execute linters, static analysis, and security scanners on code.

Community
Intermediate