| name | prepare-pr |
| description | Prepares a clean pull request from agent-made changes. Creates a new branch, stages and commits changes with a conventional-commit message, and opens a PR with a structured description. Use this skill when you need to submit work as a pull request rather than committing directly.
|
Prepare Pull Request
When to use
Use this skill after making file changes that should be submitted as a pull
request for review, rather than pushed directly to the default branch.
Instructions
-
Create a branch from the current HEAD:
BRANCH="agent/$(date +%Y%m%d-%H%M%S)-${MISSION_SLUG}"
git checkout -b "${BRANCH}"
-
Stage changes selectively — only include files that were intentionally
modified by the mission. Do NOT stage unrelated files:
git add <changed-files>
-
Commit using Conventional Commits format:
<type>(<scope>): <short summary>
<body — what changed and why>
Types: fix, feat, docs, refactor, chore, ci, test.
-
Push the branch:
git push origin "${BRANCH}"
-
Open a Pull Request using gh pr create. Always use the project's PR template at .github/pull_request_template.md:
gh pr create \
--title "<type>(<scope>): <summary>" \
--body-file .github/pull_request_template.md \
--base main
-
Update PR Body. After creating the PR with the template, update the description using gh pr edit to include specific details about your changes, keeping the template structure intact.
Rules
- Never force-push.
- Never commit secrets, tokens, or credentials.
- Keep commits atomic — one logical change per commit.
- If there are no changes to commit, exit gracefully with a message.
