gsd-code-review

Automate code review for bugs, security vulnerabilities, and quality issues.

Updated Apr 22, 2025
One-click install
npx skills add https://github.com/mcampbellr/.dotfiles --skill gsd-code-review-mcampbellr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-code-review
Source: https://github.com/mcampbellr/.dotfiles/tree/main/claude/.claude/skills/gsd-code-review
Command: npx skills add https://github.com/mcampbellr/.dotfiles --skill gsd-code-review-mcampbellr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The gsd-code-review Skill automates the process of reviewing source code for bugs, security vulnerabilities, and code quality problems, saving time and reducing human error.

Core Features & Use Cases

  • Automated Code Review: Analyze source files for issues during a development phase.
  • Depth Levels: Perform quick, standard, or deep code reviews based on the phase.
  • File Scoping: Review specific files or use default scoping based on git history.
  • Fixes and Re-Review: Automatically apply fixes and re-review code after changes.
  • Use Case: Streamline the code review process in a software development workflow, ensuring consistent quality and security.

Quick Start

Run a code review for phase 2 with a deep analysis on all files: gsd-code-review 2 --depth=deep

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 reviews for bugs and security vulnerabilities?

Automated code review analyzes source files to identify bugs, security vulnerabilities, and quality issues during development phases. It supports depth-level analysis and automatic fixes, streamlining the review process while reducing human error.

What's the best way to run a deep code review on specific source files?

Run a deep code review by specifying the development phase and depth level, such as using a depth parameter for deep analysis. You can scope the review to specific files or rely on default scoping based on git history.

Can I automatically apply fixes and re-review code after changes?

Automatic fixes can be applied during the code review process, and the tool supports re-reviewing code after changes are made. This ensures that applied fixes resolve the identified security and quality issues without introducing new errors.

Does automated code review support different levels of analysis depth?

Automated code review supports quick, standard, and deep analysis levels based on the current development phase. This allows you to balance review thoroughness against processing time depending on your workflow requirements.

Do I need workflow configuration to run automated source code analysis?

Workflow configuration and appropriate code analysis tools are required to run automated source code analysis. These prerequisites enable the system to properly scope files and execute reviews for the identified development phases.

Why use file scoping based on git history for code quality analysis?

File scoping based on git history focuses code quality analysis on recently modified source files. This default scoping method ensures the review targets relevant changes efficiently without manually specifying individual file paths.