github-pull-request

Sanitize commit messages and diffs before creating GitHub pull requests.

Updated Feb 17, 2026

Search Tags:#automation #security #github #sanitization #pr #pull

Ready to run

npx skills add https://github.com/prulloac/git-blame-vsc --skill github-pull-request-prulloac

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-pull-request
Source: https://github.com/prulloac/git-blame-vsc/tree/main/.agents/skills/github-pull-request
Command: npx skills add https://github.com/prulloac/git-blame-vsc --skill github-pull-request-prulloac

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, git, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Streamlines and safeguards the GitHub pull request process by sanitizing input data, enforcing templates, and requiring explicit human approval before PR creation.

Core Features & Use Cases

Secure PR generation: sanitize commit messages and diffs prior to drafting PR content.
Template-driven bodies: auto-fill PR descriptions from repo templates and commit context.
Red-flag awareness: detect injection patterns and prompt for review when suspicious content is present.
Flexible tooling: supports GitHub MCP servers, GitHub CLI (gh), and REST API integrations.

Quick Start

Provide a PR title and body template for the target repository, and let the skill sanitize inputs and prompt you for approval before creating the PR.

Frequently Asked Questions about github-pull-request

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I sanitize commit messages and diffs before creating a GitHub pull request?▼

To sanitize commit messages and diffs before creating a GitHub pull request, this skill automatically cleans input data and enforces PR templates. It extracts structured data, detects red-flag injection patterns, and requires explicit human approval before submitting the sanitized PR.

How does red-flag detection work for automated GitHub PR creation?▼

Red-flag detection for automated GitHub PR creation works by analyzing sanitized commit messages and diffs for suspicious injection patterns. When red flags are detected, the workflow pauses and prompts for explicit human review and approval before proceeding with PR creation.

Can I use the GitHub CLI to enforce pull request templates and require approval?▼

Yes, you can use the GitHub CLI to enforce pull request templates and require approval. This skill supports flexible tooling including GitHub MCP servers, gh CLI, and REST API integrations to auto-fill PR descriptions from repo templates and prompt for review.

Do I need jq and git installed to automate secure GitHub pull requests?▼

Yes, you need jq and git installed to automate secure GitHub pull requests. These dependencies are required by the skill to extract structured data from repository changes and process commit context prior to sanitizing inputs and generating the PR body.

What is the best way to automate GitHub PRs while preventing prompt injection in diffs?▼

The best way to automate GitHub PRs while preventing prompt injection in diffs is to apply input sanitization before drafting PR content. This skill cleans commit data, enforces structured templates, and uses red-flag detection to require human approval when suspicious content is identified.

When should I require human approval for an automated GitHub pull request?▼

You should require human approval for an automated GitHub pull request whenever red-flag detection identifies suspicious injection patterns in the sanitized diffs or commit messages. This safeguard prevents malicious content from being automatically submitted via the GitHub API.