// Generates a PR description focused on business value using the project's PR template. Analyzes branch changes and writes a clear, user-facing explanation of what changed and why. Use when the user asks to create/write/generate a PR description, or invokes /pr-description.
| name | pr-description |
| description | Generates a PR description focused on business value using the project's PR template. Analyzes branch changes and writes a clear, user-facing explanation of what changed and why. Use when the user asks to create/write/generate a PR description, or invokes /pr-description. |
| user_invocable | true |
| version | 1.0.0 |
Generates pull request descriptions focused on business value — what changed for the user/administrator/developer and why it matters. Avoids describing code-level changes; instead explains the observable impact.
If no arguments provided, analyze the current branch.
Use the pull-request-diff-fetcher skill to fetch PR data (diff, metadata, commits). Invoke it with the PR number/URL or "current-branch" if no PR was provided.
The skill handles method selection (gh CLI → WebFetch → local git), base branch detection, and diff completeness verification automatically.
Read the diff carefully. For each changed area:
Do NOT just list files or describe code modifications. Think about the business impact.
Evaluate the current PR title (or branch-derived title) against these criteria:
mg/param-values-uniq or feature/xyz are not good titlesIf the title is poor (e.g., auto-generated from a branch name, too vague, or too long), suggest an improved title. Always present the suggestion to the user — do not apply it without confirmation.
Examples of bad → good:
| Bad | Good |
|---|---|
Mg/param values uniq | Enforce unique parameter values at database level |
fix stuff | Fix GoPay cron failing on demo payment transactions |
Feature/admin domain tabs | Add direct linking to domain-specific admin pages |
Load the PR template from .github/PULL_REQUEST_TEMPLATE.md and fill in each section with the analyzed content.
Fill the description section with a business-value-focused explanation (1-3 paragraphs covering what changed from the user's perspective, the motivation, and the new behavior). Fill other sections as appropriate (e.g., "closes #123" or "N/A" for fixes, check the license checkbox).
Show the generated description to the user. If the title needs improvement, show the suggested title as well.
If updating an existing PR:
Before replacing the body, check the existing PR description for:
<!-- Replace --> markers (e.g., live preview links) — preserve these blocks exactly as they are.closes #123) — carry them over into the updated description.These are managed externally and must not be lost.
Ask the user if they want to apply the description (and title if suggested), then:
gh pr edit {PR_NUMBER} --body "{description}"
gh pr edit {PR_NUMBER} --title "{new_title}" # only if user confirms
If no PR exists yet:
Show the description (and suggested title) and tell the user it's ready to use when they create the PR.
#### Description, the reason for the PR
Demo data payment transactions were created with `CREATED` status, causing the GoPay cron job to attempt updating non-existing payment transactions and fail. Changed statuses to final ones (`CANCELED`, `TIMEOUTED`) so the cron skips them.
#### Description, the reason for the PR
This PR makes domain-specific administration pages directly linkable.
Until now, pages with administration domain tabs have always opened in the domain stored in the administrator session. That meant links could lead to the correct agenda, but not to the correct domain tab. In practice, administrators still had to switch the domain manually before they could fix the reported problem.
This change adds support for switching the selected administration domain directly from a link. As a result, links from domain-specific warnings, such as required settings notifications, can open the target page in the exact domain context that needs attention.
#### Description, the reason for the PR
Changed `PaymentTransactionDataFactory.php` to use `CANCELED` and `TIMEOUTED` constants instead of `CREATED`. Also updated `PaymentTransactionData` constructor default value.
This is bad because it describes code changes, not the business impact.
Drives `php bin/console monorepo:release` end-to-end. Runs pre-flight checks, starts the releaser, watches for confirm prompts, auto-presses Enter on prompts that are safe (waitFor already verified readiness, or ceremonial), and surfaces judgement calls to the operator via AskUserQuestion. Use when the user invokes /release.
Calls the GitHub REST API via `gh` to generate release notes for the given tag (the same content the "Generate release notes" button produces on the web UI) and inserts the result into the matching CHANGELOG-X.Y.md file. Used standalone or by the /release orchestrator when UpdateChangelogReleaseWorker is up next.
Create a Shopsys-style enum (a class extending AbstractEnum with public typed constants, NOT a native PHP enum). Use when you need to define a fixed set of values that downstream projects (like project-base) might extend or restrict.
Generates structured upgrade notes for a pull request based on diff analysis.
Analyzes PR diffs to identify breaking changes, feature movements, and scope
Commit Command — Analyzes uncommitted changes and creates logical, atomic, grouped commits following Shopsys commit guidelines. Use when the user asks to commit, create commits, or invokes /commit.