- When to Use
- Invoke this skill:
- After completing any non-trivial coding task
- Before committing changes
- When preparing PR descriptions
- After think-about-whether-you-are-done confirms completion
- Change Summary Workflow
- Step 1: Gather Change Information
- Collect information about what changed:
- Modified Files
-
- List all files that were changed
- Change Types
-
- Categorize changes (new, modified, deleted, renamed)
- Scope
- Identify affected components/modules
If using git, gather diff summary
- git
- status
- git
- diff
- --stat
- Step 2: Analyze Change Impact
- For each significant change, document:
- What Changed
-
- Specific modification made
- Why It Changed
-
- Reason/motivation for the change
- Impact
- What this affects (functionality, performance, API)
Step 3: Generate Summary
Use this template:
Changes Summary
Overview
[1-2 sentence high-level description of what was accomplished]
Changes Made
New Files
|
File
|
Purpose
|
|
|
|
|
path/to/file.ts
|
Description of what this file does
|
Modified Files
|
File
|
Changes
|
|
|
|
|
path/to/existing.ts
|
What was changed and why
|
Deleted Files
|
File
|
Reason
|
|
|
|
|
path/to/old.ts
|
Why this file was removed
|
Technical Details
**
Key Implementation Decisions
**
:
-
Decision 1 and rationale
-
Decision 2 and rationale
**
Dependencies Added/Removed
**
:
-
Added:
package-name@version
- reason
-
Removed:
old-package
- reason
Breaking Changes
[List any breaking changes or "None"]
Migration Required
[Any steps needed to adopt these changes or "None"]
Verification Checklist
[ ] Unit tests pass
[ ] Integration tests pass
[ ] Documentation updated
[ ] No console errors
[ ] Performance acceptable
Fixes #123
Related to #456
Step 4: Commit Message Suggestion
Generate a conventional commit message:
():