# Ghpr > GitHub Pull Request creation workflow for OSS contributions. Creates well-structured PRs with issue references, conventional prefixes, and proper descriptions. Use when the user wants to create a PR, send changes upstream, or submit a contribution. Use when this capability is needed. - Skill: `tomevault-io/ghpr` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/ghpr` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/ghpr/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/ghpr --- # GitHub Pull Request Workflow Create a Pull Request for the current branch. ## Title - Concise English title, one line - Apply the same prefix convention as commit messages (e.g., feat:, fix:, docs:) ## Description - Include a summary of changes, motivation or context, and how it was tested - Reference related issues with `Fixes #N` or `Closes #N` when applicable - If the repository has a PR template (`.github/PULL_REQUEST_TEMPLATE.md` or `.github/PULL_REQUEST_TEMPLATE/`), follow its structure - If `CONTRIBUTING.md` or `DEVELOPMENT.md` exists, review them and ensure the PR follows the project's conventions ## Workflow 1. Check whether the branch has been pushed to the remote - If not, prompt the user to push — never push on your own 2. Check for a PR template and use it if present 3. Review `CONTRIBUTING.md` and `DEVELOPMENT.md` if they exist 4. Draft the title and description, then **show the proposal to the user for confirmation** 5. After approval, run `gh pr create --title $TITLE --body $BODY` --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/peacock0803sz) — claim your Tome and manage your conversions.