Menu
Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.
Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/gittower/git-flow-next --skill pr-summaryLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
Basé sur la classification professionnelle SOC
Affichage de SKILL.md
| name | pr-summary |
| description | Generate a PR summary and write to .ai/ pr_summary.md |
| allowed-tools | Read, Grep, Glob, Write, Bash |
Generate a pull request summary based on branch changes.
Gather Context
.ai/ workflow folder for this branch:
feature/59-no-verify): look for .ai/issue-59-*feature/worktree-support): look for .ai/feature-worktree-support/ or .ai/worktree-support/ls .ai/ and match based on branch name patternsconcept.md - Feature concept and design rationaleanalysis.md - Issue analysis and requirementsplan.md - Implementation plan with specific changesAnalyze Changes
# All commits on this branch
git log main...HEAD --oneline
# Full diff
git diff main...HEAD --stat
git diff main...HEAD --name-only
Generate Summary
Read .github/PULL_REQUEST_TEMPLATE.md for the format specification and example.
Use context from the .ai/ folder files to write a better summary:
Write the summary to .ai/<folder>/pr_summary.md.
Validate Format
Before presenting the create command, run pr_summary.md through the
posting checklist (mechanical + tone),
then check it against .github/PULL_REQUEST_TEMPLATE.md. A PR body is a
GitHub-only artifact — it never enters git history, so unlike commit
messages it is not caught by code review, and it posts via gh so no hook
reminder fires. This step is that missing gate. Reject and rewrite the
summary if any of these fail:
Resolves/Closes/Relates #N)<!-- ... --> comments,
author checklist, or example text copied from the templateCo-Authored-By commit trailers only## Remarks and **Review focus:** sections, if present,
match the template's shapeIf it fails, fix pr_summary.md and re-check before continuing. This same
check applies to any skill that posts a PR body directly (see
/resolve-issue, /takeover-pr).
Create PR Command
Output the gh pr create command:
gh pr create --title "<title>" --body "$(cat .ai/<folder>/pr_summary.md)"
Report Completion
Follow the Pull Request Titles rules in
COMMIT_GUIDELINES.md — same subject format as
commits: type(scope): Subject.