agentsclimarketplace

Generate pr description

Skill emaraschio/cursor-commands/plugin/.cursor/skill-contracts/generate-pr-description

Production-grade Cursor slash commands with paired skill contracts, behavioral evals, and ship-gate CI. Install as a user plugin.

Install
npx -y skills add emaraschio/cursor-commands --skill generate-pr-description

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generate PR title and description from branch diff

SKILL.md

1.5 KB, as published. Nobody here has run it

Overview

Create a comprehensive pull request description based on the changes in this branch and format it as proper markdown for use in a GitHub PR description.

Steps

  1. Summary
    • Provide a clear, concise summary of what this PR accomplishes
  2. Changes Made
    • List the key changes made in this PR
    • Include both code and non-code changes
    • Highlight any breaking changes
  3. Testing
    • Describe how the changes were tested
    • Include any new test cases added
    • Note any manual testing performed
  4. Related Issues
    • Link to any related issues or tickets
    • Use closing keywords if this PR resolves issues
  5. Additional Notes
    • Any deployment considerations
    • Follow-up work required
    • Notes for reviewers

Generate PR Description Checklist

  • Provided clear, concise summary of what this PR accomplishes
  • Listed all key changes made in this PR
  • Highlighted any breaking changes
  • Described how the changes were tested
  • Included any new test cases added
  • Noted any manual testing performed
  • Linked to any related issues or tickets
  • Included any deployment considerations
  • Noted any follow-up work required
  • Formatted as proper markdown for GitHub PR

Guardrails

  • Always include a test plan describing how the changes were verified.
  • Use Conventional Commits style for the PR title when appropriate.

Gives 0 of the 12 instructions most pr commit review skills give

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-06

  • use conventional commits formatin 123 of 888, across 110 files
  • keep subject line under 72 charactersin 60 of 888, across 46 files
  • delete branches after mergein 50 of 888, across 37 files
  • use imperative mood in subject linein 50 of 888, across 41 files
  • use imperative mood in commit messagesin 45 of 888
  • generate a conventional commit messagein 42 of 888
  • make atomic commitsin 37 of 888, across 25 files
  • run tests before committingin 36 of 888, across 24 files
  • run project test suite to verify clean baselinein 35 of 888, across 7 files
  • run detected project setup commandsin 34 of 888, across 6 files
  • wrap commit body at 72 charactersin 32 of 888, across 25 files
  • split unrelated changes into separate commitsin 32 of 888, across 27 files

Said here and by no other author read

  • provide a clear summary of PR accomplishments
  • list all key code and non-code changes
  • include any new test cases added
  • note any manual testing performed
  • link related issues using closing keywords
  • include any deployment considerations

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.