full-review
From the author
Run every review skill at once — build-check, then design-check, code-audit, security-audit, a11y-audit and perf-audit fanned out across parallel agents — and merge them into one deduplicated, severity-ranked report. Use when asked for a full/complete review, to review everything before shipping or merging, or to run all the checks.
Install
npx skills add arcasilesgroup/ai-engineering --skill full-review -a claude-code
Installs to .claude/skills/full-review/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 82
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- unified-reviewathola/claude-night-marketOrchestrates multi-domain review (code, arch, tests, security) in a single pass. Use when thorough pre-release review is needed.Engineering★ 343
- review-prtobihagemann/turboReview a pull request by fetching PR comments, running a comprehensive code review, evaluating findings, and dispatching to implementation. Use when the user asks to "review PR", "review pull request", "review this PR", "check PR before merging", or "full PR review".Engineering★ 416
- requesting-code-reviewforyourhealth111-pixel/Vibe-SkillsPrepare and request a code review after implementation or before merge by assembling scope, requirements, git range, and reviewer instructions.Engineering★ 3.8K
- ai-code-reviewarcasilesgroup/ai-engineeringComprehensive code review skill. Two modes: diff review for over-engineering findings (ranked, compact), and debt collection for deferred shortcut ledgers. Checks against AGENTS.md code style rules (KISS, YAGNI, DRY, early returns, naming). Use when the user asks to "review code", "code review", "find over-engineering", "check for bloat", or "review this diff". Not for diagnosing runtime failures — use /ai-debug. Not for judging correctness of a diff — use /ai-verify. Not for writing documentation — use /ai-write.Engineering★ 61
- reviewhashgraph-online/awesome-codex-pluginsUse before merge, after subagents, or for spec/plan review.Engineering★ 1.4K
- reviewing-prMicrock/ordinary-claude-skillsUse when reviewing pull requests with comprehensive code analysis, incremental or full review options, and constructive feedback - provides thorough code reviews with severity ratingsEngineering★ 407
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in