requesting-code-review

Generate confidence-scored code review findings with actionable fixes.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/tuanldas/superteam --skill requesting-code-review-tuanldas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/tuanldas/superteam/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/tuanldas/superteam --skill requesting-code-review-tuanldas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Review methodology and discipline for performing code reviews (local diff, PR, specific files). Named from the workflow phase ("requesting a review") but contains the full review execution methodology: confidence-based severity, domain-specialized review, anti-false-positive discipline, and verify-before-fix logic. Used by reviewer agent and any agent that performs code review.

Core Features & Use Cases

  • Enforces evidence-based findings with explicit confidence scoring to prevent noisy reviews.
  • Provides domain-specific checklists and context-gathering steps to improve review rigor.
  • Supports deterministic workflow for post-task execution and pre-merge gating.

Quick Start

Provide an actionable, evidence-based review for a given code change.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I perform an evidence-based code review on a pull request?

An evidence-based code review surfaces disciplined findings by gathering context, applying domain checklists, and assigning confidence scores to prevent noisy pull request reviews.

What is confidence scoring in code reviews and how does it reduce false positives?

Confidence scoring in code reviews rates the certainty of each finding, enforcing an anti-false-positive discipline that filters out speculative issues before suggesting actionable fixes.

How can I use domain-specific checklists to review local file diffs?

Domain-specific checklists guide local file diff reviews by providing specialized context-gathering steps, ensuring rigorous verification across distinct review domains before changes are applied.

Can I automate pre-merge code checks using a deterministic workflow?

Yes, pre-merge code checks can be automated using a deterministic workflow that executes post-task reviews and gates merges based on confidence-scored, actionable findings.

What is the best way to ensure code review findings are actionable?

To ensure actionable code review findings, the review methodology requires verifying issues before fixing them and attaching explicit confidence scores to every reported defect.

When do I need a structured methodology for reviewing code changes?

A structured methodology for reviewing code changes is needed when executing post-task reviews or pre-merge checks, ensuring consistent, evidence-based quality assurance across all pull requests.