ag-watzup
Use when you need a read-only handoff summary of current branch state, local/remote refs, worktrees, active project plans, selected-plan hints, and suggested next checks.
- License 许可
- MIT
- 最近更新
- 2026-08-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- ag-watzup
- layer
- helper
- description
- Use when you need a read-only handoff summary of current branch state, local/remote refs, worktrees, active project plans, selected-plan hints, and suggested next checks.
- trigger_keywords
- watzup
02 资源文件 3
- 参考文档references/watzup-workflow.md2.9 KB
- 脚本scripts/watzup-scan.cjs26.0 KB
- 脚本scripts/watzup-scan.test.cjs9.2 KB
03 SKILL.md 正文
Watzup
When to Apply
Use this skill when working with ag-watzup workflows, tasks, or system specifications.
How to Use
Refer to the workflow instructions and command references detailed below. Summarize the current repo state for handoff and resume work.
This is a helper skill only.
- Do use it for read-only branch, worktree, and active-plan summaries.
- Do use it to surface likely selected-plan context when it can be proven or safely hinted.
- Do not use it to choose a plan authoritatively.
- Do not use it to approve execution, resume execution, or mutate repo/process state.
Core Contract
watzup is advisory.
- Evidence comes from git, worktree metadata, and
process/*plan inventory. - Selected-plan awareness is a hint, not a command.
- Next-step recommendations are suggestions, not workflow gates.
If a user needs execution, the repo still requires explicit plan selection and ENTER EXECUTE MODE.
Invocation
Run the local scanner:
node .claude/skills/watzup/scripts/watzup-scan.cjs --json
Useful flags:
node .claude/skills/watzup/scripts/watzup-scan.cjs
node .claude/skills/watzup/scripts/watzup-scan.cjs --json --max-branches 8 --plan-limit 6
node .claude/skills/watzup/scripts/watzup-scan.cjs --selected-plan process/general-plans/active/example_PLAN_27-05-26.md
node .claude/skills/watzup/scripts/watzup-scan.cjs --since "14 days ago"
node .claude/skills/watzup/scripts/watzup-scan.cjs --fetch
Input Sources
The scanner reads from:
git status --short --branchgit worktree list --porcelain- local and remote branch refs plus sampled recent commits
process/general-plans/active/process/features/*/active/- optional session-state hints if a local session id is present
It does not scan upstream plans/**, and it never treats a selected-plan hint as execute authority.
Output Shape
The default output is a human-readable report with these sections:
- Current State
- Recent Work
- In-Flight Plans
- Next Steps
- Warnings
--json returns the same information as structured data.
If the scanner fails, say that explicitly and fall back to the minimal read-only commands:
git status --short --branch
git worktree list --porcelain
git for-each-ref --format='%(refname:short) %(committerdate:iso8601) %(objectname:short) %(subject)' refs/heads refs/remotes
find process/general-plans/active process/features -path '*/active/*' -type f | sort
Safety Rules
- Read-only only. No branch switching, plan edits, or fetch unless
--fetchis explicit. - Treat selected-plan inference as tentative unless it came from an explicit
--selected-planargument. - Remote branch data is stale-by-default unless
--fetchis explicit. - Use this for session handoff and quick repo orientation, not for workflow control.
- If the scan cannot prove something, emit a warning instead of guessing.
Good trigger phrases:
what's in flightgive me a handoff summarywhat active plans do we haveshow branch and worktree statuswhat should I look at next
Load references/watzup-workflow.md when you need the project's decision tree or hint-priority rules.
References
04 同仓库更多 Skills
zustand
Rules and standards for state management using Zustand in React and Next.js. Use when implementing client-side stores, persistence with localStorage, or preventing SSR hydration mismatch.
zod
Zod v4 schema validation best practices. Use when defining schemas, utilizing safeParse, or customizing error messages.
upstash-ratelimit
Rules, standards, and references for rate limiting in serverless environments using Upstash Ratelimit. Use when implementing rate limiting, configuring Upstash Redis, or handling request blocking.
ui-design
UI/UX and frontend design best practices guidelines (formerly frontend-design). This skill should be used when writing, reviewing, or designing frontend code to ensure accessibility, performance, and usability. Triggers on tasks involving HTML structure, CSS styling, responsive layouts, form design, animations, or accessibility improvements.
typescript
TypeScript performance, tsconfig, type errors, async patterns — triggered when the user asks to "optimize TypeScript performance", "speed up tsc compilation", "configure tsconfig.json", "fix type errors", "improve async patterns", or encounters TS errors (TS2322, TS2339, "is not assignable to"). Also triggers on .ts, .tsx, .d.ts file work involving type definitions, module organization, or memory management. Does NOT cover TypeScript basics, framework-specific patterns, or testing.
typescript-refactor
TypeScript and TSX refactoring and modernization guidelines from a principal specialist perspective, current to TypeScript 6.0 and React 19. This skill should be used when refactoring, reviewing, or modernizing TypeScript or React/TSX code for type safety, compiler performance, and idiomatic patterns. Triggers on tasks involving type architecture, narrowing, generics, discriminated unions, error handling, React component and hook typing, or migration to modern TypeScript features (satisfies, using, const type parameters, inferred type predicates, isolatedDeclarations, erasable syntax, import attributes).