playbooks

home / skills / duc01226 / easyplatform / watzup

watzup skill

/.claude/skills/watzup

This skill reviews your current branch and recent commits, providing a detailed summary of changes and their impact.

npx playbooks add skill duc01226/easyplatform --skill watzup

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
548 B
---
name: watzup
description: "[Utilities] ⚡ Review recent changes and wrap up the work"
infer: true
---

Review my current branch and the most recent commits.
Provide a detailed summary of all changes, including what was modified, added, or removed.
Analyze the overall impact and quality of the changes.

**IMPORTANT**: **Do not** start implementing.

## IMPORTANT Task Planning Notes

- Always plan and break many small todo tasks
- Always add a final review todo task to review the works done at the end to find any fix or enhancement needed

Overview

This skill inspects the current Git branch and recent commits to produce a concise, actionable review and wrap-up plan. It summarizes what was modified, added, or removed and evaluates the overall impact and quality of the changes. The goal is to help developers finish work cleanly without starting any new implementation steps.

How this skill works

The skill reads the commit history on the current branch and diffs those commits to identify file-level changes, code additions, deletions, and refactors. It generates a detailed summary of changed files, key code areas affected, and potential risks or regressions. It also produces a prioritized list of small todos to finish or clean up the work, and always includes a final review task to verify fixes and enhancements.

When to use it

  • Before merging a feature branch to main or develop to understand scope and risk
  • When closing out a sprint task to ensure all intents are addressed and documented
  • After a series of commits to create an actionable checklist for final polishing
  • When performing a pre-release check to highlight regressions and test needs
  • During code review handoffs to provide reviewers with context and impact analysis

Best practices

  • Do not start implementing changes in this review; use the produced todo list to plan work.
  • Break larger items into many small, testable todos for incremental work and easier review.
  • Include contextual notes for reviewers: rationale, related issues, and dependencies.
  • Prioritize fixes that affect public APIs, security, or critical workflows first.
  • Always add and complete a final review todo to verify fixes, tests, and documentation.

Example use cases

  • Summarize a feature branch with multiple refactors and provide a finishing checklist.
  • Analyze a hotfix branch to ensure no regressions and outline verification steps.
  • Create a wrap-up plan after a large merge to tidy up leftover TODOs and docs.
  • Prepare a pre-release impact report listing files to test and areas needing QA.
  • Hand off recent changes to another developer with a prioritized task list and review step.

FAQ

Will the skill make code changes for me?

No. The skill only inspects commits and produces summaries and todo tasks; it does not implement changes.

How granular are the todo tasks?

Todos are broken into many small, actionable items to simplify implementation, testing, and review.