skills.rest
HexSleeves
HexSleevesCOMMUNITY
Explore all skills by this author →
𝕏@jacob_lecoqGitHub

staff-requesting-code-review

Identify code changes needing formal review before merge.

Updated Jul 2, 2026
Search Tags:#git#testing#software engineering#code review#verification#production readiness
One-click install
npx skills add https://github.com/HexSleeves/skills --skill staff-requesting-code-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: staff-requesting-code-review
Source: https://github.com/HexSleeves/skills/tree/main/skills/staff-review-requesting
Command: npx skills add https://github.com/HexSleeves/skills --skill staff-requesting-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers verify completed work with a focused code review before merging, reducing the chance that defects, missing requirements, or weak tests slip into production.

Core Features & Use Cases

  • Pre-merge review: Prepare a concise review request with the exact git range and implementation summary.
  • Quality checks: Ask for feedback on code quality, architecture, testing, requirements coverage, and production readiness.
  • Workflow checkpointing: Use after major features, after each delegated task, or whenever a fresh technical perspective is needed.

Quick Start

Ask the assistant to request a code review for your completed changes using the provided review template and the relevant git commit range.

Frequently Asked Questions about staff-requesting-code-review

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

FAQPage Schema
What is the best way to verify code changes before merging to production?▼

Pre-merge code review verifies code changes by evaluating quality, architecture, testing, and production readiness using a precise git range and implementation summary to catch defects before they merge.

How do I request a code review for a completed software feature?▼

To request a code review, provide the exact git commit range and a concise implementation summary, then ask for severity-ranked feedback on requirements coverage and production readiness.

When do I need a formal code review in my software development workflow?▼

You need a formal code review at task completion checkpoints, after major features, during pre-merge verification, or whenever a fresh technical perspective is needed for stuck debugging sessions.

Can I get architecture and testing feedback for a specific git commit range?▼

Yes, code review supports any precise git range, delivering severity-ranked feedback on architecture, testing, code quality, and requirements coverage to identify issues before merging.

Does pre-merge verification require a summary of the implementation?▼

Yes, pre-merge verification requires a concise implementation summary alongside a precise git range to provide focused feedback on production readiness and catch defects before merge.

Related Skills

Explore More Software Engineering Skills→
peterfeipeterfei
420

changelog-generator

Generate CHANGELOG.md from Git commit history using Conventional Commits.

Community
Intermediate
drt0927drt0927
5

land-and-deploy

Automate release orchestration from PR merge to production verification.

Community
Advanced
vladm3105vladm3105
16

code-review

Automate code review across multi-language repositories with static analysis and security scanning.

Community
Advanced
oioio-spaceoioio-space

vuln-guard

Analyze Go code for security vulnerabilities using gosec and govulncheck.

Community
Advanced