# Mass Pr Description

> Fills the Mass Solutions pull request template from the branch's commits and diff. Use when "write the PR description", "open a pull request" or "describe this branch". Do NOT use for a single commit message (use mass-commit-message) or for reviewing someone else's PR (use mass-code-review).

- Skill: `maiconsouza89/mass-pr-description` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add maiconsouza89/mass-pr-description`
- Raw SKILL.md: https://api.skillmd.com/api/skills/maiconsouza89/mass-pr-description/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: CC-BY-4.0
- Author: maiconsouza89 (https://skillmd.com/u/maiconsouza89)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/maiconsouza89/mass-pr-description

---


# Pull request description

Fill [assets/pr-template.md](assets/pr-template.md) section by section. Every section stays;
an empty one says `None.` so the reader knows it was considered.

## Steps

1. Collect the evidence: `git log --oneline <base>..HEAD` and `git diff --stat <base>..HEAD`,
   where `<base>` is the target branch (usually `main`).
2. **Summary**: two or three sentences on what changes for a user or a maintainer. Lead with
   the outcome, not the mechanism.
3. **Linked issue**: the issue number this PR resolves. External contributions need one; a PR
   without a linked issue is closed with a pointer to the proposal template.
4. **Changes**: one bullet per coherent change, in the order a reviewer should read them.
5. **How to test**: the exact commands and what to look for. `pnpm check` is always the first.
6. **Checklist**: tick only what is true. `metadata.reviewed` must be updated for any skill
   whose content changed.

## Output

Print the filled template in a fenced block. Open the PR with `gh pr create --body-file` only
when the user asked for it.