justin/pm-claude-skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Quality-improve 10 v7.0.0-era engineering skills

Browse Source 
Applies three consistent fixes across the v7.0.0 batch:
- Rename `## Output Structure` → `## Output Format` for consistency
- Wrap output template in `---` document separators (code-review-checklist,
  debugging-log-analyser needed full structural upgrade; remaining 8 already
  had the wrapper)
- Remove `## Example Trigger Phrases` section from all 10 skills

Skills updated: code-review-checklist, debugging-log-analyser,
changelog-generator, pr-description-writer, system-design-interview,
test-strategy-doc, runbook-writer, incident-postmortem, api-docs-writer,
architecture-decision-record

Both `skills/` and `plugins/pm-engineering/skills/` copies synced.

https://claude.ai/code/session_01C3HwChrccJd145vJ6Z7ajF
This commit is contained in:
mohitagw15856
2026-05-20 07:36:10 +00:00
committed by Claude
parent bf65c16222
commit e366a77cf0
20 changed files with 60 additions and 180 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/pr-description-writer/SKILL.md
+2 -9
View File
@@ -1,6 +1,6 @@
---
name: pr-description-writer
description: "Write a clear, structured pull request description from a git diff, branch summary, or commit list. Use when asked to write a PR description, draft a pull request, or document code changes. Produces a description with summary, motivation, changes made, testing steps, and reviewer guidance. Optimised for Opus 4.7 and newer models."
description: "Write a clear, structured pull request description from a git diff, branch summary, or commit list. Use when asked to write a PR description, draft a pull request, or document code changes. Produces a description with summary, motivation, changes made, testing steps, and reviewer guidance."
---
# PR Description Writer Skill
@@ -16,7 +16,7 @@ Ask for these if not provided:
- **Risk level** (low / medium / high — affects how much reviewer guidance to include)
- **PR type** (feature / bug fix / refactor / dependency upgrade / config change / hotfix)
## Output Structure
## Output Format
### Title
A clear, imperative-mood title under 72 characters:
@@ -78,10 +78,3 @@ Flag anything that warrants extra attention:
- [ ] Changes list describes logical changes (not file-by-file changes)
- [ ] Testing steps are reproducible by someone unfamiliar with the code
- [ ] Risk-appropriate reviewer guidance is included
## Example Trigger Phrases
- "Write a PR description for these changes" + [paste diff or description]
- "Draft a pull request for [feature]"
- "I need a PR description — here's what I changed"
- "Summarise these commits into a PR description"
- "Write the PR body for this branch"