skills.rest
arttttt
artttttCOMMUNITY
Explore all skills by this author →
GitHub

review

Review issues and pull requests, record verdicts, and categorize findings.

Updated Dec 6, 2025
Search Tags:#architecture#beads#review#issue#code-review#pull-request#verdict
One-click install
npx skills add https://github.com/arttttt/CMIDCABot --skill review-arttttt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/arttttt/CMIDCABot/tree/main/.codex/skills/review
Command: npx skills add https://github.com/arttttt/CMIDCABot --skill review-arttttt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines code review by providing a structured process to evaluate issues and changes, document findings, and coordinate follow-up actions.

Core Features & Use Cases

  • Structured Review Workflow: Read issue details, assess scope, and verify alignment with ARCHITECTURE.md and conventions.md.
  • Verdict Recording: Produce a clear verdict and categorize findings as related or unrelated.
  • Issue Tracking with Beads: Save reviews, create issues for unrelated findings, and report status.

Quick Start

To start a review, invoke the /review command or provide the issue details. Follow the interaction contract to obtain and record the verdict.

Frequently Asked Questions about review

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

FAQPage Schema
How do I conduct a structured code review for a pull request?▼

A structured code review involves reading ARCHITECTURE.md and conventions.md, fetching issue details, determining scope, and delivering a validated verdict with related and unrelated findings.

What is a code review verdict and how does it categorize findings?▼

A code review verdict is the formal output of a review that categorizes findings into related and unrelated groups, allowing reviewers to separate direct pull request issues from tangential code observations.

How do I track unrelated findings discovered during a pull request review?▼

You can track unrelated findings by using beads to save the review and automatically create new issues for findings that fall outside the current pull request scope, reporting the status accordingly.

Does this code review process require specific project documentation files?▼

Yes, the code review process requires ARCHITECTURE.md and conventions.md files to verify alignment, assess change scope, and ensure the pull request adheres to established project conventions.

Can I use beads to fetch issue details for code review workflows?▼

Yes, beads are used within the code review workflow to fetch issue details, save the recorded review findings, create issues for unrelated findings, and report the final status.

Related Skills

Explore More Software Engineering Skills→
fyrsmithlabsfyrsmithlabs

git-repo-standards

Validate repository naming, structure, documentation, and security files against project standards.

Official
Intermediate
vega113vega113

beads-reviewer

Review Beads task commits and diffs to assess merge readiness.

Community
Intermediate
YoshikemoloYoshikemolo
5

git-jira-integration

Generate Git branch names and validate commit messages against Jira issues.

Community
Intermediate
insightwavesmithinsightwavesmith

code-analyzer

Analyze code changes to identify those meeting evidence-shape-check criteria.

Community
Intermediate