skills.rest
ajayjoshi-ciphersonic
ajayjoshi-ciphersonicCOMMUNITY
Explore all skills by this author →
GitHub

review

Analyze code diffs for SQL safety and structural issues.

1|Updated May 5, 2026
Search Tags:#code review#deep analysis#SQL safety#LLM trust#pre-landing review
One-click install
npx skills add https://github.com/ajayjoshi-ciphersonic/octo-reach --skill review-ajayjoshi-ciphersonic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/ajayjoshi-ciphersonic/octo-reach/tree/main/.claude/skills/review
Command: npx skills add https://github.com/ajayjoshi-ciphersonic/octo-reach --skill review-ajayjoshi-ciphersonic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, read, edit, write, grep, glob, gstack, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the review of code changes before they are landed, identifying potential issues such as SQL safety, LLM trust boundary violations, conditional side effects, and more, to maintain high code quality.

Core Features & Use Cases

  • Automated Code Review: Analyzes diffs against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues.
  • Pre-Landing Analysis: Use when preparing to merge or land code changes, ensuring code quality before it goes live.
  • Use Case: When you are about to merge a PR, use this Skill to check for potential issues that could affect the stability or security of the codebase.

Quick Start

Run the review skill with the command '/review' followed by the branch name to get a comprehensive code review report for that branch.

Frequently Asked Questions about review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review for SQL safety and LLM trust boundary violations?▼

Automated code review analyzes diffs against a base branch to identify SQL safety issues, LLM trust boundary violations, and conditional side effects. Running '/review' with the branch name generates a comprehensive report highlighting these structural problems.

What is pre-landing code review and when do I need it?▼

Pre-landing code review is the process of analyzing code changes before merging or landing them. You need it when preparing to merge a PR, ensuring codebase stability and security by catching potential issues before they go live.

Can I use automated code review with my existing bash and grep environment?▼

Automated code review requires bash, read, edit, write, grep, glob, and the gstack framework to function. These dependencies are used to analyze diffs and identify structural issues within your codebase.

What is the best way to check code changes for conditional side effects before merging?▼

The best way to check for conditional side effects before merging is to run an automated review on your branch diffs. This deep analysis detects structural issues and trust boundary violations to maintain high code quality.

Does automated code review work for analyzing diffs against a specific base branch?▼

Yes, automated code review analyzes diffs against the base branch. By running '/review' followed by the branch name, it evaluates the changes for SQL safety and other structural issues to produce a comprehensive report.

What are the limitations of using automated scripts for deep code analysis?▼

Automated deep code analysis relies on the gstack framework and specific dependencies like bash, grep, and glob. It focuses on structural issues, SQL safety, and trust boundaries, meaning it complements but does not replace human code review.

Related Skills

Explore More Software Engineering Skills→
zzxtbetazzxtbeta

ship

Merge base branch, run tests, bump VERSION, and create a PR.

Community
Advanced
aporto-techaporto-tech

gstack-review

Analyze code diffs for SQL safety and LLM trust boundary violations.

Official
Advanced
zbruhnkezbruhnke
16

code-review

Review Git code changes for correctness, security, performance, and maintainability.

Community
Intermediate
yanochka11yanochka11

review

Analyze repository diffs to identify defects, security risks, and structural problems.

Community
Advanced