Menu
Generate a PR description for the current branch. Writes Markdown to .git/magit/posts/new-pullreq for use with magit-forge.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use the Xero MCP server — obtain/refresh OAuth2 bearer tokens, troubleshoot authentication, and pick up other operational notes for working with Xero MCP tools. Use when Xero MCP tools fail with authentication errors, when the bearer token has expired (tokens last ~30 min), before starting any Xero workflow, or for general guidance on Xero MCP usage.
General Xero browser automation notes. Use when automating any Xero page with agent-browser — covers non-standard UI patterns, waiting, and dropdown menus.
Size the agent-browser Chromium window to fill its current screen, leaving a configurable bottom margin for the desktop panel. Use before any agent-browser automation that needs the full screen visible without elements overlapping or scrolling off (e.g. Xero, dense web apps).
Review all unreviewed documents in Hubdoc. Use when reviewing, processing or publishing Hubdoc receipts and bills.
Convert XLSX spreadsheets (single or multi-sheet) to CSV files you can read and grep. Use whenever you need to process an .xlsx report from Xero, Cryptio, bank exports, or any tool that delivers spreadsheet output.
Create Claude Code slash commands, OpenCode command files, and Pi prompt templates that delegate to the right subagent or skill. Use when creating new commands or refactoring existing ones to follow platform conventions.
| name | describing-prs |
| description | Generate a PR description for the current branch. Writes Markdown to .git/magit/posts/new-pullreq for use with magit-forge. |
| allowed-tools | Bash(~/.agents/skills/describing-prs/scripts/find-merge-base.py:*) |
Generate a well-structured PR description for the current feature branch.
Use this skill when:
Determine the base branch
Run the helper script to find the base branch:
BASE=$(~/.agents/skills/describing-prs/scripts/find-merge-base.py)
The script outputs a branch name (e.g., origin/main) that represents
the base branch for comparison. It handles cases where you branched
from another feature branch, not just main/master.
Options:
--fetch: Fetch latest remote refs before determining base branch--debug: Show how the base branch is determinedStrategy (implemented in the script):
@{upstream} first (the current branch's configured upstream)origin/HEAD (the remote's default branch)origin/main, origin/master, origin/developGather context about the branch
Using the base branch found above:
git branch --show-current
git log --oneline <base-branch>..HEAD
git diff --no-ext-diff <base-branch>..HEAD --stat
git diff --no-ext-diff <base-branch>..HEAD
Analyze the changes
Generate the PR description
Write a Markdown file with:
Write to the output file
Create the directory and write the description:
mkdir -p .git/magit/posts
Write Markdown content to .git/magit/posts/new-pullreq
The generated file should follow this structure:
# <PR Title>
## Summary
<Brief explanation of what this PR accomplishes and why>
## Changes
- <Key change 1>
- <Key change 2>
- ...
## Testing
<How changes were tested, or "N/A" if not applicable>
## Notes
<Any additional context for reviewers, breaking changes, or follow-up work>
myFunction, CONFIG_VALUE, src/utils.ts).git/magit/posts/new-pullreq is used by magit-forge