skills.rest
tribedotrun
tribedotrunOFFICIAL
Explore all skills by this author →
GitHub

mando-pr-summary

Generate an ASCII PR summary diagram and reviewer checklist for GitHub pull requests.

8|1|Updated Mar 29, 2026
Search Tags:#automation#diagram#pull-request#gh-cli#review-checklist#pr-summary#evidence-upload
One-click install
npx skills add https://github.com/tribedotrun/mando --skill mando-pr-summary
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mando-pr-summary
Source: https://github.com/tribedotrun/mando/tree/main/bundled-skills/mando-pr-summary
Command: npx skills add https://github.com/tribedotrun/mando --skill mando-pr-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes manual effort from documenting and communicating the intent and verification steps of a code change by generating a canonical PR body, an ASCII architecture/flow diagram of the diff, and an actionable reviewer checklist; it can also auto-create a PR when none exists.

Core Features & Use Cases

  • End-to-end PR body generation: Reads the branch diff, composes a Problem/Solution/Evidence/Testing canonical PR description, and updates the PR body.
  • ASCII architecture diagram: Produces a padded box-drawing diagram that documents triggers, data paths, parallel boundaries, cache patterns, and response shapes; includes an alignment fixer script.
  • Reviewer checklist & verification: Creates a universal checklist augmented by repository-specific items and flags missing E2E verification; uploads or references local evidence artifacts to GCS or GitHub releases.
  • Auto-creation & persistence: Auto-creates a minimal PR when absent, saves a work-summary artifact to the todo DB, and writes plan artifacts into .ai/plans/pr-<n>/ when applicable.

Quick Start

Generate an ASCII PR summary diagram, a reviewer checklist, and update the current branch's PR description so reviewers have a single canonical source of truth.

Frequently Asked Questions about mando-pr-summary

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

FAQPage Schema
How do I automatically generate a PR summary and reviewer checklist from a git branch?▼

To generate a PR summary and reviewer checklist automatically, you can use a tool that reads the local git branch diff and composes a canonical PR body with verification steps. This Skill automates that process by producing an ASCII architecture diagram and a reviewer checklist from the branch diff.

What is an ASCII architecture diagram for a pull request and when do I need one?▼

An ASCII architecture diagram for a pull request visually documents triggers, data paths, and parallel boundaries within the code diff. You need this format when reviewers require a lightweight, text-based flow representation directly in the PR body without rendering external images.

Can I auto-create a GitHub pull request and update its body using gh CLI?▼

Yes, you can auto-create a GitHub pull request and update its body using gh CLI. This Skill requires gh CLI access and local git branch context to auto-create a minimal PR when none exists and then updates the PR description with the generated summary.

How do I upload code review evidence artifacts to GCS or GitHub releases?▼

To upload code review evidence artifacts to GCS or GitHub releases, you need a tool with appropriate upload privileges that references local files. This Skill augments the reviewer checklist by uploading or referencing local evidence artifacts to GCS or GitHub releases for verification.

Does this PR summary generation approach work for branches that lack an existing pull request?▼

Yes, this PR summary generation approach works for branches lacking an existing pull request. The Skill auto-creates a minimal PR when absent and applies to code review workflows where branches may lack PRs, diffs, or evidence artifacts.

What are the limitations of generating reviewer checklists from branch diffs?▼

A limitation of generating reviewer checklists from branch diffs is that the tool flags missing E2E verification if artifacts are absent. The process requires local git branch context and gh CLI access, and evidence persistence depends on having GCS or GitHub release upload privileges.

Related Skills

Explore More Software Engineering Skills→
anshul-garg27anshul-garg27

pr-create

Generate structured GitHub pull requests from branch commits and diffs.

Community
Advanced
YunosukeYoshinoYunosukeYoshino

pr

Verify quality gates and artifacts before generating a PR summary and Codex review request.

Community
Intermediate
podonospodonos
8

release-pypi

Automate Python SDK releases from version bumping to PyPI publishing.

Official
Advanced
GabeujinGabeujin

plantuml-ascii

Generate ASCII art diagrams from PlantUML definitions via command-line tools.

Community
Basic