skills.rest
NaKMiers
NaKMiersCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

review

Analyze pull request diffs for SQL safety, trust boundaries, and structural issues.

1|2|Updated Jan 4, 2024
Search Tags:#review#diff#code-quality#pr#llm-trust#pre-landing
One-click install
npx skills add https://github.com/NaKMiers/Port4lio --skill review-nakmiers
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/NaKMiers/Port4lio/tree/main/.agents/skills/review
Command: npx skills add https://github.com/NaKMiers/Port4lio --skill review-nakmiers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill analyzes pull request diffs to surface structural issues, safety gaps, and trust boundary problems before merging, reducing risk and review time.

Core Features & Use Cases

  • Diff analysis across SQL safety, LLM trust boundaries, and conditional side effects to surface issues early.
  • Guidance for reviewers and maintainers on how to resolve issues and improve PR quality.
  • Use Case: When reviewing a PR, run this skill to get an actionable plan and risk summary.

Quick Start

Provide a PR diff against the base branch and I will run a pre-landing review and return a risk summary with actionable fixes.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a PR diff for SQL safety and LLM trust boundary issues before merging?▼

To review a PR diff before merging, analyze the changes against routing rules to identify safety gaps, LLM trust boundary problems, and SQL risks, producing an actionable plan of recommended fixes to reduce merge risk.

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

A pre-landing code review analyzes pull request diffs to surface structural issues and safety gaps before merging. You need it when you want to reduce review time and catch trust boundary problems or conditional side effects prior to landing code.

How do I get an actionable plan for resolving code quality issues in a pull request?▼

To get an actionable plan for code quality issues, provide the PR diff against the base branch for analysis. The review examines repo context and routing rules to generate a risk summary with recommended changes for maintainers.

Does automated diff analysis work for spotting conditional side effects in my codebase?▼

Automated diff analysis works for spotting conditional side effects by examining the pull request changes and repo context. It targets these structural patterns alongside SQL safety and trust boundaries to surface issues early.

What is the best way to automate risk summaries for pull request reviews?▼

The best way to automate risk summaries is to run a pre-landing review on the PR diff. This analyzes the changes against routing rules to output a risk summary with actionable fixes, streamlining the review process for maintainers.

Can I use this pre-landing review without setting up any dependencies?▼

You can use this pre-landing review without setting up dependencies, as it requires no external components. Simply provide the PR diff against the base branch to run the analysis and receive a risk summary with recommended changes.

Related Skills

Explore More Software Engineering Skills→
jm199seojm199seo

review

Analyze pull request diffs against the base branch for structural issues.

Community
Advanced
antriksh-29antriksh-29

review

Analyzes diffs for SQL safety, LLM trust boundary violations, and side effects pre-merge.

Community
Advanced
2460124601

review

Analyze diffs and PR context for structural, data-safety, and quality issues.

Community
Advanced
Obsidian-OwlObsidian-Owl
9

gate-wiring

Detect unused exports, orphaned files, layer violations, and circular dependencies in changed code.

Official
Intermediate