skills.rest
pear-studio
pear-studioCOMMUNITY
Explore all skills by this author →
GitHub

review0-walkthrough

Walk through git diffs as logical units and record agreed decisions.

34|12|Updated Aug 1, 2021
Search Tags:#code review#documentation#decision logging#git diff#walkthrough#interactive workflow#rn review records
One-click install
npx skills add https://github.com/pear-studio/nonebot-dicepp --skill review0-walkthrough
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review0-walkthrough
Source: https://github.com/pear-studio/nonebot-dicepp/tree/main/docs/agent/skills/review0-walkthrough
Command: npx skills add https://github.com/pear-studio/nonebot-dicepp --skill review0-walkthrough

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review a code change one logical unit at a time, explain what changed and why, and capture agreed outcomes immediately into a downstream-ready review document.

Core Features & Use Cases

  • Interactive diff walkthrough: Breaks a diff/commit range into design-decided logical units and walks through them sequentially while waiting for user confirmation.
  • On-the-spot discussion & decision recording: Supports questions and “stop/expand” deep dives, then writes only finalized discussion outcomes into the review record.
  • Compatible review workflow: Produces a standard Rn document format compatible with review2-reply through review5-accept and can be used standalone or as an alternative to review1-raise.
  • Common TRPG/engineering change scenarios: Suitable when you need consistent, structured explanations for diffs (HEAD, ranges, or file-scoped changes) during team development.

Quick Start

Run review0-walkthrough to walkthrough the default git diff against HEAD and record any user-decided items for the next review stages.

Frequently Asked Questions about review0-walkthrough

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

FAQPage Schema
How do I do an interactive code review walkthrough of a git diff?▼

An interactive code review walkthrough breaks a git diff into logical units, explains changes sequentially, waits for user confirmation per unit, and captures agreed decisions into a review record document.

What is the best way to log decisions during a code review session?▼

Logging decisions during a code review involves discussing diff changes on the spot, then appending only finalized outcomes as Rn blocks into a downstream-ready review_record document.

Can I review specific commit ranges instead of just HEAD?▼

Yes, you can review specific commit ranges. The walkthrough applies to git diffs against HEAD, commit ranges, or file-scoped changes, breaking them into logical units for paced progression.

How do I record code review outcomes for downstream stages?▼

Recording code review outcomes uses a standard Rn document format compatible with review2-reply through review5-accept, generating logical-unit summaries for downstream review stages.

Does the walkthrough support deep dives or stop points during the review?▼

Yes, the walkthrough supports deep dives. It allows user Q&A, stop, or expand actions during the interactive workflow, writing only finalized discussion outcomes into the review record.

What are the limitations of using a step-by-step diff walkthrough?▼

A step-by-step diff walkthrough requires explicit user confirmation per logical unit and needs provided tooling and paths to append Rn blocks, making it less suited for non-interactive automated pipelines.

Related Skills

Explore More Software Engineering Skills→
OpenAuthorityOpenAuthority
8

git_add

Stage specific files or glob patterns for the next git commit.

Official
Basic
pear-studiopear-studio
34

review2-reply

Generate in-place Reply sections for each Rn in a review document.

Community
Intermediate
qq824045252-ship-itqq824045252-ship-it

superpowers-executing-plans

Load plan files, review them critically, and execute tasks with verifications.

Community
Advanced
humansyshumansys
71

rai-bugfix-analyse

Identify and document software bug root causes in RaiSE projects.

Official
Advanced