59 lines
1.5 KiB
Markdown
59 lines
1.5 KiB
Markdown
---
|
|
name: ck-watzup
|
|
description: Review recent git changes and wrap up a work session. Use for end-of-session summaries, reviewing what was modified, analyzing commit quality, and getting an impact assessment of recent work.
|
|
---
|
|
|
|
# Watzup — Review Recent Changes
|
|
|
|
Reviews the current branch and recent commits, then provides a summary of changes and impact.
|
|
|
|
## When to Use
|
|
|
|
- End of a work session — "what did I do?"
|
|
- Before creating a PR — verifying all changes are intentional
|
|
- Handing off work to another developer
|
|
- Quick audit of recent modifications
|
|
|
|
## Don't Use When
|
|
|
|
- Need a formal code review with quality feedback (use `ck-code-review`)
|
|
- Need to document changes in journals (use `ck-journal`)
|
|
|
|
## Execution
|
|
|
|
Review the current branch and most recent commits:
|
|
|
|
1. Run `git log` to see recent commit history on current branch
|
|
2. Run `git diff` to see staged and unstaged changes
|
|
3. Run `git status` to see working tree state
|
|
4. Analyze all changes: what was modified, added, or removed
|
|
5. Assess overall impact and quality
|
|
|
|
## Report Format
|
|
|
|
```markdown
|
|
## Recent Changes Summary
|
|
|
|
### Branch
|
|
[current branch name]
|
|
|
|
### Commits Reviewed
|
|
- [hash] [message] — [brief impact]
|
|
|
|
### What Changed
|
|
- **Modified:** [files and what changed]
|
|
- **Added:** [new files]
|
|
- **Removed:** [deleted files]
|
|
|
|
### Impact Assessment
|
|
[Overall quality and impact of changes]
|
|
|
|
### Notes
|
|
[Anything notable — potential issues, follow-up needed]
|
|
```
|
|
|
|
## Important Rules
|
|
|
|
- Do NOT start implementing anything
|
|
- Analysis only — observe and report
|