Best fit
Prepare a pull-request description from a branch diff and commit history.
// reviewer handoff
PR Template Generator
Turn the actual staged or branch diff into a concise, five-section pull request description.
Format: Agent skill, not a browser app. You need an AI agent that can load its instructions and use the required tools.
Package requirements: Agents that read the open SKILL.md format. Verify runtime and service requirements at the purchase or install destination.
You get: A draft summary, change list, test plan and checklist, cross-checked against Git’s reported files. Review test claims before submitting.
Licence and purchase details
Review the package licence at the destination.
Review the offer and access method at your chosen marketplace. Agensi provides connected-agent access, not a download. Buying a skill does not include an AI-agent subscription or setup service.
Inputs it uses
git diff --cachedfor the exact staged change when no branches are requested.- A user-named
BASE...HEADcomparison for a branch pull request. - The matching
--name-statusoutput for added, modified, deleted, and renamed paths. - The five most recent commit subjects as context, checked against the selected diff.
It confirms the current directory is a Git repository before reading. It does not need network access for the core workflow.
The output contract
The result is Markdown with exactly five top-level sections:
- Summary - one to three concise bullets supported by the diff.
- Changes - Git's exact status and path plus a file-level description.
- Test Plan - unchecked prompts for automated, manual, and edge-case verification.
- Screenshots - an explicit not-included note unless the author adds UI evidence.
- Checklist - tests, documentation, linting, formatting, and unintended-diff review.
A representative result
## Summary
- Reject expired sessions before account lookup.
## Changes
- M `src/session.ts` - adds the expiry guard.
- M `tests/session.test.ts` - covers expired and valid sessions.
## Test Plan
- [ ] Run the focused session tests.
Empty diffs stay honest
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.
Boundaries and limitations
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.
Build the reviewer map from evidence
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 →// choose with context
Is PR Template Generator the right skill?
It returns
A draft summary, change list, test plan and checklist, cross-checked against Git’s reported files. Review test claims before submitting.
Do not use it as
Do not treat a successful run as proof beyond the supplied files, declared scope, and evidence the skill actually checked.
Compatibility, access, version, and licence
- Reads or accesses
- Only the files or context you deliberately provide; review the listing before granting additional access.
- Compatibility
- Agents that read the open SKILL.md format. Verify runtime and service requirements at the purchase or install destination.
- Version
- Verify the current package version at the linked destination.
- Licence
- Review the package licence and seller terms at the linked destination.
Questions
What does PR Template Generator read?
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.
What does it return?
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.
Does it work with staged changes and branch pull requests?
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.
What happens when the selected diff is empty?
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.
Does it run tests or create the pull request?
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.
Can it guarantee the description explains the business reason?
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.
Describe the diff the reviewer will see.
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