create-pr
Create GitHub Pull Requests
Pull request preparation can be slow when commits, files, tests, and issue links must be summarized. This skill reviews repository changes, drafts PR text, pushes the branch, and opens the PR with GitHub CLI.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "create-pr" from https://skillstore.io/skills/crearize-create-pr.md and its manifest at https://skillstore.io/api/skills/crearize-create-pr/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "create-pr". User asks to create a PR for a feature branch that adds profile settings.
Expected outcome:
A PR title, concise summary, categorized changes, test checklist, related issue line, and a GitHub PR URL after approval.
Using "create-pr". User asks for a bug fix PR linked to issue 456.
Expected outcome:
The skill reports branch checks, summarizes the fix, includes test evidence, references issue 456, and creates the PR through GitHub CLI.
Using "create-pr". User requests a documentation-only PR.
Expected outcome:
The skill highlights updated documents, keeps technical sections minimal, and provides a review-ready PR description.
Security Audit
SafeMost static findings are false positives from Markdown fences, inline backticks, and readable Japanese documentation. The confirmed risks are the state-changing git push and gh pr create workflow, plus avoidable shell construction for the generated PR body. No prompt injection, malicious network endpoint, or obfuscated payload evidence was found.
Capability review items (4)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (29)
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/crearize-create-pr/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/crearize-create-pr?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/crearize-create-pr?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/crearize-create-pr/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/crearize-create-pr.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Crearize. (2026). create-pr security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/crearize-create-pr/audits/10BibTeX citation
@techreport{crearize-crearize-create-pr-2026,
author = {Crearize},
title = {create-pr security audit report (audit version 10)},
institution = {Skillstore},
year = {2026},
number = {10},
url = {https://skillstore.io/skills/crearize-create-pr/audits/10},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "create-pr security audit report (audit version 10)"
version: "unspecified"
type: report
authors:
- name: "Crearize"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/crearize-create-pr/audits/10"
identifiers:
- type: other
value: "skillstore:crearize-create-pr:audit:10"
description: "Skillstore immutable audit report identifier"
Compare variants
7 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
sickn33-create-pr
2026-08-21
getsentry-create-pr
2026-08-21
crearize-create-pr
2026-08-21
cloud-officer-create-pr
2026-08-21
davila7-create-pr
2026-08-21
cygnusfear-create-pr
2026-08-21
0tarof-create-pr
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Feature Branch Submission
Prepare a polished PR from a completed feature branch with summary, tests, checklist, and issue closure details.
Maintenance Fix Review
Turn a small fix branch into a review-ready PR with clear scope and changed file categories.
Team Workflow Standardization
Use a consistent PR format across backend, frontend, and documentation changes.
Try These Prompts
Create a GitHub pull request for my current branch. Show me the branch, changed files, generated title, and PR body before pushing.
Create a pull request for this branch against origin/main and link issue #123. Include the test status and a concise summary.
Analyze the commits and changed files, group backend, frontend, and documentation changes, then draft the PR. Ask before running git push.
Prepare a release-ready PR with risk notes, reviewer guidance, checklist status, and screenshots section. Use gh CLI only after I approve the preview.
Best Practices
- Review the generated title and body before approving any push or PR creation.
- Run QA checks and commit all changes before starting the workflow.
- Confirm the base branch, issue number, and test status with the user.
Avoid
- Do not run the workflow from main or another protected branch.
- Do not create a PR while uncommitted changes are present.
- Do not paste unreviewed generated text into a public PR.