creating-pull-requests
Create Pull Requests with Clear Summaries
Preparing a pull request can miss branch checks, summary details, or test notes. This skill guides Claude, Codex, or Claude Code through a consistent GitHub PR workflow.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "creating-pull-requests" from https://skillstore.io/skills/1gy-creating-pull-requests.md and its manifest at https://skillstore.io/api/skills/1gy-creating-pull-requests/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 "creating-pull-requests". Create a pull request for the current feature branch.
Expected outcome:
The skill checks branch state, pushes the branch, creates the PR, and returns the PR URL and target branch.
Using "creating-pull-requests". Open a draft PR with a test plan for reviewers.
Expected outcome:
The skill creates a draft PR with summary bullets and a checklist of validation steps.
Using "creating-pull-requests". Create a PR against a release branch and assign it to me.
Expected outcome:
The skill targets the requested branch, applies assignment options, and reports the completed PR details.
Security Audit
SafeStatic findings are false positives caused by Markdown code fences, inline option formatting, and a benign heredoc pattern. The skill documents expected git and GitHub CLI steps for creating pull requests, with no prompt injection or data exfiltration intent found.
Risk Factors
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/1gy-creating-pull-requests/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/1gy-creating-pull-requests?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/1gy-creating-pull-requests?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/1gy-creating-pull-requests/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/1gy-creating-pull-requests.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
1gy. (2026). creating-pull-requests security audit report (audit version 7) [Author version unspecified]. Skillstore. https://skillstore.io/skills/1gy-creating-pull-requests/audits/7BibTeX citation
@techreport{1gy-1gy-creating-pull-requests-2026,
author = {1gy},
title = {creating-pull-requests security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/1gy-creating-pull-requests/audits/7},
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: "creating-pull-requests security audit report (audit version 7)"
version: "unspecified"
type: report
authors:
- name: "1gy"
date-released: "2026-07-04"
url: "https://skillstore.io/skills/1gy-creating-pull-requests/audits/7"
identifiers:
- type: other
value: "skillstore:1gy-creating-pull-requests:audit:7"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prepare a Feature PR
A developer can turn a completed feature branch into a reviewed GitHub pull request.
Standardize Review Notes
A maintainer can require consistent summaries and test plans before team review.
Document Release Changes
A release lead can create a PR that clearly lists changes and validation steps.
Try These Prompts
Use the creating-pull-requests skill to create a pull request for my current branch.
Use the creating-pull-requests skill to create a draft pull request with a clear summary and test plan.
Use the creating-pull-requests skill to create a pull request against the release branch and include test notes.
Use the creating-pull-requests skill to create a PR, assign it to me, add labels, and report the final URL.
Best Practices
- Confirm the main branch name before comparing commits.
- Review the generated title, summary, and test plan before creating the PR.
- Run relevant tests before asking the skill to create the pull request.
Avoid
- Do not run it from a branch with unrelated or uncommitted changes.
- Do not create a PR before confirming the remote repository and target branch.
- Do not leave the test plan empty when reviewers need validation context.