Prepares and opens ready-for-review GitHub pull requests from completed branch changes.
npx skills add https://github.com/fx/skills --skill pr-preparer-fx
Please help me install this Agent Skill. Skill: pr-preparer Source: https://github.com/fx/skills/tree/main/skills/pr-preparer Command: npx skills add https://github.com/fx/skills --skill pr-preparer-fx
git diff main and git log to verify atomic commits, conventional commit messages, and semantic branch naming before opening the PR. - Blocking Title and Body Rules: Enforces conventional-commit PR titles (validated against a regex), forbids #N references and wave/phase numbers in titles, and requires a concrete checkbox test plan in the body. - Task Tracking Sync: Loads the project-management skill to mark completed tasks in docs/changes/ or docs/tasks.md, update change document status, and sync docs/index.yml and docs/index.md. - Use Case: After finishing a feature branch, invoke this Skill to validate the branch, generate a compliant PR title and description, create the PR with gh pr create (never as a draft), and hand off to CI monitoring. ## Quick Start Use the pr-preparer skill to review my current branch changes and open a ready-for-review pull request on GitHub.High-intent search queries and answers about installing and using this skill.
Use `gh pr create --title "type(scope): description" --body "..."` after committing all changes. This Skill automates the full process: it audits the branch, enforces a conventional-commit title, writes a concise body with a test plan, and opens the PR ready for review.
A conventional commit title follows `type(scope): description`, such as `feat(auth): add OAuth2 login`, matching the regex `^(feat|fix|docs|refactor|chore|test|perf|build|ci|style|revert)(\(.+\))?!?: .+`. On squash-merge the title becomes the commit subject, so non-conventional titles pollute the history.
On squash-merge the PR title becomes the commit subject, where `#N` auto-links to that PR or issue. Using it for waves, phases, or change-doc numbers wrongly cross-links the commit, and GitHub already appends the real PR number automatically at merge time.
No. All PRs must be created ready for review, never as drafts, because downstream steps like CI monitoring and reviewer adapters run from the moment the PR opens. If the work is not ready, finish it before opening the PR.
The Skill runs `git status --porcelain` first and stops immediately if any uncommitted changes exist. You must commit everything before it proceeds with branch analysis or PR creation.
imvanzenCreates commits on-demand from GitHub and/or GitLab events and webhooks. Fetches metadata for each commit and forwards it to the specified URL.
fxDetect unresolved Copilot and CodeRabbit threads on GitHub pull requests and invoke resolver skills.
sgcarstrendsAutomate detection of security vulnerabilities, performance issues, and code quality defects in code reviews.
sakastudioCreate a GitHub pull request from the current branch using gh pr create.