review

Analyze feature branch diffs for SQL safety and trust boundary issues.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Kakarottoooo/onegent --skill review-kakarottoooo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Kakarottoooo/onegent/tree/main/.agents/skills/gstack/review
Command: npx skills add https://github.com/Kakarottoooo/onegent --skill review-kakarottoooo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review analyzes diffs between the feature branch and the base branch to surface structural issues that tests often miss, helping teams merge safer changes.

Core Features & Use Cases

  • Analyzes SQL safety, LLM trust boundary violations, and conditional side effects in proposed changes.
  • Provides proactive recommendations and flags potential risks before merge.
  • Integrates with existing PR workflows to guide reviewers on where to focus.

Quick Start

Review the current PR against the base branch and run the /review workflow to surface issues before merging.

Frequently Asked Questions about review

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

FAQPage Schema
How does pre-landing PR review catch structural issues that tests miss?

Pre-landing PR review analyzes diffs between feature and base branches to detect structural risks like SQL safety and LLM trust boundary violations before merge. It surfaces conditional side effects and proactive recommendations that automated tests often overlook.

How do I review a PR diff for SQL safety and LLM trust boundary violations?

You can review a PR diff for SQL safety and LLM trust boundary violations by running the review workflow against your feature branch. It analyzes the diff and flags structural issues, providing proactive suggestions to guide reviewers before merge.

Can I run a pre-landing review on my feature branch before merging?

Yes, you can run a pre-landing review on your feature branch before merging. The review process analyzes the diff between your feature branch and the base branch to identify structural issues and provides proactive suggestions.

What is the best way to catch conditional side effects in a pull request?

The best way to catch conditional side effects in a pull request is using a pre-landing review tool. It analyzes branch diffs to target conditional side effects and other structural risk areas that tests may miss, offering recommendations before merge.

Does pre-landing review work with existing CI workflows?

Pre-landing review integrates with existing PR workflows to guide reviewers on where to focus. It analyzes the diff between branches to flag SQL safety, LLM trust boundary violations, and other risks, fitting naturally into your CI pipeline.

Why should I use pre-landing review instead of relying only on tests?

You should use pre-landing review because tests often miss structural issues. Pre-landing review analyzes branch diffs to proactively target SQL safety, LLM trust boundary violations, and conditional side effects, surfacing risks before you merge.