skills.rest
bostonaholic
bostonaholicCOMMUNITY
Explore all skills by this author →
Website𝕏@bostonaholicGitHub

code-review

Separate generator and evaluator roles to review code against security and quality standards.

8|1|Updated Mar 28, 2026
Search Tags:#automation#testing#quality assurance#code review#security#engineering standards
One-click install
npx skills add https://github.com/bostonaholic/team --skill code-review-bostonaholic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/bostonaholic/team/tree/main/skills/code-review
Command: npx skills add https://github.com/bostonaholic/team --skill code-review-bostonaholic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates self-evaluation bias and quality degradation by enforcing a strict generator-evaluator separation, ensuring that code is reviewed by agents with fresh context and no prior involvement in the implementation.

Core Features & Use Cases

  • Generator-Evaluator Separation: Prevents authors from reviewing their own code, ensuring objective assessment.
  • Conventional Comments Integration: Standardizes feedback using issue, suggestion, and nitpick labels.
  • Severity-Based Gating: Automates pipeline flow based on security, test quality, and technical standards, blocking merges for critical defects.

Quick Start

Invoke the code-review skill to perform a comprehensive quality and security audit on the current diff against the established project standards.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I enforce bias-free code review standards in an automated pipeline?▼

Enforce bias-free code review by separating generator and evaluator roles to prevent self-evaluation. This skill objectively audits diffs against security, maintainability, and test-quality standards to gate pipeline progression.

Can code review automation block merges based on security and test quality?▼

Yes, code review automation can block pipeline progression using severity-based gating. It evaluates changes against security, technical standards, and test quality to halt merges for critical defects.

How does generator-evaluator separation improve code review automation?▼

Generator-evaluator separation improves code review by ensuring agents with fresh context evaluate changes without prior implementation involvement. This prevents self-evaluation bias and quality degradation.

What's the best way to standardize automated code review feedback formatting?▼

Standardize automated code review feedback using conventional comment formatting. The skill categorizes feedback with issue, suggestion, and nitpick labels to clarify severity and required actions.

Does automated code review validate SOLID principles and documentation completeness?▼

Yes, automated code review validates implementation correctness, SOLID principles, and documentation completeness. It comprehensively evaluates code changes to ensure they meet established engineering standards.

When do I need conventional comments in automated code review?▼

Use conventional comments in automated code review when standardizing feedback clarity across pipelines. This formatting labels issues, suggestions, and nitpicks to automate severity-based gating for technical standards.

Related Skills

Explore More Software Engineering Skills→
mamu7211mamu7211

pr-review

Review GitHub pull request diffs for correctness, security, and conventions.

Community
Advanced
dayvidphamdayvidpham
1

reviewer-comment

Standardize review findings with severity classification via Beads CLI.

Community
Intermediate
mlbrightmlbright

code-review

Analyzes Rails code quality and security via automated tools.

Community
Intermediate
peancharoenpeancharoen

speckit.checker

Run static analysis tools to detect linting, type, and security issues across source code.

Community
Advanced