Automated summary
Generates a structured pull/merge request description once the code review has passed, following the format defined in claude/templates.md.
Strengths
- Explicitly checks its prerequisites (a /review verdict of PASS with confidence ≥ 95, green tests, no blocking issues) before writing anything
- Reuses the project's template from claude/templates.md and falls back to a complete default format (What / Why / How / Testing / Checklist) when none exists
- Gathers real change context through git diff --stat and git log over the main...HEAD range
- Shows the description and the git push command before pushing, and waits for explicit confirmation
Limitations
- Tightly coupled to its ecosystem: the /review skill, claude/build.md for the test command, and claude/templates.md must all exist
- Does not perform the review or fix anything: if tests fail it simply stops without suggesting a remedy
- Assumes the main branch is called main and relies on the linked ticket being available outside the repository
Use it right after a successful review, when the branch is ready to be proposed for merge and the PR/MR description still needs to be written.
Avoid it when tests are not green or the review has not yet returned a PASS verdict, since the skill will then refuse to generate the description.
Security analysis
SafeThe skill only generates PR descriptions; it reads local files and runs read-only git inspection commands (diff --stat, log). No writes, no network, no destructive or exfiltration behavior, and it explicitly requires user confirmation before pushing. Push is left as a proposed command the user must approve, which is a good safeguard.
No concerns found
How this analysis is madeExamples
/review is green on my feature branch — generate the PR description for merging into main.Write the MR description for the branch feat/PAY-412-refund-flow; the ticket is PAY-412.Generate a PR description using our claude/templates.md format, then show me the git push command and wait for my go-ahead.name: mr description: Generate a PR/MR description after the review passes. Use after /review confirms the code is ready to merge. Reads claude/templates.md for the required format.
MR/PR Description Skill
Generate a structured pull request description.
Prerequisites
/reviewMUST pass (verdict: PASS, confidence ≥ 95) before generating a PR description- All tests must be green
- No blocking issues from the review
Protocol
1. Verify prerequisites
# Confirm tests pass
# (use the test command from claude/build.md)
If tests fail: STOP. Fix before generating the PR description.
2. Read the PR template
Read claude/templates.md — the required PR/MR format for this project.
3. Gather the diff
git --no-pager diff main...HEAD --stat | head -50
git --no-pager log main...HEAD --oneline | head -20
4. Read the linked ticket (if any)
If a ticket number is referenced, extract the requirements from it.
5. Generate the PR description
Use the template from claude/templates.md. If no template exists, use this default:
## What
<One paragraph: what does this change do and why?>
## Why
<One paragraph: what problem does this solve? Link to ticket.>
## How
<Bullet list: key implementation decisions and approach>
## Testing
<What was tested? How? Test commands run + results>
## Checklist
- [ ] Tests pass
- [ ] No new warnings
- [ ] Documentation updated (if applicable)
- [ ] Breaking changes documented (if applicable)
6. Present to user
Show the PR description and proposed git push command. Wait for confirmation before pushing.
Rules
- NEVER generate a PR description before review passes
- NEVER include implementation details that would confuse reviewers
- NEVER push without explicit user confirmation
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/generate-pr-mr-description-mrwak90u/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/generate-pr-mr-description-mrwak90u' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/generate-pr-mr-description-mrwak90u/download' --output '.skill-downloads/generate-pr-mr-description-mrwak90u/SKILL.md.part' && mv '.skill-downloads/generate-pr-mr-description-mrwak90u/SKILL.md.part' '.skill-downloads/generate-pr-mr-description-mrwak90u/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Original excerpt: Prerequisites
/reviewMUST pass (verdict: PASS, confidence ≥ 95) before generating a PR description- All tests must be green
- No blocking issues from the review
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/generate-pr-mr-description-mrwak90u/SKILL.md' && test -s '.skill-downloads/generate-pr-mr-description-mrwak90u/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/mr' && cp -R '.skill-downloads/generate-pr-mr-description-mrwak90u' '.claude/skills/mr'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/generate-pr-mr-description-mrwak90u'openskills read 'generate-pr-mr-description-mrwak90u'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/generate-pr-mr-description-mrwak90u/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.