GitHub Pull Requests

Create a GitHub pull request with conventional commit title

majiayu000/claude-skill-registry·0installs663starsSecurity

SKILL.md

Full skill instructions

GitHub Pull Requests Skill

You are helping the user create a GitHub pull request for the current branch.

Steps

Get the current branch name (base branch is always main):
```
git branch --show-current
```
Ensure main is merged into the branch (no merge conflicts):
```
git fetch origin main
git merge origin/main --no-edit
```
- If merge conflicts occur, stop and help the user resolve them before proceeding
- If the merge introduces new commits, push the updated branch

Analyze the changes:

git log origin/main..HEAD --oneline
git diff origin/main..HEAD --stat

Read commit messages for context:

git log origin/main..HEAD --format="%B---"

Generate the PR:
- Title: Use conventional commits format (e.g., feat: add user authentication, fix: resolve null pointer in parser)
- Body: Fill out the template below concisely

PR Template

## Description
(1-2 sentences on what this PR does)

## Reason
(1-2 sentences on why this change was needed)

Output

Run this command with the generated title and body. Use a heredoc for the body to handle newlines:

gh pr create --web --title "feat: example title" --body "$(cat <<'EOF'
## Description
Brief description here.

## Reason
Why this was done.
EOF
)"

Guidelines

Keep title under 72 characters
Use conventional commit prefixes: feat, fix, refactor, docs, chore, test, perf
Be concise - no fluff or excessive detail
If the branch name contains a ticket ID (e.g., COP-123), DO NOT include it in the title
Only create ONE pull request

Install skill

Copy and run in your terminal

npx -y skills add https://github.com/majiayu000/claude-skill-registry --skill gh-pull-requests

View on GitHub

skills/data/gh-pull-requests/SKILL.md

More Security skills

View all

Security

supabase

Handles the full Supabase workflow from schema changes to deployment, with built-in security guardrails that catch common traps like RLS...

2.7K 308.9K

View

Security

neon-postgres

Comprehensive guides and best practices for Neon Serverless Postgres, covering setup, connection methods, authentication, and platform APIs.

98 216.2K

View

Security

firebase-auth-basics

Guide for setting up and using Firebase Authentication. Use this skill when the user's app requires user sign-in, user management, or secure data access using auth rules.

462 163.8K

View

Security

firebase-security-rules-auditor

A skill to evaluate how secure Firestore security rules are. Use this when Firestore security rules are updated to ensure that the generated rules are extremely secure and robust.

462 127.7K

View

Security

firebase-ai-logic-basics

Official skill for integrating Firebase AI Logic (Gemini API) into web applications. Covers setup, multimodal inference, structured output, and security.

462 125.1K

View

Security

better-auth-best-practices

Complete Better Auth server and client setup with database adapters, session management, plugins, and security configuration.

222 118.2K

View

Security

Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".

31.9K 116.1K

View

Security

cloudflare

Complete Cloudflare platform integration with decision trees for compute, storage, AI, networking, security, and infrastructure-as-code.

3K 110.7K

View

Security

azure-compliance

Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.

253 103K

View