skills.rest
Himanshu-Sangshetti
Himanshu-SangshettiCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Identify production-potential bugs in code changes during pre-merge reviews.

6|1|Updated Mar 14, 2026
Search Tags:#static-analysis#quality-assurance#code-review#pull-request#pre-merge#production-bugs
One-click install
npx skills add https://github.com/Himanshu-Sangshetti/cursor-stack --skill code-review-himanshu-sangshetti
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Himanshu-Sangshetti/cursor-stack/tree/main/code-review
Command: npx skills add https://github.com/Himanshu-Sangshetti/cursor-stack --skill code-review-himanshu-sangshetti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify bugs that pass automated tests but fail in production by enforcing paranoid code review mindset and checklists before merging changes.

Core Features & Use Cases

  • Bug detection: surface hidden issues such as race conditions, data integrity gaps, and potential security concerns that slip through CI.
  • Pre-merge guardrails: enforce a thorough review checklist to catch high-risk changes.
  • Team alignment: standardize rigorous review practices across engineering teams.

Quick Start

Run the paranoid code-review routine on a new pull request to surface bugs that could break in production.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I catch race conditions and security bugs that pass automated tests before merging a pull request?▼

To catch race conditions and security bugs that pass automated tests, use a paranoid code review checklist with static analysis signals during pre-merge reviews to surface hidden production-potential issues.

What is the best way to enforce a standardized pre-merge code review checklist across diverse engineering teams?▼

The best way to enforce a standardized pre-merge code review checklist is to apply a structured routine across pull requests, utilizing static analysis signals and prioritized issue reporting to align engineering teams.

How do I identify potential production bugs in code changes across diverse codebases and stacks?▼

To identify potential production bugs across diverse stacks, apply a paranoid code review routine with static analysis signals and a structured checklist to surface data integrity gaps and high-risk changes before merging.

Does static analysis alone catch data integrity gaps and production-potential bugs in pull requests?▼

Static analysis alone does not catch all data integrity gaps and production-potential bugs in pull requests; it must be combined with a paranoid code review mindset and a structured checklist to identify high-risk changes effectively.

Why do hidden production bugs slip through CI pipelines, and how can I prevent them?▼

Hidden production bugs slip through CI pipelines because automated tests miss race conditions and data integrity gaps; prevent them by enforcing paranoid pre-merge code reviews with static analysis signals and prioritized issue reporting.

Can I use a paranoid code review routine to surface data integrity gaps in high-risk changes before merging?▼

Yes, you can use a paranoid code review routine to surface data integrity gaps in high-risk changes before merging by enforcing a thorough review checklist and analyzing static analysis signals across diverse codebases.

Related Skills

Explore More Software Engineering Skills→
ohyesgocoolohyesgocool

mr-review

Orchestrate independent AI model code reviews on GitLab or GitHub merge requests.

Community
Advanced
ZaxbyHubZaxbyHub
437

swarm-pr-review

Review pull requests with multi-lane validation and critic challenge.

Official
Advanced
its-Basudebaits-Basudeba
1

laravel-verification

Automate Laravel environment validation, static analysis, and deployment readiness checks.

Community
Advanced
SantiagoisperSantiagoisper

canary

Monitor deployed applications by comparing periodic screenshots against pre-deployed baselines.

Community
Intermediate