Turn the actual staged or branch diff into a concise, five-section pull request description.
git diff --cached for the exact staged change when no branches are requested.BASE...HEAD comparison for a branch pull request.--name-status output for added, modified, deleted, and renamed paths.It confirms the current directory is a Git repository before reading. It does not need network access for the core workflow.
The result is Markdown with exactly five top-level sections:
If the selected diff contains no changes, the skill does not infer a file list from recent commits. It returns a valid template stating that no code changes were detected and that no files changed in the selected diff. Commit subjects may be mentioned only as unverified background.
The workflow reads Git state and returns text. It does not stage files, run tests, create a branch, push commits, or open a pull request. Its Test Plan and Checklist items are prompts, not claims that the checks passed.
A diff can show what changed without proving the business reason, incident context, rollout plan, or reviewer assignment. Add that author or issue context when it is absent. The generated Markdown is portable, but the package does not automate GitHub, GitLab, or Bitbucket APIs.
Use the guide to choose the correct diff, preserve Git's exact file scope, separate completed tests from checks still needed, and tell reviewers where risk lives.
Read the pull request description guide →Generate a complete pull request description from your staged changes, commits, and branch diff: summary, changes, test plan, and checklist, ready for GitHub, GitLab, or Bitbucket. Cross-checks the file list against what git actually reports,…
Generate a complete pull request description from your staged changes, commits, and branch diff: summary, changes, test plan, and checklist, ready for GitHub, GitLab, or Bitbucket.….
Do not treat a successful run as proof beyond the supplied files, declared scope, and evidence the skill actually checked.
It reads either the staged diff or a user-named base-to-head branch comparison, the matching name-status file list, and the five most recent commit subjects for context. The selected diff controls claims about what changed.
It returns Markdown with exactly five top-level sections: Summary, Changes, Test Plan, Screenshots, and Checklist. Changed files preserve the paths and statuses reported by Git.
Yes. It uses git diff --cached when no branch comparison is requested and a three-dot git diff BASE...HEAD when the user supplies the branches.
It returns a structurally valid template that says no changes were detected. Recent commits may be labeled as background, but they are not presented as files or behavior in the selected diff.
No. It generates the Markdown body from read-only Git inspection. The test plan contains unchecked verification prompts, and the user or another approved workflow runs tests and creates the pull request.
No. A diff and commit subjects may show what changed without proving why the work matters. Add the issue, ticket, incident, or author context when that purpose is not present in the repository evidence.
Current price and purchase option are shown on Agensi. PR Template Generator works with agents that read SKILL.md and keeps the core workflow local and read-only.
Get PR Template Generator on Agensi