review
From the author
Pre-landing code review. Analyzes the diff against the base branch for SQL and data safety, race conditions, LLM trust-boundary violations, shell injection, enum completeness and other structural problems, fixes the mechanical ones and asks about the rest. Use when asked to "review this PR", "code review", "pre-landing review" or "check my diff", and when someone is about to merge.
Install
npx skills add Bevel-Software/Hexis --skill review -a claude-code
Installs to .claude/skills/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 83
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.
- code-reviewanthropics/knowledge-work-pluginsReview code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection risks, missing edge cases, or error handling gaps.OfficialEngineering★ 33.5K
- self-reviewapache/magpieRun a structured pre-flight self-review on local changes before opening a PR. Reads the diff against a configurable base (default: the merge base of HEAD and origin/<default-branch>), checks correctness, security, and project conventions, and returns a structured report. No state changes, no PR, no external writes — the report is the output.Engineering★ 129
- Pre-Landing Self-Reviewagentskillexchange/skillsStructured self-review checklist to run before committing substantial code changes. Covers edge cases, error paths, test coverage, documentation, and code quality — so CI is a last resort, not your first reviewer.Engineering★ 58
- differential-reviewtrailofbits/skillsPerforms security-focused differential review of code changes. Adapts analysis depth to codebase size, uses git blame for context, calculates blast radius by counting callers, checks test coverage of modified code, and generates a markdown report. Use when reviewing a PR, commit, or diff for security vulnerabilities, checking whether a change re-introduces a previously fixed bug, asking what else a change could break, or finding which modified code has no test covering it.Engineering★ 7.9K
- review-codetobihagemann/turboReview code for bugs, security vulnerabilities, API misuse, consistency issues, simplicity problems, or test coverage gaps and low-value tests by running internal reviews and a peer review in parallel and returning combined findings. Single-concern with a type argument, or full review with no argument. Use when the user asks to "review my code", "full code review", "review my changes", "check for bugs", "scan for bugs", "review correctness", "security audit", "find vulnerabilities", "review security", "check API usage", "verify against docs", "check for cross-file duplication", "review consistency", "check for code reuse", "review simplicity", "find untested code", "find redundant tests", or "review test coverage".Engineering★ 417
- 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
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in