skills.rest
ShadowAUS
ShadowAUSCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Enforce evidence-based code reviews with verification gates before completion claims.

Updated Aug 27, 2026
Search Tags:#verification#build#quality#subagent#code-review#pull-request#tests
One-click install
npx skills add https://github.com/ShadowAUS/chez-king-portal --skill code-review-shadowaus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/ShadowAUS/chez-king-portal/tree/main/.tessl/tiles/secondsky/claude-skills/plugins/code-review/skills/code-review
Command: npx skills add https://github.com/ShadowAUS/chez-king-portal --skill code-review-shadowaus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enforces rigorous, evidence-based code reviews and verification gates to prevent incomplete or unverified completion claims.

Core Features & Use Cases

  • Receiving feedback with structured evaluation to avoid performative responses
  • Requesting code-reviewer subagent reviews after each task or before merges
  • Verification gates ensuring tests pass, builds succeed, and changes are substantiated with evidence

Quick Start

Start a code-review cycle by implementing changes, triggering verification, and documenting evidence before claiming completion.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I enforce verification gates before claiming a pull request is complete?▼

Verification gates enforce evidence-based code reviews by requiring passing tests, successful builds, and documented evidence before any completion claims are made. This prevents unverified or incomplete changes from being merged into the main branch.

What is the best way to request a code-review subagent review after a major feature delivery?▼

Request a code-review subagent review by triggering a verification cycle after implementing changes. The subagent evaluates the delivery against verification gates, ensuring builds succeed, tests pass, and structural references are documented before finalizing completion.

How does evidence-based code review prevent performative responses to feedback?▼

Evidence-based code review prevents performative responses by enforcing structured evaluation protocols. Feedback must be substantiated with documented evidence, ensuring that completion claims and outcome-based reviews are backed by passing tests and successful builds.

Can I use verification gates for pre-merge verification in subagent-driven development?▼

Yes, verification gates are explicitly applicable to subagent-driven development and pre-merge verification. They ensure that tests pass, builds succeed, and changes are substantiated with evidence before any merge or completion claims are approved.

When do I need to trigger a code review cycle during development?▼

Trigger a code review cycle after implementing changes, before major merges, or following task completion. The cycle enforces verification gates, requiring documented evidence and successful builds before you can validly claim the work is complete.

Related Skills

Explore More Software Engineering Skills→
xiaoshuangLixiaoshuangLi
1

autonomous-coding

Plan and execute autonomous programming tasks through explore, implement, build, test, and verify phases.

Community
Advanced
bdsqqqbdsqqq
59

git-ship

Stage modified files, commit with conventional commits, and push to the remote repository.

Community
Intermediate
mt-krainskimt-krainski
1

verify

Run verification commands and review output before asserting completion.

Community
Basic
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate