skills.rest
arch-team
arch-teamCOMMUNITY
Explore all skills by this author →
GitHub

pace-review

Generate human-readable review summaries for code changes in the in_review state.

73|6|Updated Feb 20, 2026
Search Tags:#automation#git#quality assurance#code review#development workflow#traceability
One-click install
npx skills add https://github.com/arch-team/devpace --skill pace-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pace-review
Source: https://github.com/arch-team/devpace/tree/main/skills/pace-review
Command: npx skills add https://github.com/arch-team/devpace --skill pace-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of human-readable review summaries for code changes, ensuring quality and traceability throughout the development lifecycle.

Core Features & Use Cases

  • Automated Review Summaries: Generates concise summaries of code changes, highlighting key aspects for human reviewers.
  • Traceability: Links code changes back to business goals, providing a clear value chain from Epic to code.
  • Impact Analysis: Detects cross-impact between multiple active changes to prevent conflicts.
  • Use Case: When a feature branch is ready for review, this Skill automatically creates a summary detailing the changes, their business justification, potential conflicts with other branches, and any identified quality concerns, significantly speeding up the approval process.

Quick Start

Use the pace-review skill to generate a summary for the code changes currently in the review state.

Frequently Asked Questions about pace-review

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

FAQPage Schema
How do I automate code review summaries for git branches?▼

Automated code review summaries are generated by analyzing git changes in the 'in_review' state, performing cross-impact scanning, intent consistency checks, and tracing business lineage back to the Epic level to highlight potential issues for human approval.

What is business traceability in a development workflow?▼

Business traceability in a development workflow links code changes directly back to business goals, providing a clear value chain from the Epic level down to the specific implementation to ensure development alignment.

How do I detect cross-impact conflicts between active code changes?▼

Cross-impact conflicts between active code changes are detected through automated scanning during the review phase, which analyzes multiple branches to identify potential conflicts and prevent integration issues before human approval.

Does the code review summary format adapt to change request complexity?▼

The code review summary format adapts dynamically based on change request complexity, categorizing changes into S, M, L, and XL sizes to appropriately scale the depth of the generated review output.

Can I use adversarial reviews to identify quality assurance issues before approval?▼

Adversarial reviews identify quality assurance issues by automatically challenging the code changes during the review state, exposing potential flaws and intent inconsistencies for human reviewers prior to final approval, rejection, or revision.

Related Skills

Explore More Software Engineering Skills→
hashintelhashintel
1.6k

managing-git-workflow

Automate HASH git workflow with branch naming, PR creation, and reviews.

Official
Intermediate
allan-mobley-jrallan-mobley-jr
1

revise

Address GitHub PR review feedback by applying fixes and running checks.

Community
Advanced
matteotittamatteotitta
29

weekly-plan

Scan Gmail, Slack, Granola, and Calendar to synchronize tasks in Linear and Paperclip.

Community
Advanced
lehuuhau1231lehuuhau1231

code-review-checklist

Analyze source code against structured checklists for quality, security, and performance.

Community
Intermediate