Menu

Individual skill

pr-writeup

Write or refresh a pull/merge request description a reviewer can follow in one read: the problem as a visitor saw it, a before/after table of the values that changed, reviewer notes, matching before/after screenshots committed with the PR under `.github/pr-assets/<topic>/` (the branch name, `/` → `-`), and a concrete test plan, with the text put through the `work-humanizer` skill and its check before it goes up. Use it when a PR/MR is opened or updated and needs a description, e.g. "write the PR description", "add screenshots to the PR", "update the PR after review", "refresh the before/after shots". Not for commit messages or release notes. Optional argument: the PR/MR number or URL.

theme-meridian/.agents/skills/pr-writeup/SKILL.md

Read pinned source

Source commit d66f0fd9976e15ca51d6fcd5352482c5c66c281b

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Local scripts
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
18
Repository last updated
Nov 5, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# PR write-up

**When to use:** a PR/MR exists (or is about to) and its description has to carry the
change to a reviewer: what was wrong, what changed, with numbers, what the reviewer should
know, how it looks before and after, and how to test it. Also when review feedback changes
the work and the description, table and screenshots need a refresh.

Stack-agnostic. Requirements, all optional except the forge CLI:
- **Forge CLI:** `gh` (GitHub) or `glab` (GitLab), picked from the remote host
  (`git remote get-url origin`).
- **A browser you can drive** for screenshots: the `agent-browser` CLI, Playwright, or the
  Chrome DevTools MCP. Without one, skip screenshots and say so.
- **python3** for the humanizer check, plus **Pillow** (or ImageMagick) for cropping.