​
/watzup — Handoff report tự động

Skill mới trong bộ claudekit — /watzup = “What’s up?” Generate handoff report tự động từ Git activity, open worktrees, unfinished plans, roadmap. Useful: end-of-session, chuyển ca, trước standup, fresh worktree. No manual typing.

​
Tổng quan

/watzup đọc:
  • Git branches → PRs open, merged, pending
  • Worktrees → active work, dirty state
  • Plan files (plans/XXX/) → unfinished phases
  • Roadmap (docs/project-roadmap.md) → upcoming work
  • Issue tracker (local issues folder) → urgent items
Output: Priority-ranked handoff report

​
Prefix & flags

​
Workflow

1

Bước 1: Gọi skill

2

Bước 2: Read output

Report includes:
  • Unfinished work (priority ordered)
  • Open branches & PR status
  • Active worktrees
  • Next steps (checkbox format)
  • Risks (if detected)
3

Bước 3: Copy to team

Or configure auto-post (future):
  • Scheduled (daily standup time)
  • On-demand (team request)
4

Bước 4: Act on next steps

Team review report:
  • PR reviews, merges
  • Unblock dependencies
  • Update roadmap if needed

​
Ví dụ thực tế

​
Case 1: End-of-session handoff

Workflow:
  • 5 PM: Developer A calls /watzup
  • Report shows: F06 ready to merge, F07 merge conflict, F08 planning not done
  • Copy output → paste into team channel
  • Developer B picks up: “I’ll rebase F07, then start F08 planning”
  • Smooth handoff, no context loss

​
Case 2: Quick standup summary

Workflow:
  • 9 AM: Team standup
  • Lead calls /watzup --next
  • Output: “Priority: merge F06, fix F07 conflict, start F08”
  • 1-minute standup, everyone aligned

​
Case 3: Monday morning after weekend

Workflow:
  • Monday 9 AM: “What was I working on?”
  • /watzup --worktrees → shows all local branches, dirty state
  • Quickly resume work, don’t lose context

​
Case 4: Fresh checkout, new machine

Workflow:
  • New dev, fresh repo clone
  • /watzup --plans → shows all unfinished work + plans
  • Understand roadmap + dependencies
  • Pick next task

​
So sánh với skill khác

Tóm tắt:
  • /watzup = automated status from code state
  • /daily-standup = manual template (3 questions)
  • /checkpoint = save/resume state
  • /sprint-status = burndown + velocity

​
Common pitfalls

Sai lầm phổ biến:
  • Run /watzup khi chưa commit anything: Dirty worktree → report incomplete. Commit trước
  • Expect /watzup to auto-close issues: It’s reporting only, not modifying. Use it as checklist
  • Ignore merge conflicts in report: If reported as blocker, fix immediately (don’t postpone)
  • Run on empty/new repo: No history → report minimal. Thêm issues/plans trước
  • Assume worktrees auto-discovered: /watzup scan ~/.worktrees/ config. Setup worktree tracking first
  • Multiple machines, forget to push: /watzup reads local only. Push branches trước for team visibility

​
FAQ

A: Report shows:
  • “Plans not found in plans/ folder”
  • Still report: branches, worktrees, roadmap
To include plans: create /plans/XXX-feature-name/plan.md before /watzup
A: Stdout (display), không auto-save:
Copy-paste into Slack/Lark, or future: auto-post to team channel
A: No. /watzup reads local machine only:
  • Machine A: /watzup → shows A’s worktrees
  • Machine B: /watzup → shows B’s worktrees
To sync: config worktree registry in Git (future enhancement)
A: Currently: fixed priority (blocker > pending > in-progress)Future: /watzup --priority <custom-config> to override For now: report as-is, team reorder if needed
A: Real-time:
  • Runs git branch -v → current
  • Reads plan files → current
  • Checks remote refs → current (via git fetch)
Age: < 30 seconds
A: Minimum: Git only
  • Read branches, commits, worktrees
  • Local plan files
Optional: GitHub CLI for:
  • PR status (author, approval count)
  • Issue status (open/closed)
Works without gh, but limited detail

​
Integration with standups

Workflow:

​
Xem thêm