hrt-mr-brief

Adapted from the pr skill in mattpocock/skills (MIT), which credits Dex Horthy's show-me skill (humanlayer). The three-section shape is theirs. What changes here: the output is a file in the change directory, not a PR body, and every section is sourced from this change's artifacts instead of the agent's memory.

Why this exists

A reviewer of a merge request sees the diff. The reasoning behind it lives in discovery.md, design.md, align.md, and specs/**/*.md, which the reviewer may never open. mr-brief.md is the one file that tells the reviewer what changed, proves it works, and says what it costs to be wrong.

This skill only writes the file. The user commits it with the code and posts its content wherever their review happens. The skill never posts anything and never runs git.

When to run

Once, at the end of apply, after hrt-apply-code-review has finished. Write mr-brief.md next to tasks.md in the change directory. If it already exists, rewrite it from the current state, do not append. Write the final version once, before the user commits, and tell the user to include the file in that commit.

If the review loop ended with unresolved HIGH findings (RELEASE BLOCKER), still write the file. The blocker goes first under Merge Danger, stated plainly.

Inputs

Read only these. Anything you cannot find in them, you do not write.