code-change-summarizer
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
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It uses proper third-person voice, provides comprehensive specific actions, includes natural trigger terms developers would use, and clearly delineates both what the skill does and when to use it. The numbered list format makes the use cases scannable and the input/output specification adds helpful context.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create PR descriptions from git diffs', 'Summarize what changed and why', 'Document breaking changes with migration guides', 'Add technical details and design decisions', 'Provide testing instructions', 'Enhance descriptions with security, performance, and architecture notes', 'Document dependency changes'. | 3 / 3 |
Completeness | Clearly answers both what ('Generates clear and structured pull request descriptions') and when ('Use when Claude needs to:' followed by 7 explicit trigger scenarios). Also specifies input/output format. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'pull request', 'PR descriptions', 'git diffs', 'code changes', 'breaking changes', 'migration guides', 'testing instructions', 'dependency changes'. Good coverage of terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on PR descriptions with distinct triggers like 'PR descriptions', 'git diffs', 'migration guides'. Unlikely to conflict with general documentation or commit message skills due to specific PR focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, concrete guidance with excellent examples and templates for PR description generation. However, it is severely over-engineered for its purpose—Claude already knows how to write PR descriptions, so this skill should focus only on project-specific conventions or preferences. The content would benefit from aggressive trimming (80%+ reduction) and splitting detailed templates into reference files.
Suggestions
Reduce content by 80%+ by removing explanations of concepts Claude already knows (what PR types are, what breaking changes are, basic markdown formatting) and keeping only project-specific conventions or unique patterns
Move the extensive templates, common scenarios, and troubleshooting sections to separate reference files (e.g., pr-templates.md, pr-examples.md) and reference them from a concise main skill
Add explicit validation steps such as 'Verify the summary answers: what changed, why it changed, and who is affected' rather than vague 'review for clarity' instructions
Consolidate the redundant examples—showing the same OAuth2 example across multiple sections adds no value and wastes tokens
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~500+ lines with extensive repetition. The skill explains obvious concepts (what a PR is, what types of changes exist), provides redundant examples showing the same patterns multiple times, and includes lengthy templates that could be referenced externally. Claude already knows how to write PR descriptions. | 1 / 3 |
Actionability | Provides fully concrete, copy-paste ready examples throughout. Every section includes specific markdown templates, exact formatting patterns, and complete example outputs that Claude can directly use or adapt. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced (1-11), but lacks validation checkpoints. No feedback loops for verifying the PR description quality, no explicit 'review and iterate' validation steps, and the 'Review and Refine' section at step 11 is vague rather than providing concrete validation criteria. | 2 / 3 |
Progressive Disclosure | References one external file (pr-templates.md) appropriately, but the main content is a monolithic wall of text. The extensive templates, common scenarios, and troubleshooting sections should be split into separate reference files rather than inline in the main skill. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (684 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
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.