skills.rest
FxHollow
FxHollowCOMMUNITY
Explore all skills by this author →
GitHub

review

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

Updated Mar 26, 2026
Search Tags:#automation#checklist#review#diff#code-quality#pr#gstack
One-click install
npx skills add https://github.com/FxHollow/100000mrr-landing --skill review-fxhollow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/FxHollow/100000mrr-landing/tree/main/.agents/skills/gstack/review
Command: npx skills add https://github.com/FxHollow/100000mrr-landing --skill review-fxhollow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a framework to analyze a PR diff against the base branch, identify structural and safety issues, and surface actionable improvements before merging.

Core Features & Use Cases

  • Surface SQL safety concerns, LLM trust boundary violations, and potential side effects in PR diffs.
  • Generate deterministic, planful recommendations and status reports (DONE, PARTIAL, NOT DONE) to guide developers and reviewers.
  • Produce a plan-style audit with traceable file changes and recommended next steps to improve code health.

Quick Start

Review the current branch diff against the base branch, run the built-in checklist, and generate an action-oriented report with concrete items.

Frequently Asked Questions about review

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

FAQPage Schema
How do I check a PR diff for SQL safety and LLM trust boundary violations?▼

You can review a PR diff by applying a structured checklist against the base branch to identify SQL safety and LLM trust boundary violations. This surfaces structural risks and produces an action-oriented plan with DONE, PARTIAL, or NOT DONE statuses to guide fixes.

How do I generate an action-oriented code review report for a branch diff?▼

Generate an action-oriented code review report by analyzing the branch diff against the base branch and applying a built-in checklist. This yields a structured conformance report with traceable file changes, DONE, PARTIAL, or NOT DONE statuses, and recommended next steps.

What is a structured code review checklist and when do I need it for safer PRs?▼

A structured code review checklist is a framework that identifies structural issues and safety concerns in a PR diff before merging. You need it to surface potential side effects, SQL safety issues, and LLM trust boundary violations to ensure safer PRs.

Can I automate code quality checks for PR diffs against a base branch?▼

Yes, you can automate code quality checks by applying a deterministic checklist to a PR diff against the base branch. This framework automatically surfaces structural issues, identifies critical defects, and generates planful recommendations with status reports.

What is the best way to surface structural issues and potential side effects in a codebase?▼

The best way to surface structural issues and potential side effects is to generate a plan-style audit of a PR diff against the base branch. This approach produces traceable file changes, conformance reports, and recommended next steps to improve code health.

Related Skills

Explore More Software Engineering Skills→
AkbarDevopAkbarDevop

review

Identify production-risk findings in a code diff before merging.

Community
Advanced
shaythegay13shaythegay13

review

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

Community
Advanced
omeraltnomeraltn

agency-api-tester

Validate RESTful API functionality, security, and performance in CI/CD pipelines.

Community
Advanced
act70255act70255

lint-and-validate

Lint and statically analyze Node.js and Python code with ESLint, Pylint, Ruff, MyPy, and Bandit.

Community
Advanced