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.

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.

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.

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.

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.

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.