Skills pr-prepare
📦

pr-prepare

Content revision r2 Safe ⚙️ External commands

Prepare Clear Pull Request Descriptions

Writing complete pull request descriptions from branch changes takes time and often misses important context. This skill reviews Git changes and produces a structured title and description.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "pr-prepare" from https://skillstore.io/skills/byronwilliamscpa-pr-prepare.md and its manifest at https://skillstore.io/api/skills/byronwilliamscpa-pr-prepare/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 "pr-prepare". Prepare a pull request for a branch that adds OAuth login and authentication tests.

Expected outcome:

  • Suggested title: feat: add OAuth login
  • Summary: Adds provider login, callback handling, and secure session management.
  • Testing: Authentication tests were added, but execution status requires confirmation.

Using "pr-prepare". Write a pull request description for a fix that prevents duplicate order processing.

Expected outcome:

  • Suggested title: fix: prevent duplicate order processing
  • Impact: Repeated delivery events no longer create duplicate orders.
  • Notes: Confirm retry behavior and database constraints before merge.

Using "pr-prepare". Prepare a maintenance pull request for dependency updates and documentation changes.

Expected outcome:

  • Suggested title: chore: update dependencies and documentation
  • Changes: Updates project dependencies and aligns setup documentation with the current workflow.
  • Testing: Dependency compatibility and installation steps need verification.

Security Audit

Safe
v9 • 7/23/2026 Open versioned report

All 25 static matches are false positives caused by Markdown formatting or fixed Git inspection commands. The commands use no dynamic user input, and push commands appear only as user-facing suggestions.

1
Files scanned
150
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
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.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/byronwilliamscpa-pr-prepare/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/byronwilliamscpa-pr-prepare/security.svg)](https://skillstore.io/skills/byronwilliamscpa-pr-prepare?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/byronwilliamscpa-pr-prepare?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/byronwilliamscpa-pr-prepare/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/byronwilliamscpa-pr-prepare.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

ByronWilliamsCPA. (2026). pr-prepare security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/byronwilliamscpa-pr-prepare/audits/9

BibTeX citation

@techreport{byronwilliamscpa-byronwilliamscpa-pr-prepare-2026, author = {ByronWilliamsCPA}, title = {pr-prepare security audit report (audit version 9)}, institution = {Skillstore}, year = {2026}, number = {9}, url = {https://skillstore.io/skills/byronwilliamscpa-pr-prepare/audits/9}, 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: "pr-prepare security audit report (audit version 9)" version: "unspecified" type: report authors: - name: "ByronWilliamsCPA" date-released: "2026-07-23" url: "https://skillstore.io/skills/byronwilliamscpa-pr-prepare/audits/9" identifiers: - type: other value: "skillstore:byronwilliamscpa-pr-prepare:audit:9" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
70
Community
83
Spec Compliance

What You Can Build

Describe a feature branch

Convert a completed feature branch into a structured title and reviewer-focused pull request description.

Standardize team submissions

Apply consistent summary, impact, testing, and notes sections across pull requests.

Prepare maintenance changes

Summarize dependency, refactoring, performance, or documentation updates before repository review.

Try These Prompts

Prepare my current branch
Prepare a pull request title and description for my current branch against main. Keep test items unchecked unless verified.
Use another base branch
Prepare this branch against develop. Group changes by component and identify any breaking behavior or required follow-up work.
Focus on a bug fix
Prepare a bug-fix pull request. Explain the cause, changed behavior, affected components, regression coverage, and remaining risks.
Build a release-ready description
Analyze the branch and prepare a release-ready pull request. Separate verified tests from pending checks, and flag migrations, security effects, and compatibility risks.

Best Practices

  • Confirm the correct base branch before generating the comparison.
  • State which tests and checks actually ran, and leave unverified items unchecked.
  • Review the generated description for sensitive data, inaccurate claims, and missing reviewer context.

Avoid

  • Do not mark tests as passed without execution evidence.
  • Do not use vague summaries that repeat the pull request title.
  • Do not include credentials, tokens, personal data, or unrelated secrets from the diff.

Frequently Asked Questions

Does this skill create the pull request?
No. It prepares the title and description, then provides optional commands for the user.
Which base branch does it use?
It uses main by default. Specify another base branch when your repository uses a different workflow.
Does it run tests or linting?
No. It includes checklist items, but the user must run and confirm each check.
Can it follow my repository template?
It uses a built-in template. Provide repository-specific sections or requirements in the request.
How does it choose a pull request title?
It maps the change purpose to a conventional prefix such as feat, fix, docs, refactor, test, perf, or chore.
Can it handle large branches?
It can summarize them, but large diffs may require focused prompts or separate descriptions by component.

Developer Details

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

a39a91716eadede5f4cdefd78178fed4e837a128

Maintenance freshness

7/24/2026

Usage

7 downloads · 184 views

File structure

📄 SKILL.md