pr-description
SkillDev toolsTemplate and rules for writing PR descriptions
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the pr-description skill
What this skill tells your AI
The instructions your AI receives, as published by albinotonnina/echos in .hive/prompts/skills/pr-description/SKILL.md and read by ahel’s review.
Every PR description must contain these sections:
## 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.
Signals
- GitHub stars
- 60
- Forks
- 8
- Last commit
- Jul 2026
Advanced
- Catalog kind
- skill
- Gateway key
pr-description- Source
- github.com/albinotonnina/echos