skills.rest
tinner-deinno
tinner-deinnoCOMMUNITY
Explore all skills by this author →
GitHub

gsd-code-review

Review phase-scoped source changes and generate severity-classified REVIEW.md findings.

1|Updated May 24, 2026
Search Tags:#static analysis#code review#security scanning#bug detection#phase-based workflow#fix automation#severity reporting
One-click install
npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-code-review-tinner-deinno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-code-review
Source: https://github.com/tinner-deinno/innova-skills-lib/tree/main/core/gsd/gsd-code-review
Command: npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-code-review-tinner-deinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams catch bugs, security vulnerabilities, and code quality regressions by reviewing the source files changed during a specific phase of work.

Core Features & Use Cases

  • Phase-scoped code review: Review changes tied to a given phase, generating a structured report artifact in that phase directory.
  • Configurable review depth: Use quick, standard, or deep analysis to balance speed vs. thoroughness (pattern checks, per-file checks, or cross-file reasoning like call chains).
  • Actionable remediation support: Optionally apply fixes by spawning a fixer agent and (when enabled) automatically re-review up to a capped iteration count.

Quick Start

Run the command gsd-code-review for phase 2 with standard depth to generate phase-scoped REVIEW.md findings for the changes in that phase.

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 bugs and security vulnerabilities in changed files?▼

Automated code review for changed source files identifies bugs, security vulnerabilities, and code quality problems, then generates a severity-classified REVIEW.md artifact summarizing the findings. You can review changes tied to a specific work phase using configurable depth levels.

What's the best way to balance speed and thoroughness during static analysis?▼

Static analysis depth is configurable to balance speed versus thoroughness. You can select quick pattern matching, standard per-file checks, or deep cross-file analysis like call chain reasoning depending on the required risk-scoped assessment.

Can I automatically apply fixes and recheck code after security scanning?▼

Security scanning optionally coordinates an automated fix-and-recheck loop via a dedicated fixer workflow. When enabled, it applies fixes and automatically re-reviews the code up to a capped iteration count.

Does phase-based code review work without external dependencies?▼

Phase-based code review works without external dependencies. It reviews source files changed in a given phase internally, applying risk-scoped assessments to produce a structured report artifact directly in that phase directory.

Why use cross-file analysis instead of standard per-file checks for bug detection?▼

Cross-file analysis provides deeper bug detection by reasoning across call chains and file interactions, whereas standard per-file checks evaluate files independently. Deep analysis offers more thorough risk-scoped assessment for complex code changes.

Related Skills

Explore More Software Engineering Skills→
calcosmiccalcosmic
9

code-review

Identify defects and security risks in changed source files and generate REVIEW.md.

Community
Advanced
QunnnnQunnnn

dart-run-static-analysis

Run Dart static analysis and apply automated lint fixes.

Community
Intermediate
PantaniPantani
30

tdmcp-interactive-projection-mapping

Coordinate end-to-end development of interactive projection mapping with USB camera and projector.

Community
Advanced
baphledbaphled
1

static-analysis

Guide static code analysis tools to detect bugs, vulnerabilities, and style violations.

Community
Intermediate