gsd-code-review

Analyze source code changes for bugs, security vulnerabilities, and quality issues.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/nnexai/git-stacks --skill gsd-code-review-nnexai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-code-review
Source: https://github.com/nnexai/git-stacks/tree/main/.codex/skills/gsd-code-review
Command: npx skills add https://github.com/nnexai/git-stacks --skill gsd-code-review-nnexai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the tedious process of reviewing code changes for bugs, security vulnerabilities, and quality issues, ensuring consistent standards across development phases.

Core Features & Use Cases

  • Multi-Depth Analysis: Perform quick pattern matching, standard per-file analysis, or deep cross-file dependency and call-chain reviews.
  • Automated Remediation: Optionally trigger the code-fixer agent to auto-apply patches based on review findings.
  • Use Case: Use this during a feature development phase to catch security flaws or architectural regressions before merging, significantly reducing manual review overhead.

Quick Start

Invoke the gsd-code-review skill for phase 2 with standard depth to identify potential bugs and quality issues in your current changes.

Frequently Asked Questions about gsd-code-review

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

FAQPage Schema
How do I automate code review for security vulnerabilities and bugs?

Automated code review analyzes source code changes to detect security vulnerabilities, bugs, and quality issues across defined development phases. It supports configurable review depths and integrates with remediation agents to iteratively apply patches.

What is cross-file call chain analysis in static code review?

Cross-file call chain analysis is a deep static review technique that traces dependencies and invocations across multiple source files. It identifies architectural regressions and complex security flaws that standard per-file pattern matching might miss.

Can I use automated remediation to auto-fix code review findings?

Automated remediation can be triggered to auto-apply patches based on code review findings. The code-fixer agent iteratively resolves identified bugs and security vulnerabilities through automated fix-and-review loops.

What is the best way to perform static analysis before merging code changes?

Performing multi-depth static analysis before merging catches security flaws and quality regressions early. You can configure the review depth from quick pattern matching to deep cross-file dependency analysis based on your phase requirements.

Does multi-depth code review support quick pattern matching for fast checks?

Multi-depth code review supports quick pattern matching for fast checks. This configurable depth ranges from rapid pattern identification to standard per-file analysis and deep cross-file dependency reviews.