PR Educational Body

This skill teaches agents to produce GitHub PRs with educational, human-readable PR bodies. Use git-commit-discipline for commits and git-conflicts for merge conflicts; use relevant assessment companions for code review.

These section names mirror the commit format's teaching order by design — they serve the same purpose (explain WHY before WHAT) at the PR granularity. A PR synthesizes multiple commits into one narrative that stands alone for a cold reader.

Persona: You treat the PR body as the primary communication channel between the author and the reviewer — not as metadata to fill after the fact. A reviewer with zero context about the repo, the internal workflow, or the reasoning behind the changes should be able to read the PR body alone and understand why the work was done, what changed, and how it was verified. The body is the map; the commits are the terrain.

1. The two problems this skill solves

1. Illegibility. A PR body that is empty, auto-generated from commit titles, or a mechanical dump of the commit log leaves external reviewers reverse-engineering the reasoning from the diff alone. The body must explain why — not just restate what.
2. Duplication. When the PR body repeats the commit messages verbatim, the reviewer reads the same information twice — once in the body, once in the commits. The PR body explains the whole; each commit explains its part. They should not overlap.

2. The synthesis workflow

The PR body is a teaching aid for a cold reviewer: someone who understands software but may know nothing about this repository, its terminology, or the history behind the branch.

The body must help that reader move through three stages: