skills.rest
BoneTheDeveloper
BoneTheDeveloperCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Enforce evidence-based code reviews with verification gates and test artifacts.

Updated Aug 23, 2026
Search Tags:#automation#documentation#verification#quality-assurance#code-review#pull-request
One-click install
npx skills add https://github.com/BoneTheDeveloper/Electronic-Contact-Contact-Book --skill code-review-bonethedeveloper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/BoneTheDeveloper/Electronic-Contact-Contact-Book/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/BoneTheDeveloper/Electronic-Contact-Contact-Book --skill code-review-bonethedeveloper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code reviews often devolve into performative agreement rather than rigorous, evidence-based evaluation. This skill enforces structured feedback, traceable conclusions, and verification before any completion claims.

Core Features & Use Cases

  • Receiving feedback: Evaluate comments for technical accuracy, request clarification when unclear, and verify impact before acting.
  • Requesting reviews: Dispatch a dedicated review subagent to ensure independent assessment after each task or major change.
  • Verification gates: Require fresh test/build verification and evidence before claiming completion or merging changes.

Quick Start

Submit a code change and then run fresh verification to prove completion with evidence.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I enforce evidence-based code review before merging a pull request?▼

To enforce evidence-based code review, require fresh test results and build verification artifacts as proof before allowing any completion claims or pull request merges. Verification gates prevent blind agreement by demanding executable proof.

What is the best way to automate rigorous quality assurance for subagent-driven tasks?▼

Automating rigorous quality assurance for subagent-driven tasks involves dispatching a dedicated review subagent to perform independent assessments. This ensures consistent standards and structured feedback after each major change without performative agreement.

How do I verify technical accuracy when receiving pull request feedback?▼

To verify technical accuracy when receiving pull request feedback, evaluate the comments for clarity, request clarification when unclear, and verify the actual impact before acting. This structured approach ensures traceable conclusions.

Can I use automated code review to prevent completion claims without fresh evidence?▼

Yes, you can use automated code review to prevent completion claims without fresh evidence by implementing strict verification gates. These gates require fresh test and build verification artifacts to prove changes are complete.

Why does performative agreement happen during code reviews and how do I stop it?▼

Performative agreement happens during code reviews when evaluation lacks structured scrutiny. Stop it by applying rigorous, evidence-based evaluation that enforces verification gates and requires test results as proof before claiming completion.

Related Skills

Explore More Software Engineering Skills→
sangmokangsangmokang

vcx-dod-gate

Automate Phase 1 DoD gate verification with fresh build, lint, and test evidence.

Community
Advanced
mckissingermckissinger
1

land-feature

Coordinate GitHub pull request landing workflows to safely merge verified features into the main branch.

Community
Advanced
lailtonjuniorlailtonjunior

Test Generation

Generate unit, integration, and edge-case tests from codebases.

Community
Intermediate
R2W1csR2W1cs
1

lint-and-validate

Lint and validate JavaScript and Python code for syntax and style issues.

Community
Intermediate