How do I install the Mass Pr Description skill?

Run npx skillmds@latest add maiconsouza89/mass-pr-description in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Mass Pr Description safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mass Pr Description?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mass Pr Description free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under CC-BY-4.

Who published Mass Pr Description?

maiconsouza89 (@maiconsouza89) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mass Pr Description by maiconsouza89

Name: Mass Pr Description
Rating: 4.666666666666667 (3 reviews)
Author: maiconsouza89

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).

maiconsouza89 Updated Sep 22, 2026

File contents

Pull request description

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

Steps

Collect the evidence: git log --oneline <base>..HEAD and git diff --stat <base>..HEAD, where <base> is the target branch (usually main).
Summary: two or three sentences on what changes for a user or a maintainer. Lead with the outcome, not the mechanism.
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.
Changes: one bullet per coherent change, in the order a reviewer should read them.
How to test: the exact commands and what to look for. pnpm check is always the first.
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.

Frequently asked questions