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
plugins/pm-engineering/skills/code-review-checklist/SKILL.md
+8 -10
View File
@@ -1,6 +1,6 @@
---
name: code-review-checklist
description: "Generate a tailored code review checklist for any pull request based on the language, type of change, and risk level. Use when asked to review code, check a PR, review a pull request, or generate a code review checklist. Produces a focused checklist with language-specific checks, risk-level-appropriate depth, and a clear approve/request-changes recommendation. Optimised for Opus 4.7 and newer models."
description: "Generate a tailored code review checklist for any pull request based on the language, type of change, and risk level. Use when asked to review code, check a PR, review a pull request, or generate a code review checklist. Produces a focused checklist with language-specific checks, risk-level-appropriate depth, and a clear approve/request-changes recommendation."
---
# Code Review Checklist Skill
@@ -16,10 +16,12 @@ Ask the user for these if not provided:
- **PR description** (paste the description or link to the PR)
- **Author context** (new starter / experienced / external contributor)
## Output Structure
## Output Format
---
# Code Review: [PR Title or Reference]
### 1. Review Summary
**PR:** [Title or reference]
**Scope assessment:** [Small / Medium / Large / Too large — should be split]
**Recommended review depth:** [Skim / Standard / Deep dive]
**Estimated review time:** [Minutes]
@@ -94,14 +96,10 @@ Language-specific correctness checks — choose based on the language stated:
### 7. Common Pitfalls for This Change Type
Based on the change type and language, flag 2-3 things reviewers typically miss for this combination.
---
## Quality Checks
- [ ] Checklist is tailored to the stated language (not generic)
- [ ] Change-type-specific section is included
- [ ] Risk-appropriate depth matches stated risk level
- [ ] Decision framework is explicit
## Example Trigger Phrases
- "Generate a code review checklist for [PR description]"
- "What should I check in this pull request?"
- "Give me a code review checklist for a [language] [change type]"
- "Review checklist for a high-risk PR in [language]"