# Gstack Canary

> GStack canary method for staged release thinking, smoke gates, rollout checks, and rollback signals before or after deployment.

- Skill: `dirtytrii/gstack-canary` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add dirtytrii/gstack-canary`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dirtytrii/gstack-canary/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Dirtytrii (https://skillmd.com/u/dirtytrii)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/dirtytrii/gstack-canary

---


# GStack Canary Adapter

This is a Codex role-system adapter for Garry Tan's gstack `gstack-canary` method.

## When To Use

Use this when:

- a release needs staged validation;
- smoke gates or rollback signals are missing;
- architecture or ops needs release confidence;
- the user explicitly invokes `$gstack-canary`.

## Workflow

1. Keep the active role boundary. Do not expand scope just because this gstack method is useful.
2. Read the relevant repo/docs/evidence first when the task depends on current state.
3. Read `../gstack/references/methodology.md` if you need the shared method map, then use the section named `QA, Security, And Release Methods`.
4. Produce: canary scope, smoke checks, metrics/signals, rollback conditions, and go/no-go recommendation.
5. Return the result in the active role's normal format, including boundaries, validation, and unresolved decisions when applicable.

## Boundaries

- Treat upstream gstack as external methodology, not local-owned project state.
- Do not run upstream gstack runtime, telemetry, browser-cookie import, upgrade checks, or host routing injection automatically.
- Do not create or edit `CLAUDE.md`, `.claude/`, `.agents/`, or upstream routing files unless the user explicitly asks for upstream gstack installation work.
- Do not write files, commit, push, deploy, restart, migrate, clean, delete, or change production unless the active role prompt explicitly allows it.
- Preserve this repository's `QA` versus `测试` split: formal test cases/reports belong to `测试` and `$test-case-report-builder`.
- For remote production facts, prefer Hermes read-only verification before action.