ck:watzup

Summarize current branch changes and commits with file-level impact and risks.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/quanganh208/cookmate --skill ck-watzup-quanganh208
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:watzup
Source: https://github.com/quanganh208/cookmate/tree/main/.opencode/skills/watzup
Command: npx skills add https://github.com/quanganh208/cookmate --skill ck-watzup-quanganh208

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers quickly summarize the current work session by analyzing the latest branch changes and commits, saving time during standups and code reviews.

Core Features & Use Cases

  • Summary of changes: Identify modified, added, and removed files with concise explanations.
  • Quality and risk highlights: Flag potential code-quality issues and risk areas for quick remediation.
  • PR-ready briefing: Generate a concise description suitable for inclusion in a pull request.

Quick Start

Review my current branch and the most recent commits and generate a detailed, readable summary of changes.

Frequently Asked Questions about ck:watzup

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

FAQPage Schema
How do I summarize git commits for a code review?

Summarizing git branch changes involves identifying modified, added, and removed files to generate a structured review. This provides a rationale-backed assessment of file-level impact, code quality, and potential risks for quick remediation.

What is the best way to generate a pull request description from recent commits?

Generating a pull request description from recent commits involves analyzing the latest branch state. It produces a concise, PR-ready briefing that explains the impact of modifications and suggests concrete improvements.

How do I assess code impact and risks on my current git branch?

Assessing code impact and risks on a git branch involves reviewing the latest commits to flag potential code-quality issues. This highlights risk areas and provides a structured, rationale-backed review for quick remediation.

Can I automate a change summary of modified files for my standup?

Automating a change summary of modified files for a standup analyzes the current work session's latest branch changes and commits. It identifies file modifications and generates concise explanations of what was resolved.