Skip to content
Back to skills

Git Pull Request

ASecurity

Use when creating a pull request.

  • 666 stars
  • 0 votes
  • 1 copy
  • 7 views
  • Added February 8, 2026
documentationgitapidatabasedocumentation

Works with

  • api
  • mcp

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill git-pull-request --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Git Pull Request?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Git Pull Request
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-git-pull-request/badge)](https://www.skillsdirectory.com/skills/majiayu000-git-pull-request)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: git-pull-request
description: Use when creating a pull request.
---

# Creating Pull Requests

## Process

1. **Analyze changes:** Call the `fetch_feature_branch` tool to get the current branch's changes. If there are no changes, stop.

2. **Check for Linear issue:** Run `./scripts/extract-issue-from-current-branch.sh` to check if the current branch has a Linear issue ID. If it outputs an issue ID, fetch the Linear issue using the Linear MCP.

3. **Create PR title:** Write a clear, descriptive title that explains what the PR accomplishes. Often this will be a slightly reworked version of the Linear issue title. If there's a Linear issue, prepend the title with the issue ID in square brackets.

   Examples:
   - Add user profile management system
   - Update API documentation with examples
   - [IAM-12] Resolve authentication timeout issues
   - [AI-345] Simplify database connection logic

4. **Create PR description:** Write a concise description focused on essential information. Keep it brief and focused.
   - Check for a PR template at `.github/pull_request_template.md`
     - If it exists, use it:
       - If the PR contains a checklist, review each item and determine completion. Ask user if unsure. Remove the checklist section when done.
       - Remove merging instructions or generic template text
       - Keep screenshots/demo sections but leave them empty
     - If no template exists, create a simple description with Summary and Changes sections:
       - **Summary:** Short paragraph explaining what changed and why
       - **Changes:** Bulleted list of key modifications
   - For simple changes, use a single paragraph summary only
   - Focus on what changed and why, not implementation details
   - Use backticks for code terms, file names, and technical references

5. **Present for review:** Show the proposed PR title and body to the user. Display them clearly formatted and ask if they'd like to proceed or make changes.

6. **Create PR:** After user approval:
   - Push commits: `git push`
   - Create PR: `gh pr create --web --title "<title>" --body "<description>"`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.