check

Name: check
Author: tw93

6.6kstars384forks

How to install check?

tw93/waza/check

$npx -y skills add tw93/Waza --skill check

Installs into the current project.

Summary

Reviews code diffs, PRs, issue queues, release readiness, commits, pushes, publishing, and project audits. Use when users ask in any language for code review, issue or PR triage, release gates, publishing follow-through, or project audits. Not for debugging root causes or prose r

Files · 1

View on GitHub

SKILL.md

1	# Check: Review Before You Ship
2
3	Prefix your first line with 🥷 inline, not as its own paragraph.
4
5	Update check (non-blocking). Once per conversation, run `bash <skill-base-dir>/scripts/check-update.sh` with `<skill-base-dir>` replaced by this skill's base directory; relay any printed line, otherwise continue silently (also when the script already ran, is missing, or errors). It checks at most once a day, reads only a public version file, and sends no data.
6
7	> Note: `/review` is a built-in Anthropic plugin command for PR review. Waza uses `/check` (or the alias `code-review`) instead. Do not re-trigger `/review` from within this skill.
8
9	Read the diff, find the problems, fix what can be fixed safely, ask about the rest. Done means verification ran in this session and passed.
10
11	## Outcome Contract
12
13	- Outcome: a review, release decision, or maintainer action grounded in the current diff, project context, and live evidence.
14	- Done when: findings, fixes, shipped state, or blockers are stated with the commands, artifacts, or remote state that prove them.
15	- Evidence: worktree status, diff, public project docs, manifests, CI, package contents, release or registry state, and current command output.
16	- Output: concise findings first, then verification and shipped-state summary when applicable. Multi-step or ship-action runs close with a completion ledger (done / not applicable / remaining), never a narrative that leaves the user asking "is everything done".
17
18	## Worktree Safety Preflight
19
20	Before any review, triage, ship, release, or PR operation, read the current worktree with:
21
22	```bash
23	git status --short --branch -uall
24	```
25
26	Treat modified, staged, and untracked files as user work. You may read them and include them in the review surface, but you must not move, hide, overwrite, clean, or discard them without explicit user approval in the current turn.
27
28	Do not run these commands as default review or PR setup: `git switch`, `git checkout`, `git reset --hard`, `git clean`, `git stash -u`, `git stash --include-untracked`, `git stash -a`, `git stash --all`, or `gh pr checkout`. If a branch change or cleanup is genuinely required, stop and ask for that exact operation.
29
30	Do not "protect" user work by moving untracked files, generated files, screenshots, or local scratch files into `/tmp` or another holding directory. Moving someone else's WIP out of the checkout is the same class of interference as stashing it. If a clean tree is required for generation, packaging, or verification, use a separate worktree from a known commit and copy only the artifact or patch you own back into the current checkout.
31
32	For commit or push follow-through in a dirty or multi-agent checkout, record `git rev-parse HEAD` before staging. Re-read `git status --short --branch -uall` and `git rev-parse HEAD` immediately before commit and again before push. If HEAD moved, unknown commits appeared, or the worktree changed outside your intended files, stop and report the mismatch instead of rebasing, recommitting, or pushing.
33
34	For PR inspection, prefer commands that do not switch the current working tree: `gh pr view`, `gh pr diff`, `git fetch origin pull/<n>/head:refs/tmp/pr-<n>`, and `git merge-tree`.
35
36	## Mode Picker
37
38	Pick the mode that matches the user's intent, then read that section in full. Modes layer on top of the shared review surface (Scope, Hard Stops, Autofix, Specialist Review, Verification, Sign-off) further down.
39
40	\| User intent \| Mode \|
41	\|---\|---\|
42	\| "implement this plan", `/think` output handed off \| [Plan Execution](#plan-execution-mode) \|
43	\| Diff or PR ready, "review", "看看代码", "合并前" \| Default review (start at [Get the Diff](#get-the-diff)) \|
44	\| "look at issues", "review PRs", "triage", "批量处理" \| [Triage Mode](#triage-mode) \|
45	\| "is this worth a release", "值不值得发版" \| [Release Worthiness Analysis](#release-worthiness-analysis) \|
46	\| "commit", "push", "publish", "release", "close issue", "发布表情" \| [Ship / Release Follow-through](#ship--release-follow-through) \|
47	\| "audit", "项目体检", "项目评分", "给项目打分", "深入分析项目代码"

People who liked this also viewed

6 picks

Type

check

6.6kstars384forks

View on GitHub

How to install check?

tw93/waza/check

$npx -y skills add tw93/Waza --skill check

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Check: Review Before You Ship
2
3	Prefix your first line with 🥷 inline, not as its own paragraph.
4
5	Update check (non-blocking). Once per conversation, run `bash <skill-base-dir>/scripts/check-update.sh` with `<skill-base-dir>` replaced by this skill's base directory; relay any printed line, otherwise continue silently (also when the script already ran, is missing, or errors). It checks at most once a day, reads only a public version file, and sends no data.
6
7	> Note: `/review` is a built-in Anthropic plugin command for PR review. Waza uses `/check` (or the alias `code-review`) instead. Do not re-trigger `/review` from within this skill.
8
9	Read the diff, find the problems, fix what can be fixed safely, ask about the rest. Done means verification ran in this session and passed.
10
11	## Outcome Contract
12
13	- Outcome: a review, release decision, or maintainer action grounded in the current diff, project context, and live evidence.
14	- Done when: findings, fixes, shipped state, or blockers are stated with the commands, artifacts, or remote state that prove them.
15	- Evidence: worktree status, diff, public project docs, manifests, CI, package contents, release or registry state, and current command output.
16	- Output: concise findings first, then verification and shipped-state summary when applicable. Multi-step or ship-action runs close with a completion ledger (done / not applicable / remaining), never a narrative that leaves the user asking "is everything done".
17
18	## Worktree Safety Preflight
19
20	Before any review, triage, ship, release, or PR operation, read the current worktree with:
21
22	```bash
23	git status --short --branch -uall
24	```
25
26	Treat modified, staged, and untracked files as user work. You may read them and include them in the review surface, but you must not move, hide, overwrite, clean, or discard them without explicit user approval in the current turn.
27
28	Do not run these commands as default review or PR setup: `git switch`, `git checkout`, `git reset --hard`, `git clean`, `git stash -u`, `git stash --include-untracked`, `git stash -a`, `git stash --all`, or `gh pr checkout`. If a branch change or cleanup is genuinely required, stop and ask for that exact operation.
29
30	Do not "protect" user work by moving untracked files, generated files, screenshots, or local scratch files into `/tmp` or another holding directory. Moving someone else's WIP out of the checkout is the same class of interference as stashing it. If a clean tree is required for generation, packaging, or verification, use a separate worktree from a known commit and copy only the artifact or patch you own back into the current checkout.
31
32	For commit or push follow-through in a dirty or multi-agent checkout, record `git rev-parse HEAD` before staging. Re-read `git status --short --branch -uall` and `git rev-parse HEAD` immediately before commit and again before push. If HEAD moved, unknown commits appeared, or the worktree changed outside your intended files, stop and report the mismatch instead of rebasing, recommitting, or pushing.
33
34	For PR inspection, prefer commands that do not switch the current working tree: `gh pr view`, `gh pr diff`, `git fetch origin pull/<n>/head:refs/tmp/pr-<n>`, and `git merge-tree`.
35
36	## Mode Picker
37
38	Pick the mode that matches the user's intent, then read that section in full. Modes layer on top of the shared review surface (Scope, Hard Stops, Autofix, Specialist Review, Verification, Sign-off) further down.
39
40	\| User intent \| Mode \|
41	\|---\|---\|
42	\| "implement this plan", `/think` output handed off \| [Plan Execution](#plan-execution-mode) \|
43	\| Diff or PR ready, "review", "看看代码", "合并前" \| Default review (start at [Get the Diff](#get-the-diff)) \|
44	\| "look at issues", "review PRs", "triage", "批量处理" \| [Triage Mode](#triage-mode) \|
45	\| "is this worth a release", "值不值得发版" \| [Release Worthiness Analysis](#release-worthiness-analysis) \|
46	\| "commit", "push", "publish", "release", "close issue", "发布表情" \| [Ship / Release Follow-through](#ship--release-follow-through) \|
47	\| "audit", "项目体检", "项目评分", "给项目打分", "深入分析项目代码"

People who liked this also viewed

6 picks

Type