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

review4-execute

Executes finalized consensus implementation entries from a review document after validation and tests.

34|12|Updated Aug 1, 2021
Search Tags:#code review#test verification#adversarial review#change implementation#workflow gating#consensus execution
One-click install
npx skills add https://github.com/pear-studio/nonebot-dicepp --skill review4-execute
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review4-execute
Source: https://github.com/pear-studio/nonebot-dicepp/tree/main/docs/agent/skills/review4-execute
Command: npx skills add https://github.com/pear-studio/nonebot-dicepp --skill review4-execute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates risky, premature coding by executing only the explicitly finalized and accepted “consensus implementation” items from a review record, while refusing to proceed when any pending or needs-clarification items remain.

Core Features & Use Cases

  • Consensus-only execution: Implements only entries marked as 已共识·实施, while skipping 已共识·存档 and other non-implementation outcomes.
  • Strict refusal gates: Refuses to execute if the document still contains 需补充回复 or 待裁决 items, and blocks execution unless the stage 3 checklist is completed based on a fresh re-read.
  • Change traceability & safety: Requires the user to explicitly provide the document path, confirms authorization before making code changes, runs project tests, and marks stage 4 after completion.

Quick Start

Provide the review document path (for example, review4-execute .temp/review-250416-1430-persona.md) and ask the Defender to implement the agreed 已共识·实施 items.

Frequently Asked Questions about review4-execute

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

FAQPage Schema
How do I execute only approved code changes from a review document?▼

To execute approved code changes, you provide the review document path and the workflow applies only finalized consensus implementation entries while skipping archived items, ensuring changes match the accepted review scope.

What happens to pending or unresolved items during consensus code execution?▼

Pending or unresolved items block consensus code execution entirely. The workflow refuses to proceed if the review document still contains reply-completion or arbitration-pending items, enforcing strict gating until all entries are finalized.

How does adversarial review workflow gating prevent premature code changes?▼

Adversarial review workflow gating prevents premature code changes by requiring a fresh re-read of the review document to validate stage 3 checklist completion before authorizing any implementation modifications.

Can I run project tests automatically after implementing finalized review diffs?▼

Yes, you can run project tests automatically. The execution workflow runs relevant project tests after transforming approved review diffs into actual code changes and sets stage 4 only after successful test completion.

Do I need explicit user authorization to implement consensus code changes?▼

Yes, explicit user authorization is required. The workflow honors explicit user consent before performing any code modifications within the confirmed subset of the review document to maintain change traceability and safety.

Related Skills

Explore More Software Engineering Skills→
pear-studiopear-studio
34

review3-confirm

Confirm Review-Reply items into consensus, deferment, denial, or clarification states.

Community
Advanced
lutzcc1lutzcc1

pr-feedback-addresser

Plan and apply code changes for PR review comments with RuboCop and tests.

Community
Intermediate
yxc023yxc023

todo-resolve

Resolve ready todos in parallel and document lessons learned.

Community
Advanced
discountrydiscountry
1

codex

Execute OpenAI Codex CLI commands for code analysis, refactoring, and automated editing.

Community
Advanced