create-pr
Create Sentry-Style Pull Requests
Writing clear pull requests takes context and review discipline. This skill guides Claude, Codex, and Claude Code through Sentry-style PR preparation.
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/getsentry-create-pr.md and its manifest at https://skillstore.io/api/skills/getsentry-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". Prepare a PR for a bug fix branch.
Expected outcome:
The skill produces a concise bug fix title, a short explanation of the failure, reviewer context, and an issue reference.
Using "create-pr". Create a PR for a refactor with no behavior change.
Expected outcome:
The skill explains what moved, why the refactor helps future work, and which files deserve careful review.
Using "create-pr". Add reviewers after opening the PR.
Expected outcome:
The skill identifies the requested reviewers or team and updates the existing pull request through GitHub CLI.
Security Audit
SafeThe static findings are false positives caused by Markdown backticks, fenced examples, and expected Git or GitHub CLI instructions. No prompt injection, data exfiltration intent, hidden network behavior, or malicious command pattern was found in SKILL.md.
Risk Factors
⚙️ External commands (29)
🌐 Network access (2)
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/getsentry-create-pr/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/getsentry-create-pr?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/getsentry-create-pr?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/getsentry-create-pr/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/getsentry-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
getsentry. (2026). create-pr security audit report (audit version 7) [Author version unspecified]. Skillstore. https://skillstore.io/skills/getsentry-create-pr/audits/7BibTeX citation
@techreport{getsentry-getsentry-create-pr-2026,
author = {getsentry},
title = {create-pr security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/getsentry-create-pr/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: "create-pr security audit report (audit version 7)"
version: "unspecified"
type: report
authors:
- name: "getsentry"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/getsentry-create-pr/audits/7"
identifiers:
- type: other
value: "skillstore:getsentry-create-pr:audit:7"
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
Open a Feature Pull Request
Prepare a focused feature PR with a clear title, motivation, and reviewer context.
Standardize Team Review Requests
Apply consistent Sentry PR conventions before asking teammates for review.
Prepare Maintenance Changes
Explain refactors, bug fixes, and issue references without adding unrelated test sections.
Try These Prompts
Create a pull request for my current branch using the Sentry style. Review the branch state, summarize the change, and draft the PR body.
Review my current branch and rewrite the pull request description to explain the motivation, reviewer context, and issue references clearly.
Analyze the commits and diff on this branch, identify the correct PR title, create the PR with GitHub CLI, and report the URL.
Create a Sentry-style PR for this branch, call out risky areas for reviewers, suggest one to three reviewers if ownership is clear, and avoid test-plan sections.
Best Practices
- Run it after all intended changes are committed to the branch.
- Review the generated title and description before approving GitHub CLI commands.
- Provide ticket links and reviewer names when the branch context does not show them.
Avoid
- Do not use it to bundle unrelated changes into one pull request.
- Do not approve PR creation before checking the branch diff and destination branch.
- Do not expect it to replace tests, CI checks, or human code review.