---
name: Gstack Review
slug: gstack-review
category: Quality
description: Gstack Review performs a pre-merge review of the current diff to catch regressions, security issues, missing tests, and cleanup problems. Use it before shipping or asking whether a change is safe.
github: "https://github.com/LING71671/Open-ClaudeCode/tree/main/plugins/gstack-workflows/skills/gstack-review"
language: TypeScript
stars: 945
forks: 1224
install: "npx degit https://github.com/LING71671/Open-ClaudeCode/tree/main/plugins/gstack-workflows/skills/gstack-review ~/.claude/skills/gstack-review"
installs_to: ~/.claude/skills/gstack-review
source_path: plugins/gstack-workflows/skills/gstack-review/SKILL.md
collection_size: 15
category_size: 1354
collection_url: "https://dirskills.com/collections/LING71671/Open-ClaudeCode"
added: 2026-08-21T05:15:32.088Z
last_synced: 2026-08-21T05:15:32.088Z
canonical_url: "https://dirskills.com/skills/gstack-review"
---

# Gstack Review

Gstack Review performs a pre-merge review of the current diff to catch regressions, security issues, missing tests, and cleanup problems. Use it before shipping or asking whether a change is safe.

**Install:**

```bash
npx degit https://github.com/LING71671/Open-ClaudeCode/tree/main/plugins/gstack-workflows/skills/gstack-review ~/.claude/skills/gstack-review
```

## README

# gstack-review

Use this skill as a staff-engineer review pass over the current diff.

## Workflow

1. Inspect repository state with `git status --short`.
2. Identify the base diff with `git diff --stat` and the focused changed files.
3. Read the changed code and its immediate callers.
4. Look for behavioral regressions, security boundaries, error handling gaps, state persistence bugs, and missing tests.
5. Run or identify the narrowest verification command that matches the changed surface.

## Review Priorities

- Correctness and edge cases
- Security and trust boundaries
- Data loss, persistence, and migration risks
- Long-running process handling and cleanup
- Provider/protocol compatibility
- Test coverage proportional to risk
- Docs or README drift when user-facing behavior changed

## Output

Lead with findings, ordered by severity. For each finding include:

- File and line when available
- Impact
- Why it can happen
- Suggested fix

If no issues are found, say that clearly and list remaining test gaps or residual risk.