← gstack WorkflowsCONTENT HISTORY

Update to gstack Workflows

Snapshot Sep 30, 2026 · 23:14 UTC · version 0.1.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "review",
  "description": "Review a change before landing and find defects that can pass CI but fail in production.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 271
    }
  ],
  "skill_md_contents": "---\nname: review\ndescription: Review a change before landing and find defects that can pass CI but fail in production.\n---\n\n# Review\n\nPortable ChatGPT/Codex adaptation of the `review` workflow from `garrytan/gstack`. Preserve the original job and safety intent while mapping execution to capabilities the current host actually exposes.\n\n## When to use\n\nUse this Skill when the user explicitly names `review` or asks for the same job described above.\n\n## Host contract\n\n- Inspect repository or file evidence before making claims about the current state.\n- Use host-native read, list, search, grep, patch, write, shell, browser, computer, and Python capabilities only when they actually exist.\n- Never claim commands, tests, browser actions, device actions, file writes, Git operations, or external mutations that were not executed.\n- Prefer read-only discovery before mutation.\n- Respect repository instructions and preserve unrelated work.\n- When the original native gstack runtime is available in Codex, it may be used as an implementation detail after inspecting the installed upstream Skill. Do not hard-code Claude-only paths as a requirement.\n\n## Workflow\n\n1. Read the change, diff, plan, or code in scope.\n2. Trace affected paths and identify behavior changes and blast radius.\n3. Validate suspected findings against code, tests, contracts, and runtime evidence when available.\n4. Report only actionable findings with severity, location, evidence, and consequence.\n5. Separate confirmed defects from open questions.\n6. Do not modify reviewed code unless the user separately asks for fixes.\n\n## Completion\n\nReturn the decision, findings, changed artifacts if any, executed verification, skipped checks, and remaining blockers.\n"
}

SHA-256: 8a2d9e8e30db3709fec19de80af247e051b4157a22f92c9a83ba3458968b6e86