skills.rest
fghaffar
fghaffarCOMMUNITY
Explore all skills by this author →
GitHub

review

Analyze git diffs for SQL safety, race conditions, and LLM trust boundaries.

Updated Mar 25, 2026
Search Tags:#code review#pr review#race conditions#git diff#llm security#sql safety#checklist audit
One-click install
npx skills add https://github.com/fghaffar/faystack --skill review-fghaffar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/fghaffar/faystack/tree/main/review
Command: npx skills add https://github.com/fghaffar/faystack --skill review-fghaffar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill performs a thorough pre-landing review of code changes to detect hidden issues like SQL injection risks, race conditions, and incomplete enum handling that tests might miss, preventing production failures and security vulnerabilities.

Core Features & Use Cases

  • Critical Safety Checks: Scans for SQL safety, concurrency issues, and LLM output trust boundaries to ensure data integrity.
  • Informational Audits: Identifies test gaps, performance impacts, and design inconsistencies for higher code quality.
  • Use Case: When working on a feature branch with database updates, run this Skill to verify no N+1 queries or missing validations slip through before creating a pull request.

Quick Start

Invoke the review skill on your current git branch to analyze the diff against the base branch for potential issues.

Frequently Asked Questions about review

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

FAQPage Schema
How do I run an automated code review on a git diff for SQL injection risks?▼

An automated code review of a git diff analyzes branch changes against the base to detect SQL injection risks, race conditions, and incomplete enum handling. It applies automated checklists to ensure concurrency safety and production readiness before merging.

What is the best way to catch race conditions and LLM trust boundary issues before merging code?▼

Catching race conditions and LLM trust boundary issues requires a pre-landing pull request review that scans git diffs for structural problems. This automated checklist application ensures concurrency safety and validates LLM output boundaries before merging.

Can I use this to check enum completeness and concurrency safety in my pull request?▼

Yes, this skill analyzes git diffs to verify enum completeness and concurrency safety in pull requests. It applies automated checklists to ensure structural issues like missing enums and race conditions are resolved before landing.

Does this code review skill identify N+1 queries and missing validations in database updates?▼

Yes, this skill identifies N+1 queries and missing validations by performing informational audits on git diffs. It detects test gaps, performance impacts, and design inconsistencies to ensure database updates maintain higher code quality.

When do I need an automated checklist audit for my feature branch?▼

An automated checklist audit is needed for feature branches during pre-landing pull request reviews. It ensures production readiness by detecting hidden issues like SQL safety risks, race conditions, and incomplete enum handling that standard tests might miss.

Related Skills

Explore More Software Engineering Skills→
leighmccullochleighmcculloch
1

github-issue-from-wip

Generates a draft GitHub issue from the current branch's uncommitted changes.

Community
Intermediate
chrishuffman5chrishuffman5

upload-skill

Automate publishing skill folders to the main branch and trigger CI/CD deployment.

Community
Advanced
whilpwhilp

tests

Audit GitHub repository test suites for coverage gaps and fixes.

Community
Intermediate
stephanjstephanj
9

security-reviewer

Conducts security audits and vulnerability assessments on codebases and infrastructure.

Community
Advanced