菜单
Quick pre-commit sanity check — validate post-implementation changes against the aio-snapshot baseline via change detection, duplication detection, and type checking. Light pass; for deep multi-agent review use aio-review-deep.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Runs an adaptive, project-aware code-review workflow (profile the project, detect its lint tools + conventions, run mechanical + semantic review, consolidate into an LGTM verdict) and carries the Google eng-practices playbook it applies — reviewer (what to look for, when to approve, severity-labeled comments, handling pushback) and PR/CL author (CL descriptions, splitting changelists, responding to comments). Use when reviewing or authoring a PR/MR/CL/diff, running a code review, deciding LGTM or LGTM threshold, authoring a merge request, assessing code health, handling a hotfix review, or replying to review feedback.
Push books/docs and read notes from an Onyx BOOX e-reader account (push.boox.com / send2boox.com) WITHOUT the web UI, via the self-contained `boox.mjs` CLI. Uploads a file to Aliyun OSS, writes a digital_content doc into the device's MESSAGE sync channel, and calls saveAndPush to notify the device — the exact 3-step flow the web app performs. Also lists the push list, lists synced notes, removes pushed items, and shows device online status. Auth = long-lived JWT via BOOX_TOKEN env or a token file.
Capture this session's repeatable process into a reusable SKILL.md file via guided interview.
Turn Claude into a wise, effective teacher whose only goal is to make sure YOU deeply understand the work an AI agent just did — the problem it solved, why that problem existed, the solution and its design decisions, the edge cases it handled, and the broader impact. Incremental and mastery-gated: it has you restate your understanding first, fills the gaps at the depth you ask for (eli5 / eli14 / like-an-intern), shows you the real code, and quizzes you with AskUserQuestion — and it does not conclude until you have demonstrably understood. Use when the AI moved faster than you could follow and you want to catch up before merging. Trigger on "teach me", "help me understand what you did", "make sure I understand this change", "walk me through this", "explain the session", "I don't get it", "why did you do it this way", "quiz me", "eli5 / eli14", "don't let me fall behind", "I want to actually understand this, not just merge it", "catch me up", "bring me up to speed", "I fell behind", "the AI moved too fast".
Architecture decision advisor — guides pattern selection, application, synthesis, and stress-testing for system design, scaling, resilience, and migration decisions.
Look up architecture patterns and concepts via semantic search — read the full article on demand, compare patterns side-by-side, or browse by volume.
| name | aio-review-quick |
| description | Quick pre-commit sanity check — validate post-implementation changes against the aio-snapshot baseline via change detection, duplication detection, and type checking. Light pass; for deep multi-agent review use aio-review-deep. |
| when_to_use | check my changes, before I commit, did I miss anything, review implementation, validate changes, post-implementation review, verify work, change validation, pre-commit check, quick review |
| effort | medium |
| context | fork |
npx gitnexus status 2>/dev/null && echo "AVAILABLE" || echo "NOT INSTALLED"Review completed work using change detection, duplication detection, and type checking.
/aio-snapshotnpx gitnexus analyze) for duplication checkdetect_changes()
For each changed file, get symbol context:
context(file)
For each new function or significant code block, use the GitNexus MCP query tool:
query("description of new code")
Flag if similarity >0.75 — potential duplication or missed reuse.
query("pattern used in new code")
Verify new code follows existing conventions.
lsp_diagnostics(file) → errors in changed files
lsp_diagnostics_directory(dir) → broader check
## Review: [what was implemented]
### Changes (from detect_changes)
- `file-a.ts`: Added `fnX`, modified `fnY`
- `file-b.rs`: Added struct `Z`, new command `cmd`
### Duplication Check
- OK: No similar code found for `fnX`
- WARNING: `fnY` is 78% similar to `existingFn` in `other.ts`
### Convention Check
- OK: Follows pattern from `similar-file.ts`
- NOTE: [any deviations]
### Type Safety
- N errors, M warnings
### Checklist
- [ ] Logic in correct layer? (backend vs frontend)
- [ ] No duplicated business logic? (SSOT)
- [ ] Proper fix, not a workaround?
- [ ] Easy to change tomorrow? (iteration-first)
Skip change detection. Just run:
lsp_diagnostics on changed filesqueryAfter review completes:
| Result | Next skill |
|---|---|
| Review clean, ready to merge | /superpowers:verification-before-completion → /superpowers:finishing-a-development-branch |
| Issues found, needs fixes | Fix issues → re-run /aio-review-quick |
| Needs full code review (security, architecture) | /aio-review-deep — parallel multi-agent review with OMC agents |
| Want to extract learnings | /aio-reflect — capture knowledge from this session |