skills.rest
fredrikaverpil
fredrikaverpilCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-review

Enforce evidence-based verification gates before claiming code review completion.

253|7|Updated Apr 8, 2016
Search Tags:#git#feedback#verification#pr#code-review
One-click install
npx skills add https://github.com/fredrikaverpil/dotfiles --skill code-review-fredrikaverpil
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/fredrikaverpil/dotfiles/tree/main/stow/shared/.claude/skills/review
Command: npx skills add https://github.com/fredrikaverpil/dotfiles --skill code-review-fredrikaverpil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides proper code review practices with technical rigor, avoiding performative agreement and ensuring verification before claiming completion.

Core Features & Use Cases

  • Receiving Feedback: Techniques to evaluate feedback and request clarification
  • Requesting Reviews: Protocol to dispatch code-reviewer subagent for reviews
  • Verification Gates: Evidence-based checks before claiming completion

Quick Start

Before claiming completion, review the guidance and run the verification gates as described in references.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I evaluate code review feedback for technical rigor?▼

Code review feedback should be grounded in evidence and specific technical concerns. Request clarification on vague or unsupported comments, push back on performative agreement, and require reviewers to cite concrete issues like failing tests, architectural violations, or security gaps before accepting feedback as valid.

What verification gates should I enforce before marking code complete?▼

Verification gates require fresh evidence: passing test suites, successful builds, confirmed bug fixes, and completed checklists. Never claim completion without running these checks. Each gate enforces that code meets technical standards before merge, preventing incomplete work from advancing.

How do I request a code review through pull requests?▼

Dispatch the code-reviewer subagent with your PR and specific areas needing feedback. Provide context on changes, testing performed, and dependencies affected. This structured protocol ensures reviewers have the information needed to give technically rigorous, evidence-based feedback.

Why do code reviews need verification before claiming completion?▼

Verification gates prevent status claims without proof. A PR marked complete but with failing tests or unresolved issues creates technical debt and slows downstream work. Enforcing evidence-based checks—passing builds, test results, checklist sign-off—ensures quality before merge.

Can I use this approach across different development workflows?▼

Yes, verification gates apply across subagent-driven development, pull requests, and pre-merge checks. The core principle—enforcing technical rigor and fresh evidence before completion—works in any workflow using code review as a quality control step.

Related Skills

Explore More Software Engineering Skills→
kk20300113-pngkk20300113-png

land-and-deploy

Merge pull requests and verify production health via canary checks.

Community
Advanced
adryanmoldokkr32-pixeladryanmoldokkr32-pixel

land-and-deploy

Merge pull requests, monitor CI, deploy to production, and verify health with canary checks.

Community
Intermediate
InnoMikitaKutasInnoMikitaKutas

verify

Execute tiered Definition of Done checks and generate pass/fail reports.

Community
Advanced
ChangZhou-xjChangZhou-xj

requesting-code-review

Automate pre-commit code verification with static scans, quality gates, and an auto-fix loop.

Community
Advanced