Generates clear and structured pull request descriptions from code changes. Use when Claude needs to: (1) Create PR descriptions from git diffs or code changes, (2) Summarize what changed and why, (3) Document breaking changes with migration guides, (4) Add technical details and design decisions, (5) Provide testing instructions, (6) Enhance descriptions with security, performance, and architecture notes, (7) Document dependency changes. Takes code changes as input, outputs comprehensive PR description in Markdown.
Install with Tessl CLI
npx tessl i github:ArabelaTso/Skills-4-SE --skill code-change-summarizer79
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Breaking change documentation
Title type prefix
100%
100%
Title length
100%
100%
Summary length
100%
100%
Active voice summary
100%
100%
Changes categorized
0%
0%
Breaking change warning emoji
0%
100%
Breaking change impact
37%
100%
Migration guide with steps
100%
100%
Before/After code examples
100%
100%
Related issue reference
100%
100%
Final checklist
42%
100%
Testing section
50%
100%
Markdown output format
100%
100%
Without context: $0.1282 · 39s · 8 turns · 13 in / 2,274 out tokens
With context: $0.5135 · 1m 41s · 17 turns · 3,595 in / 5,343 out tokens
Dependency and testing documentation
Title type prefix
100%
100%
Title length
0%
0%
Dependencies Added section
100%
100%
Dependencies Updated section
100%
100%
Dependencies Removed section
100%
100%
Testing steps numbered
100%
100%
Unit test count
100%
100%
Integration test count
100%
100%
Coverage percentage
100%
100%
Manual testing checklist
28%
100%
Documentation checklist
0%
100%
Related issue reference
100%
100%
Changes categorized
100%
100%
Without context: $0.1975 · 59s · 12 turns · 19 in / 2,780 out tokens
With context: $0.6020 · 1m 53s · 23 turns · 3,602 in / 5,571 out tokens
Technical details and security/architecture documentation
Title type prefix
100%
100%
Title length
100%
100%
Summary active voice
100%
100%
Summary sentence count
100%
100%
Technical implementation approach
100%
100%
Design decisions documented
100%
100%
Architecture changes noted
100%
100%
Security improvements listed
100%
100%
Security review status
0%
100%
Performance metrics present
100%
100%
Performance optimizations
100%
100%
Related issue reference
100%
85%
Final checklist present
100%
100%
Without context: $0.2037 · 1m 21s · 9 turns · 14 in / 3,850 out tokens
With context: $0.5558 · 2m 1s · 21 turns · 3,631 in / 5,900 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.