code-review-checklist

Apply a structured checklist to assess code changes and log PASS/REJECT decisions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/silbaram/artifact-driven-agent --skill code-review-checklist-silbaram
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-checklist
Source: https://github.com/silbaram/artifact-driven-agent/tree/main/core/skills/code-review-checklist
Command: npx skills add https://github.com/silbaram/artifact-driven-agent --skill code-review-checklist-silbaram

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often suffer from inconsistency and subjectivity. This checklist provides a standardized set of criteria to guide reviewers toward objective decisions (Pass/Reject) and ensures decisions are well-documented.

Core Features & Use Cases

  • Provides a structured review checklist across acceptance criteria, technical compliance, code quality, and safety to guide reviewers.
  • Encourages objective decisions by requiring documented justification and limiting scope to task-related changes.
  • Use Case: When reviewing a pull request, apply the checklist to determine Pass or Reject and log the rationale for traceability.

Quick Start

Run the code-review-checklist against the latest code changes to determine Pass or Reject with justification.

Frequently Asked Questions about code-review-checklist

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

FAQPage Schema
How do I standardize code reviews to make objective pass or reject decisions?

To standardize code reviews, apply a formal checklist that assesses acceptance criteria, technical compliance, code quality, and safety. This enforces objective PASS or REJECT decisions with documented justification and neutrality.

What is the best way to document code review rationale for traceability?

Documenting code review rationale requires logging strict PASS or REJECT decisions with written justification. Limiting scope to task-related changes ensures decisions remain neutral and traceable for future audits.

How do I use a checklist to review a pull request for technical compliance and safety?

To review a pull request, run the code changes against a structured checklist covering acceptance criteria, technical compliance, code quality, and safety to determine a PASS or REJECT outcome with formal justification.

Can I enforce consistent code quality checks across different software review processes?

Yes, enforcing consistent code quality checks is achieved by applying a standardized review checklist. This limits scope to task-related changes and requires documented justification for every PASS or REJECT decision.

Why does my code review process suffer from subjectivity and inconsistent decisions?

Code reviews suffer from inconsistency and subjectivity when lacking a standardized set of criteria. Applying a formal checklist guides reviewers toward objective, documented decisions and limits scope to task-related changes.

When do I need a formal code review checklist during software development?

You need a formal code review checklist when evaluating pull requests to ensure objective decision-making. It assesses acceptance criteria, technical compliance, code quality, and safety while enforcing strict PASS or REJECT logging.