AgentStack
SKILL verified MIT Self-run

Pr Description

skill-davila7-claude-with-skills-pr-description · by davila7

Write a pull request description with summary, motivation, and test plan. Use when creating a PR, asked for a PR description, or preparing to submit a pull request.

No reviews yet
0 installs
17 views
0.0% view→install

Install

$ agentstack add skill-davila7-claude-with-skills-pr-description

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Pr Description? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Instructions

  1. List the commits on this branch:

`` git log --oneline main..HEAD ``

If main does not exist, try master:

`` git log --oneline master..HEAD ``

  1. Get a summary of changed files:

`` git diff main...HEAD --stat ``

(Use master...HEAD if main does not exist.)

  1. Write a PR description using the following structure. Output only the description, with no surrounding explanation.

Summary

  • What changed, as a bullet list. One bullet per logical change. Focus on the user-visible or caller-visible effect, not the implementation detail.

Motivation

A short paragraph (two to four sentences) explaining the problem being solved. Why does this PR need to exist? What was wrong or missing before?

Test plan

A checklist of specific steps a reviewer can follow to verify the change works:

  • [ ] Step one
  • [ ] Step two
  • [ ] Edge case or error scenario to check

Notes

Anything a reviewer should know that is not obvious from the diff: migrations that need to run, environment variables that need to be set, follow-up work that is intentionally deferred, known limitations.

If there are no reviewer notes, omit this section entirely.


Keep the description factual and concise. Do not pad with filler phrases. If the PR is straightforward, the description should be short.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.