Gstack Orchestrate
PassAudited by ClawScan on May 7, 2026.
Overview
Gstack Orchestrate is a disclosed, purpose-aligned developer workflow skill that can run git/shell subagents and modify a repository, so it should be used carefully on code you intend to change.
Before installing or invoking this skill, make sure you trust the gstack ecosystem components it composes with, run it only in a clean git repository on a branch you are willing to modify, approve the task breakdown deliberately, and review the resulting commits and local ~/.gstack state if the project is sensitive.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If used, the skill can run parallel coding agents and change the current repository branch.
This shows the skill can delegate code work to subagents and apply their commits to the user's branch. That is powerful but matches the stated orchestration purpose and is described as approval-gated.
Dispatches each task as an `Agent` subagent with `isolation: "worktree"` ... Cherry-picks each successful task's commit onto your working branch in dependency order
Use it only on a clean, non-critical branch; review the task decomposition, generated commits, and test results before allowing review/ship steps to proceed.
Actual behavior also depends on locally installed gstack and superpowers components.
The skill depends on external tools and other skills that are not included in this artifact review. This is disclosed and expected for the workflow, but users should trust those dependencies too.
"requires": { "tools": ["jq", "git"], "siblingSkills": ["gstack/review", "gstack/ship"], "subSkills": ["superpowers:using-git-worktrees", "superpowers:dispatching-parallel-agents"] }Install the related skills and helper tools only from trusted sources, and review them separately if the repository or deployment path is sensitive.
Run history and task outputs may remain on disk after the orchestration finishes.
The skill stores persistent local orchestration state and subagent results, which may include repository names, branch names, task details, and implementation context.
Shared state directory: `~/.gstack/projects/<slug>/orchestrate/<branch-safe>/` holds `TASKS.md`, `env.sh`, `state.jsonl`, `results/<TASK_ID>.json`.
Review or clean ~/.gstack for sensitive projects, and keep telemetry disabled unless you intentionally want usage metrics recorded.