Check
Run diff-grounded code review, merge/release gates, and project-wide quality scorecards before you ship or publish.
Overview
Check is an agent skill most often used in Ship (also Ship launch sub-work, Operate iterate) that reviews real diffs and release artifacts with safety gates before merge or publish.
Install
npx skills add https://github.com/tw93/waza --skill checkWhat is this skill?
- Reviews code diffs, PRs, issues, commits, and release/publish/push flows with explicit safety gates for dirty or untrack
- Supports project-wide code-quality audit scorecards (项目体检 / scorecard / rate this codebase)
- Can implement an approved plan after review when the user asks to continue optimization
- Distinct from Waza `/review` plugin—uses `/check` or `code-review` alias to avoid double-triggering Anthropic’s built-in
- Done means verification ran in-session and passed—not a prose-only opinion
Adoption & trust: 6.6k installs on skills.sh; 5.6k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are about to merge, release, or push but lack a diff-grounded review that also respects dirty worktrees and skips idea exploration.
Who is it for?
Solo maintainers running pre-merge review, release gates, GitHub publish/push follow-through, or a one-session codebase scorecard.
Skip if: Brainstorming features, debugging root causes, or literary/content review—the skill README explicitly routes those elsewhere.
When should I use this skill?
review, 看看代码, 合并前, release, publish, push, code review, project audit, scorecard, before merge, implement approved plan
What do I get? / Deliverables
You get a verified review or release decision on the current diff, with safe fixes applied where possible and clear asks for everything else.
- Review findings tied to the current diff
- Release/merge recommendation
- Optional safe in-tree fixes and verification results
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Ship because the skill’s contract is review-before-merge and release readiness, not ideation or root-cause debugging. Review subphase matches pre-merge checks, PR/issue triage, and maintainer actions tied to the current diff.
Where it fits
Run `/check` on a feature branch before opening or merging a PR.
Gate a release or publish/push with verification that artifacts match the diff.
Score and prioritize tech-debt fixes after a project-wide audit scorecard.
Implement the next slice of an already-approved plan with review between commits.
How it compares
Use instead of ad-hoc “looks fine” chat review when you need diff evidence and release safety sinks.
Common Questions / FAQ
Who is check for?
Indie builders and small-team maintainers using Claude Code or similar agents who want `/check`-style review before merge, release, or project audit—not open-ended design chat.
When should I use check?
In Ship for pre-merge and code review; before release, publish, or push; when triaging issues/PRs; or when you want a project-wide quality scorecard. Also when continuing an already-approved implementation plan with review gates.
Is check safe to install?
Treat it as a powerful git/filesystem reviewer that may modify safe fixes—review the Security Audits panel on this Prism page and your worktree state before allowing auto-fixes.
SKILL.md
READMESKILL.md - Check
# Check: Review Before You Ship Prefix your first line with 🥷 inline, not as its own paragraph. > 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. 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. ## Outcome Contract - Outcome: a review, release decision, or maintainer action grounded in the current diff, project context, and live evidence. - Done when: findings, fixes, shipped state, or blockers are stated with the commands, artifacts, or remote state that prove them. - Evidence: worktree status, diff, public project docs, manifests, CI, package contents, release or registry state, and current command output. - Output: concise findings first, then verification and shipped-state summary when applicable. ## Worktree Safety Preflight Before any review, triage, ship, release, or PR operation, read the current worktree with: ```bash git status --short --branch -uall ``` 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. 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. 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`. ## Mode Picker 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. | User intent | Mode | |---|---| | "implement this plan", `/think` output handed off | [Plan Execution](#plan-execution-mode) | | Diff or PR ready, "review", "看看代码", "合并前" | Default review (start at [Get the Diff](#get-the-diff)) | | "look at issues", "review PRs", "triage", "批量处理" | [Triage Mode](#triage-mode) | | "is this worth a release", "值不值得发版" | [Release Worthiness Analysis](#release-worthiness-analysis) | | "commit", "push", "publish", "release", "close issue", "发布表情" | [Ship / Release Follow-through](#ship--release-follow-through) | | "audit", "项目体检", "项目评分", "给项目打分", "深入分析项目代码", "scorecard", "linus review" | [Project Audit](#project-audit-mode) | | Document, PDF, prose review | Delegate to `/write` (see [Document Review](#document-review)) | Before any mode, run [Project Context Extraction](#project-context-extraction) and (if memory is in scope) [Durable Context Preflight](#durable-context-preflight). ## Plan Execution Mode Activate wh