gstack-execution

Execute code review, debugging, security auditing, QA, and PR preparation workflows.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/MoxyWolfLLC/moxywolf-plugins --skill gstack-execution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-execution
Source: https://github.com/MoxyWolfLLC/moxywolf-plugins/tree/main/plugins/gstack-execution/skills/gstack-execution
Command: npx skills add https://github.com/MoxyWolfLLC/moxywolf-plugins --skill gstack-execution

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It speeds up the build-review-ship workflow by turning vague requests like “review my code” or “audit this for security” into structured execution with concrete findings and next actions.

Core Features & Use Cases

  • Code review with actionable checkpoints: Runs /gstack-review for structural review and merge-blocking style feedback.
  • Bug investigation with hypothesis testing: Uses /gstack-investigate to narrow root cause and guide fixes.
  • Security audit focused on real risk: Executes /gstack-cso with OWASP/STRIDE/supply-chain style scanning and severity classifications.
  • Test and browser QA with the user’s logged-in session: Provides /gstack-qa and /gstack-browse using Claude in Chrome when available.
  • Ship pipeline for PR creation: Orchestrates /gstack-ship to prepare PR-ready work (with optional gh CLI for automation).

Quick Start

Ask the skill to audit your repository for security issues and propose concrete remediation steps.

Frequently Asked Questions about gstack-execution

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

FAQPage Schema
How do I run a security audit on my repository and get actionable remediation steps?

A security audit scans your workspace using OWASP, STRIDE, and supply-chain methodologies to classify severity. It produces structured findings with concrete recommendations and next actions to fix identified vulnerabilities.

How do I debug and find the root cause of a bug in my codebase?

Debugging uses hypothesis testing to investigate bugs, systematically narrowing down the root cause. It analyzes your repository using git and grep, guiding you through targeted fixes based on structural code analysis.

Can I test my web application using my real logged-in Chrome session?

Yes, browser QA supports testing with your active logged-in Chrome session via Claude in Chrome, with a Playwright fallback. It enables workspace execution for validating application behavior within your authenticated environment.

What's the best way to prepare a pull request after completing code review and fixes?

The ship pipeline orchestrates PR-ready work preparation, optionally automating creation through the gh CLI. It follows structured code review and debugging to ensure merge-blocking style feedback is resolved before submission.

Does this code review tool provide merge-blocking feedback or just style suggestions?

Code review provides structural analysis with actionable checkpoints and merge-blocking style feedback. It evaluates your workspace repository to ensure code quality standards are met before merging changes.

Do I need the gh CLI installed to prepare pull requests for my repository?

The gh CLI is optional for PR automation. The ship pipeline prepares PR-ready work structurally, but installing gh enables automated pull request creation directly from your workspace execution environment.