skills.rest
jfmyers9
jfmyers9COMMUNITY
Explore all skills by this author →
WebsiteGitHub

review

Automate end-to-end code review workflows and surface findings as beads tasks.

8|Updated Jan 24, 2026
Search Tags:#automation#beads#code-quality#task-management#code-review#design-review#git-diffs
One-click install
npx skills add https://github.com/jfmyers9/claude --skill review-jfmyers9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/jfmyers9/claude/tree/main/skills/review
Command: npx skills add https://github.com/jfmyers9/claude --skill review-jfmyers9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Senior engineer code review, filing findings as beads issues.

Core Features & Use Cases

  • Orchestrates code review workflow via beads tasks and design fields.
  • Beads-driven collaboration: assign tasks, track progress, and surface issues across the review lifecycle.
  • Use Case: When reviewing a feature branch, trigger a beads-based review bead and surface issues for triage.

Quick Start

Start a review with a pattern such as '/review <file-pattern>'.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review workflows and track findings as tasks?▼

Automated code review workflows are orchestrated end-to-end by triggering a review on a feature branch, which surfaces findings as beads tasks for triage and progress tracking. It coordinates solo or multi-perspective reviews and stores results.

What is the best way to run a multi-perspective code review on a feature branch?▼

Multi-perspective code review on a feature branch is coordinated by triggering a beads-based review using a file pattern. The workflow evaluates the git diff and surfaces issues as beads design fields for comprehensive triage.

Do I need a Git context and beads CLI to run automated design and code reviews?▼

Yes, a Git context including the branch and diff is required, alongside the beads CLI and a skill frontmatter with a name and description. These prerequisites enable the automation to store review results as beads design fields.

How does beads-driven task management work for code review issue tracking?▼

Beads-driven task management for code review works by assigning tasks, tracking progress, and surfacing issues across the review lifecycle. Findings from the git diff evaluation are stored as beads design fields for triage.

Can I review specific file patterns instead of an entire branch diff?▼

Yes, you can review specific file patterns by triggering the review with a pattern such as '/review <file-pattern>'. This scopes the automated code review workflow and surfaces findings as beads tasks for targeted triage.

Related Skills

Explore More Software Engineering Skills→
jayteealaojayteealao

review:quick

Automate structured code reviews by analyzing git diffs with five checklists.

Community
Basic
jfmyers9jfmyers9
8

prepare

Convert exploration findings into a beads epic with child tasks and swarm.

Community
Intermediate
cloud-native-toolscloud-native-tools

code-review

Standardize code reviews with git-delta diff visualization and structured feedback.

Official
Advanced
jamesjlundinjamesjlundin
32

pr-review

Analyze pull requests and generate structured review reports.

Community
Intermediate