skills.rest
sajalsuhane
sajalsuhaneCOMMUNITY
Explore all skills by this author →
Website𝕏@SajalSuhane1998GitHub

review

Audit PR diffs for SQL safety, data integrity, and scope drift.

Updated Dec 22, 2019
Search Tags:#safety#quality#review#code-review#pull-request#diff-analysis
One-click install
npx skills add https://github.com/sajalsuhane/sajalsuhane.github.io --skill review-sajalsuhane
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/sajalsuhane/sajalsuhane.github.io/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/sajalsuhane/sajalsuhane.github.io --skill review-sajalsuhane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews often miss structural issues and drift from requested scope. This skill provides a structured audit of diffs to surface SQL safety concerns, data integrity risks, and unintended side effects before merging.

Core Features & Use Cases

  • Detects scope drift between a feature branch and the base branch.
  • Highlights risks across SQL safety, data integrity, and conditional side effects.
  • Use Case: before landing a PR, run the audit to surface actionable fixes and safety checks.

Quick Start

Run the /review workflow on your feature branch to kick off a pre-landing PR audit.

Frequently Asked Questions about review

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

FAQPage Schema
How do I audit a pull request for SQL safety before merging?▼

To audit a pull request for SQL safety, run a pre-landing review workflow on your feature branch to detect data integrity risks and surface actionable remediation steps before merging.

What is the best way to detect scope drift in a feature branch diff?▼

Detecting scope drift in a feature branch diff requires auditing the changes against your project goals to identify unintended side effects and structural issues before they land.

How do I check data integrity risks in a backend code diff?▼

Checking data integrity risks in a backend code diff involves evaluating the planned changes to surface conditional side effects and structural issues across your SQL statements and backend logic.

Can I run a code review audit on both backend changes and tests?▼

Yes, you can run a code review audit on backend changes, tests, and documentation by evaluating the diff against the base branch to surface safety concerns and change impacts.

What are the limitations of automated diff analysis for pre-landing reviews?▼

Automated diff analysis for pre-landing reviews requires reading the planned changes and evaluating them against project goals, meaning it depends on clearly defined objectives to accurately surface concrete remediation steps.

Related Skills

Explore More Software Engineering Skills→
GeneralJerelGeneralJerel
6

review-code

Analyze code changes for security, performance, and maintainability impacts.

Community
Advanced
olaafrossiolaafrossi
10

review

Analyze diffs for SQL safety, LLM trust boundaries, and side effects.

Community
Advanced
tilework-techtilework-tech
149

Finishing a Development Branch

Run tests, formatters, linters, type checks, and submit a PR.

Official
Intermediate
blundergoatblundergoat

goat-qa

Map code changes to test suites and identify coverage gaps.

Official
Advanced