Agent skill · software engineering · google-gemini
pr-creator
Use this skill when asked to create a pull request (PR). It ensures all PRs follow the repository's established templates and standards.
Why this skill is useful
Adds a detailed workflow for creating pull requests that ensures adherence to repository standards and includes specific commands and checks.
What it needs
Requires gh installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 106,400 stars on the source repository.
What this skill does
Pull Request Creator This skill guides the creation of high-quality Pull Requests that adhere to the repository's standards. Workflow Follow these steps to create a Pull Request: 1. Branch Management: CRITICAL: Ensure you are NOT working on the main branch. Run git branch --show-current. If the current branch is main, you MUST create and switch to a new descriptive branch: 2. Commit Changes: Verify that all intended changes are committed. Run git status to check for unstaged or uncommitted changes. If there are uncommitted changes, stage and commit them with a descriptive message before proceeding. NEVER commit directly to main. 3. Locate Template: Search for a pull request template in the repository. Check .github/pullrequesttemplate.md Check .github/PULLREQUESTTEMPLATE.md If multiple templates exist (e.g., in .github/PULLREQUESTTEMPLATE/), ask the user which one to use or select the most appropriate one based on the context (e.g., bugfix.md vs feature.md). 4. Read Template: Read the content of the identified template file. 5. Draft Description: Create a PR description that strictly follows the template's structure. Headings: Keep all headings from the template. Checklists: Review each item. Mark with [x] if completed. If an item is not applicable, leave it unchecked or mark as [ ] (depending on the template's instructions) or remove it if the template allows flexibility (but prefer keeping it unchecked for transparency). Content: Fill in the sections with clear, concise summaries of your changes. Related Issues: Link any issues fixed or related to this PR (e.g., "Fixes #123"). 6. Preflight Check: Before creating the PR, run the workspace preflight script to ensure all build, lint, and test checks pass. If any checks fail, address the issues before proceeding to create the PR. 7. Push Branch: Push the current branch to the remote repository. CRITICAL SAFETY RAIL: Double-check your branch name before pushing. NEVER push if the current branch is main. 8. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google-gemini/pr-creator