Pr

Skill steph-dove/klaussy-agents/src/klaussy/templates/skills/pr

A multi-agent context, rules, and hooks boilerplate generator. With a single command, it scaffolds conventions, namespaced skills, stack-appropriate settings, and interactive guardrails for seven major AI coding environments, matching each agent's native file formats and capability profiles.

Install

npx -y skills add steph-dove/klaussy-agents --skill pr

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

11 stars11 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

Use when the user wants a PR description generated for the current branch. Reads commit history, file changes, and CLAUDE.md, then writes a Summary / Changes / Test Plan / Notes block to pr-description.md.

SKILL.md

2.5 KB, as published. Nobody here has run it

Branch

git branch --show-current

Commit history vs base

git log {{BASE_BRANCH}}..HEAD --oneline

Files changed

git diff {{BASE_BRANCH}}...HEAD --stat

Instructions

Generate a PR description for the changes summarized above. Extract any ticket reference (e.g. FEAT-1234) from the branch name. Read CLAUDE.md for project conventions and any PR template rules. For key changed files, read them to understand the full context — do not paraphrase from the diff alone.

Output format:

## Summary

<!-- 1-3 sentences explaining what this PR does and why -->

## Changes

<!-- Bullet list of key changes, grouped logically -->

## Test Plan

<!-- How the changes were tested -->
- [ ] Tests pass locally
- [ ] Manually verified

## Notes

<!-- Anything reviewers should pay attention to, migration steps, feature flags, etc. -->

Rules:

Write for a reviewer who has 30 seconds. Lead with what changed and why it matters; surface the one thing they must look at. The Summary should orient them before they open a single file.
Don't echo the diff. The reviewer can read the diff. Summarize intent and group related changes — do not narrate every edit line by line.
Describe the current end state, not a changelog. Write what the PR is, not a chronological story of how you got there ("first I tried X, then changed to Y"). If you revised an approach mid-branch, describe only the final shape.
Be specific — reference actual file names, functions, and components.
Focus on the "why" not just the "what".
If the branch name has a ticket reference, include it in the summary.
Keep it concise. No filler.
If there are database changes, call them out explicitly.
If there are new dependencies, mention them.

Write the output to pr-description.md in the repo root.

When NOT to use

The user wants to actually open a PR (gh pr create) — this skill only writes the description text into a file.
The branch has no commits ahead of {{BASE_BRANCH}} — there's nothing to describe; tell the user instead.
The user wants a release-notes-style summary spanning multiple PRs — different shape; don't try to fit it in this template.