gs:codex
OpenAI Codex CLI wrapper — three modes. (gstack)
thanh-abaii · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add thanh-abaii/gstack-windows-port --skill gs:codex技能说明
name: gs:codex preamble-tier: 3 version: 1.0.0 description: OpenAI Codex CLI wrapper — three modes. (gstack) triggers:
- codex review
- second opinion
- outside voice challenge allowed-tools:
- Bash
- Read
- Write
- Glob
- Grep
- AskUserQuestion
Preamble (run first)
python "bin/gstack-boot.py" --skill codex | iex
If PROACTIVE is "false", do not proactively suggest gstack skills AND do not
auto-invoke skills based on conversation context. Only run skills the user explicitly
types (e.g., /gs:qa, /gs:ship). If you would have auto-invoked a skill, instead briefly say:
"I think /skillname might help here — want me to run it?" and wait for confirmation.
The user opted out of proactive behavior.
If SKILL_PREFIX is "true", the user has namespaced skill names. When suggesting
or invoking other gstack skills, use the /gstack- prefix (e.g., /gstack-qa instead
of /qa, /gstack-ship instead of /ship). Disk paths are unaffected — always use
$GSTACK_ROOT/[skill-name]/SKILL.md for reading skill files.
If output shows UPGRADE_AVAILABLE <old> <new>: read $GSTACK_ROOT/gstack-upgrade/SKILL.md and follow the "Inline upgrade flow" (auto-upgrade if configured, otherwise AskUserQuestion with 4 options, write snooze state if declined). If JUST_UPGRADED <from> <to>: tell user "Running gstack v{to} (just updated!)" and continue.
If WRITING_STYLE_PENDING is yes: You're on the first skill run after upgrading
to gstack v1. Ask the user once about the new default writing style. Use AskUserQuestion:
v1 prompts = simpler. Technical terms get a one-sentence gloss on first use, questions are framed in outcome terms, sentences are shorter.
Keep the new default, or prefer the older tighter prose?
Options:
- A) Keep the new default (recommended — good writing helps everyone)
- B) Restore V0 prose — set
explain_level: terse
If A: leave explain_level unset (defaults to default).
If B: run $GSTACK_BIN/gstack-config set explain_level terse.
Always run (regardless of choice):
Remove-Item -Force ~/.gstack/.writing-style-prompt-pending
New-Item -ItemType File -Force ~/.gstack/.writing-style-prompted | Out-Null
This only happens once. If WRITING_STYLE_PENDING is no, skip this entirely.
If LAKE_INTRO is no: Before continuing, introduce the Completeness Principle.
Tell the user: "gstack follows the Boil the Lake principle — always do the complete
thing when AI makes the marginal cost near-zero. Read more: https://garryslist.org/posts/boil-the-ocean"
Then offer to open the essay in their default browser:
Start-Process https://garryslist.org/posts/boil-the-ocean
New-Item -ItemType File -Force ~/.gstack/.completeness-intro-seen | Out-Null
Only run open if the user says yes. Always run touch/New-Item to mark as seen. This only happens once.
If TEL_PROMPTED is no AND LAKE_INTRO is yes: After the lake intro is handled,
ask the user about telemetry. Use AskUserQuestion:
Help gstack get better! Community mode shares usage data (which skills you use, how long they take, crash info) with a stable device ID so we can track trends and fix bugs faster. No code, file paths, or repo names are ever sent. Change anytime with
gstack-config set telemetry off.
Options:
- A) Help gstack get better! (recommended)
- B) No thanks
If A: run $GSTACK_BIN/gstack-config set telemetry community
If B: ask a follow-up AskUserQuestion:
How about anonymous mode? We just learn that someone used gstack — no unique ID, no way to connect sessions. Just a counter that helps us know if anyone's out there.
Options:
- A) Sure, anonymous is fine
- B) No thanks, fully off
If B→A: run $GSTACK_BIN/gstack-config set telemetry anonymous
If B→B: run $GSTACK_BIN/gstack-config set telemetry off
Always run:
New-Item -ItemType File -Force ~/.gstack/.telemetry-prompted | Out-Null
This only happens once. If TEL_PROMPTED is yes, skip this entirely.
If PROACTIVE_PROMPTED is no AND TEL_PROMPTED is yes: After telemetry is handled,
ask the user about proactive behavior. Use AskUserQuestion:
gstack can proactively figure out when you might need a skill while you work — like suggesting /gs:qa when you say "does this work?" or /gs:investigate when you hit a bug. We recommend keeping this on — it speeds up every part of your workflow.
Options:
- A) Keep it on (recommended)
- B) Turn it off — I'll type /commands myself
If A: run $GSTACK_BIN/gstack-config set proactive true
If B: run $GSTACK_BIN/gstack-config set proactive false
Always run:
New-Item -ItemType File -Force ~/.gstack/.proactive-prompted | Out-Null
This only happens once. If PROACTIVE_PROMPTED is yes, skip this entirely.
If HAS_ROUTING is no AND ROUTING_DECLINED is false AND PROACTIVE_PROMPTED is yes:
Check if a CLAUDE.md file exists in the project root. If it does not exist, create it.
Use AskUserQuestion:
gstack works best when your project's CLAUDE.md includes skill routing rules. This tells Claude to use specialized workflows (like /gs:ship, /gs:investigate, /gs:qa) instead of answering directly. It's a one-time addition, about 15 lines.
Options:
- A) Add routing rules to CLAUDE.md (recommended)
- B) No thanks, I'll invoke skills manually
If A: Append this section to the end of CLAUDE.md:
## Skill routing
When the user's request matches an available skill, ALWAYS invoke it using the Skill
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
The skill has specialized workflows that produce better results than ad-hoc answers.
Key routing rules:
- Product ideas, "is this worth building", brainstorming → invoke gs:office-hours
- Bugs, errors, "why is this broken", 500 errors → invoke gs:investigate
- Shi
阅读完整来源 ↗