code-review

Enforce evidence-based code review verification before completion claims.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/DxTa/dotfiles --skill code-review-dxta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/DxTa/dotfiles/tree/main/opencode/skills/core/code-review
Command: npx skills add https://github.com/DxTa/dotfiles --skill code-review-dxta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces rigorous code review practices, preventing performative agreement, ensuring technical correctness, and verifying completion before claims are made, thereby improving code quality and development process integrity.

Core Features & Use Cases

  • Technical Rigor: Prioritizes technical evaluation over social comfort during feedback reception.
  • Systematic Review: Utilizes a subagent for requesting and managing code reviews, especially for subagent-driven development and pull requests.
  • Verification Gates: Mandates evidence-based verification before any claims of success, completion, or passing statuses.
  • Use Case: Before merging a feature, you can use this skill to ensure all tests pass, the code adheres to requirements, and any feedback from reviewers has been technically assessed and addressed, preventing the introduction of bugs or incomplete work.

Quick Start

Use the code-review skill to request a review for the latest commit.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I enforce technical rigor during a code review?

To enforce technical rigor during code review, you must prioritize technical evaluation over social comfort and use a subagent to systematically request and manage reviews. This prevents performative agreement and maintains technical correctness during feedback reception.

How do I verify tests and builds before claiming task completion?

You verify tests and builds by implementing mandatory evidence-based verification gates before any success or completion claims. This requires passing tests and builds, ensuring code adheres to requirements, and addressing reviewer feedback to prevent false completion claims.

How do I request a pull request review using a subagent?

You request a pull request review using a subagent by following systematic review protocols for subagent-driven development. The subagent manages the review request, prioritizing technical evaluation and ensuring all feedback is technically assessed before merging.

What is the best way to prevent false completion claims in software engineering?

The best way to prevent false completion claims is by applying mandatory evidence-based verification gates. This process requires passing tests, builds, and bug fixes, ensuring any reviewer feedback is technically addressed before declaring a task complete.

How do I handle feedback reception to ensure technical correctness?

You handle feedback reception by prioritizing technical evaluation over social comfort. This means systematically assessing all reviewer feedback for technical correctness rather than performative agreement, ensuring code quality and development process integrity.

Do I need specific dependencies to implement verification gates for bug fixes?

No specific dependencies are required to implement verification gates for bug fixes. You can mandate evidence-based verification directly to ensure tests pass and code adheres to requirements before claiming success or completion statuses.