Skip to content
Back to skills

Pr Description

ASecurity

Template and rules for writing PR descriptions

  • 60 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 12, 2026
ai-agentstesting

Security analysis

A100/100

Scanned September 12, 2026

npx -y skills add albinotonnina/echos --skill pr-description --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pr Description?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Pr Description
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/albinotonnina-pr-description/badge)](https://www.skillsdirectory.com/skills/albinotonnina-pr-description)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: pr-description
description: Template and rules for writing PR descriptions
disable-model-invocation: true
---

Every PR description must contain these sections:

```markdown
## What

[One paragraph: what changed and why. Link the Hive task ID.]

## How

[Technical approach: key decisions made, alternatives considered, trade-offs.]

## Testing

[How was this verified? Which test commands were run? Include output for non-obvious cases.]

## Screenshots / recordings

[For UI changes: before/after screenshots or a screen recording. Delete section if not applicable.]

## Checklist

- [ ] Tests added or updated
- [ ] `npm test` passes locally
- [ ] No new lint errors (`npm run lint`)
- [ ] Breaking changes documented in the PR body
- [ ] Dependent PRs linked in description
```

Keep the "What" section readable by non-engineers — it will end up in the changelog.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…