watzup

Review recent git commits and diffs to summarize changes and assess commit readiness.

7|3|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/brainbrewlabs/brainbrew-devkit --skill watzup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: watzup
Source: https://github.com/brainbrewlabs/brainbrew-devkit/tree/main/.claude/skills/watzup
Command: npx skills add https://github.com/brainbrewlabs/brainbrew-devkit --skill watzup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly review recent repository changes, assess code quality, and produce a concise session summary so developers can decide next steps without manually scanning diffs, commits, and documentation impact.

Core Features & Use Cases

  • Change Discovery: Summarizes files modified, added, and removed and extracts key changes from recent commits.
  • Quality Review: Coordinates with the code-reviewer subagent to flag obvious issues and assess overall code quality.
  • Docs Impact & Recommendations: Uses the docs-manager agent to identify affected documentation, propose updates, and suggest commit messages or next steps.
  • Use Case: After a focused work session or a small PR iteration, run this Skill to get a short session summary, prioritized issues to fix, test recommendations, and suggested commit text.

Quick Start

Ask the watzup skill to review the last 10 commits and produce a concise session summary with recommended next steps.

Frequently Asked Questions about watzup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I summarize recent git changes and assess code quality before committing?

To summarize recent git changes and assess code quality before committing, you can review modified files and recent commits to produce a concise session summary with prioritized issues and suggested commit messages.

What's the best way to review recent commits and identify documentation impact?

The best way to review recent commits and identify documentation impact is to analyze repository diffs and flag affected documentation, proposing necessary updates and next steps for the development session.

Can I generate a commit message suggestion from my recent repository changes?

Yes, you can generate a commit message suggestion from recent repository changes by extracting key modifications from recent commits and assessing overall readiness to produce recommended commit text.

How does a code review session summary work for short development iterations?

A code review session summary for short development iterations works by scanning recent diffs, flagging obvious quality issues, and outputting a concise summary with test recommendations and prioritized fixes.

Do I need access to the git workspace and diffs to review recent code changes?

Yes, you need access to the git workspace and diffs to review recent code changes, as the process requires extracting modified files and recent commits to assess quality and documentation impact.

When should I run a code review and session summary for my git repository?

You should run a code review and session summary after a focused work session or a small pull request iteration to get a short summary, prioritized issues to fix, and recommended next steps without manually scanning diffs.