Catalog
Yeachan-Heo/pr

Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.

NewUpdated Oct 13, 2026

PR Body

When work lands behind a review, the PR body is the one artifact a reviewer outside the session reads. Everything it needs already exists in the paper trail — this skill assembles it and adds nothing that was not already established. The summary-visual discipline is inspired by show-me (credited in the frontmatter).

Template

## Summary
<one-line claim, then the smallest visual that proves it>

## Evidence
- **Before:** <output / failing check>
  **After:** <output / passing check>

## Reversibility
<Rollback: cheap via <mechanism> | expensive because <reason>>
<Blast radius: one line>

Sections

Summary

State the change in one sentence, then show the smallest view that makes the point. Match the visual to the change:

  • logic or an algorithm → pseudocode
  • runtime control flow → a call tree
  • UI structure → a component tree
  • file responsibility or a broad refactor → a shallow file tree
  • component interaction or data flow → a Mermaid diagram
  • the delta itself → a diff shaped like the change (component, layout, call tree, or state machine)

Show the whole block only when most of it is new, omitted context would hide ownership, or the reviewer needs a copyable target shape. One visual usually suffices; never all forms.

Evidence

Consume the verify protocol's output — BUILD, TEST, LINT, FUNCTIONALITY evidence, freshness rule inherited. Present before/after pairs: the exact check that failed before and passes after, quoted from the output itself. When the change is visual, prefer a captured screenshot; qa-tester can drive the runtime for one. Never re-collect evidence here and never claim evidence the verify pass did not produce.

Reversibility

Run the ADR test on the diff itself — the same three questions launch applies to decisions: hard to reverse? surprising without context? the result of a real trade-off? A no on all three is a cheap rollback: say by what mechanism (revert the merge, toggle the flag). Any yes means an expensive rollback: say why. Classify the door first: a two-way door (undo is cheap and ordinary) needs no ceremony beyond naming the undo; a one-way door says so explicitly and names what makes the step irreversible. Link the ADR when the change implements or touches one. Close with the blast radius in one line — what else this change can move.

Language

Terms come from GLOSSARY.md where a glossary exists (legacy yards not yet migrated keep it in CONTEXT.md). The PR is read outside the session; the glossary is the only vocabulary the reader shares with it.

Triggers

  • launch Phase 5, when the platform reviews through PRs: the completion report carries a PR body drafted by this skill.
  • Any session that opens or materially updates a PR.

Output

  • The PR body, ready to paste
  • The paper-trail pointers it relies on (verify evidence, ADRs, spec)
Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

76/100

Grade

B

Good

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

92

Quality

72

Clarity

78

Completeness

64

Summary

This skill guides AI agents to draft well-structured PR bodies by assembling evidence and documentation from an existing paper trail (verify outputs, ADRs, glossary). It prescribes a three-section template (Summary with visual proof, Evidence with before/after pairs, Reversibility analysis) and emphasizes consuming only pre-existing artifacts without re-collecting data.

Detected Capabilities

read verification outputsread ADR and glossary filesassemble markdown documentationpresent git diffs and visualsstructure code review documentation

Trigger Keywords

Phrases that agents use to match this skill to user intent.

draft pr bodysummarize change evidencepr template assemblyreversibility assessmentbefore after verification

Referenced Domains

External domains referenced in skill content, detected by static analysis.

github.com

Use Cases

  • Draft PR bodies for code reviews with minimal visual evidence
  • Summarize changes with before/after verification outputs
  • Assess rollback difficulty and blast radius for changes
  • Create review-ready documentation from existing ADRs and verify logs
  • Present UI or architectural changes as diagrams or diff shapes

Quality Notes

  • Strong conceptual framework with clear discipline derived from established practices (summary-visuals, verify protocol, ADR pattern)
  • Well-scoped guidance — skill operates strictly within documentation assembly; no file writes, no destructive ops
  • Excellent discipline around evidence freshness: explicitly prohibits re-collection and requires consuming only verify protocol outputs
  • Template is practical and well-reasoned with clear visual matching guidance (logic→pseudocode, UI→component tree, etc.)
  • Glossary reference shows awareness of shared vocabulary across teams and legacy projects
  • Missing: concrete examples of PR bodies using this template, no runnable validation pattern for what constitutes 'smallest visual', no guidance on when to omit context vs. show full blocks
  • Incomplete: 'paper trail' and 'verify protocol' concepts are assumed to exist in the user's workflow but are not defined in this skill — external dependency not documented
  • No guidance on handling missing evidence (e.g., verify pass did not run, no ADR exists for the change)
  • Triggers are contextual (Phase 5, PRs) but not tied to specific commands or file patterns
Model: claude-haiku-4-5-20251001Analyzed: Oct 13, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

  1. v1.1

    Content updated

    ✦ AIExpands Reversibility guidance to classify one-way vs. two-way doors and updates glossary file reference to GLOSSARY.md.

    2026-10-13

    LATEST
  2. v1.0

    2026-10-02

    View This VersionInitial version

Use Yeachan-Heo/pr in your dev environment

Command Palette

Search for a command to run...