requesting-code-review

Collects diffs, tests, and verification evidence to request final implementation acceptance review.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/hugefiver/ocmm --skill requesting-code-review-hugefiver
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/hugefiver/ocmm/tree/main/dsmm/skills/requesting-code-review
Command: npx skills add https://github.com/hugefiver/ocmm --skill requesting-code-review-hugefiver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After finishing implementation work, it is easy to declare completion without a rigorous final check. This Skill ensures a structured acceptance review happens before dsmm implementation work is considered done, preventing stale or conditional verdicts from slipping through. ## Core Features & Use Cases - Evidence Collection: Gathers the current diff, test results, diagnostics, and user-visible verification evidence before requesting review. - Acceptance Review Request: Asks the selected reviewer to check the implementation against the originally requested behavior. - Verdict Quality Control: Rejects stale or conditional review verdicts so only current, definitive acceptance counts. - Use Case: After completing a dsmm feature implementation, invoke this Skill to package the diff and test evidence and obtain a final acceptance verdict from the reviewer before marking the work complete. ## Quick Start Ask the AI to request a final code review for the completed dsmm implementation using the current diff and test evidence.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I request a final code review after implementation?▼

Collect the current diff, test results, diagnostics, and user-visible verification evidence, then ask the selected reviewer to check the implementation against the requested behavior. This Skill structures that request and rejects stale or conditional verdicts.

When should I use the requesting-code-review skill?▼

Use it after dsmm implementation work completes, before declaring the work done. It is the final acceptance gate, not a substitute for iterative review during development.

What evidence is needed for an acceptance code review?▼

The review requires the current diff, test results, diagnostics, and user-visible verification evidence. These artifacts let the reviewer confirm the implementation matches the requested behavior.

Why are stale or conditional review verdicts rejected?▼

Stale verdicts may not reflect the current state of the code, and conditional verdicts leave acceptance ambiguous. Rejecting them ensures the final approval is based on the latest implementation and is definitive.

Can this skill replace running tests before review?▼

No. Tests and diagnostics are inputs to the review, not outputs of it. The Skill collects existing test evidence and presents it to the reviewer rather than executing the test suite itself.