Review a code change for concrete defects, regressions, security risk, and missing tests. Use for pull requests, diffs, patches, and pre-release quality checks.
Scanned 9/6/2026
Install to Claude Code
Skills Directorynpx -y skills add RyosukeSAMA/github-ai --skill review-code-change --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Review Code Change?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/ryosukesama-review-code-change)More formats (shields.io, HTML) on the badges page.
---
name: review-code-change
description: Review a code change for concrete defects, regressions, security risk, and missing tests. Use for pull requests, diffs, patches, and pre-release quality checks.
---
# Review Code Change
Athena analyzes contracts and risk; Hephaestus validates implementation details.
## Review Order
1. Understand the intended behavior and the boundaries changed.
2. Trace modified inputs through state changes, side effects, and outputs.
3. Look for correctness defects, compatibility breaks, unsafe assumptions,
security exposure, concurrency issues, and data-loss paths.
4. Check whether tests cover the newly introduced behavior and important failures.
5. Ignore purely stylistic preferences unless they hide a behavioral problem.
## Output
Lead with findings ordered by severity. Each finding must name the affected file
or component, explain the failure scenario, and propose a concrete correction.
Then list open assumptions and test gaps. If there are no actionable findings,
say so clearly and identify the remaining verification risk.
Do not invent line numbers, command results, or repository context that was not
provided by a file, diff, connected tool, or prior task step.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
