skills.rest
ShaheerKhawaja
ShaheerKhawajaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

review

Identify code change risks across diffs, branches, or files.

8|Updated Mar 17, 2026
Search Tags:#testing#security#dependencies#diff#code-review#risk-analysis
One-click install
npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill review-shaheerkhawaja
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/ShaheerKhawaja/ProductionOS/tree/main/skills/review
Command: npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill review-shaheerkhawaja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing review workflow that surfaces SQL safety risks, LLM trust boundaries, conditional side effects, missing tests, dependency risks, and security issues in code changes before merging.

Core Features & Use Cases

  • Evidence-driven findings with severity ordering, file references, and line numbers.
  • Scope-aware analysis that works on diffs, branches, or individual files.
  • Clear remediation guidance and guardrails to improve code quality and security.
  • Use Case: during a PR, run the review to quickly surface high-risk issues and coverage gaps.

Quick Start

Provide the scope (diff, branch, or file) and run the pre-landing review to surface actionable findings.

Frequently Asked Questions about review

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

FAQPage Schema
How do I run a pre-landing code review on a pull request?▼

Pre-landing code review identifies risks in SQL safety, LLM trust boundaries, conditional side effects, missing tests, dependency risks, and security issues. It returns prioritized findings with severity, file references, and concrete remediation steps.

What is the best way to analyze code changes for security and dependency risks?▼

Pre-landing code review analyzes code changes for security and dependency risks by applying scope-aware analysis to the provided diff. It surfaces evidence-driven findings ordered by severity with clear remediation guidance.

Does pre-landing risk analysis work on individual files or only full branches?▼

Pre-landing risk analysis works on individual files, diffs, and branches. The scope-aware analysis identifies code changes and their potential risks across the repository regardless of the input scope provided.

How do I check SQL safety and LLM trust boundaries before merging code?▼

To check SQL safety and LLM trust boundaries before merging, run a pre-landing code review on your changes. It identifies these specific risks along with missing tests and conditional side effects, returning actionable findings.

Can pre-landing code review identify missing tests in my diff?▼

Yes, pre-landing code review identifies missing tests in your diff. The analysis surfaces coverage gaps alongside security issues and dependency risks, providing concrete remediation steps for each finding.

Related Skills

Explore More Software Engineering Skills→
stevenevanstevenevan
1

review-complex-task

Coordinate multi-specialist code reviews for complex branch changes using git diff analysis.

Community
Advanced
antriksh-29antriksh-29

review

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

Community
Advanced
magicpro97magicpro97
8

merge-when-green

Automatically merge GitHub pull requests after all required CI checks pass.

Community
Intermediate
EdgeHuntEdgeHunt

ck:security-scan

Scan codebases for hardcoded secrets, dependency issues, and vulnerability patterns.

Official
Intermediate