Evidence record · captured 2026-10-11

PR Description Writer

Writes or refreshes pull-request titles and bodies as a cover note for reviewers rather than a changelog or file-by-file list: the agent inspects the branch, working tree, existing PR, base branch, commits and full diff with git and gh, then drafts a concise title and body and updates the PR.

Community publisherUnverifiedSource reviewedBehavior not tested

Source review

Editorial assessment

This is a source-only assessment. It does not claim runtime or security testing.

What it does

Reframes the PR body as a reviewer cover note: the agent reads the full branch diff against the real base, writes a conventional title, and picks the smallest body shape, with no default Test Plan.

Best for

Opening a pull request from a finished feature branch
Refreshing a PR title and body after follow-up commits change its scope or risk
Describing a breaking or contract change with before/after examples and migration notes

Strengths in the source

Uses the existing PR's baseRefName, or the repository default branch, and reviews the full branch diff rather than only the latest commit.
Maps change types to body shapes in a table, such as compatibility and migration guidance for contract changes and a review starting point for broad changes.
Forbids pasted CI logs, command transcripts, exhaustive file lists, customer names, emails and secrets, and allows issue references only when verified.
On refresh it rewrites the description around the current diff instead of narrating review history, and it skips refreshes for typo-only or rename-only commits.

Limitations

Acts on the real GitHub repository: it needs an authenticated gh, creates draft PRs, and edits existing PR titles and bodies through gh api.
Creates a feature branch first if run on main or master, and expects the intended changes to be committed before it writes anything.
Encodes Sentry conventions, including a fixed list of title types and, per its SPEC.md, ignoring repository PR templates, which may clash with other teams' rules.

When not to use it

Repositories that require a specific PR template or checklist to be filled in.
Reviewing someone else's PR; the skill writes descriptions, it does not review code.

Reviewed by Retenta editorial on 2026-10-11; scope: source only.

Files included in this review

skills/pr-writer/SKILL.md

Evidence and boundaries

Execution · not tested

Retenta has not executed this skill.

Security · not tested

The skill folder bundles no executable scripts. Retenta has not run a security scan.

Pinned publisher source: skills/pr-writer/SKILL.md
Revision: d18b7aa8ba878354e5c348310230e652f7690f9c
License evidence: Apache-2.0Retenta preserves the license text captured with this immutable upstream snapshot; no independent legal or security review is claimed.
Last source change: 2026-07-15
Independent verification: Published by Sentry, which does not own the product this skill covers. Not independently verified.
Upstream repository: Open publisher repository