Repository navigation
fix: add codex skill metadata for gstack discovery - #339
Merged
garrytan merged 1 commit intoMar 23, 2026
Merged
Conversation
Contributor
Author
|
@garrytan verified on March 22, 2026. This PR is intentionally limited to Codex discovery metadata:
On my machine, this was the difference between seeing only a partial |
4 tasks done
garrytan
added a commit
that referenced
this pull request
Mar 23, 2026
…tted PR #339 force-added agents/openai.yaml files to git despite .agents/ being in .gitignore. This created a split state: git pull brings yaml files but not SKILL.md files (gitignored), so Codex sees metadata but no actual skill content. All .agents/ content must be generated by `gen:skill-docs --host codex` during setup, not committed.
garrytan
pushed a commit
that referenced
this pull request
Mar 26, 2026
rapidstartup
pushed a commit
to rapidstartup/gstack
that referenced
this pull request
Mar 29, 2026
24601
pushed a commit
to 24601/gastack
that referenced
this pull request
Mar 29, 2026
…tted PR garrytan#339 force-added agents/openai.yaml files to git despite .agents/ being in .gitignore. This created a split state: git pull brings yaml files but not SKILL.md files (gitignored), so Codex sees metadata but no actual skill content. All .agents/ content must be generated by `gen:skill-docs --host codex` during setup, not committed.
mathiasmora2232
pushed a commit
to mathiasmora2232/gstack
that referenced
this pull request
May 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
agents/openai.yamlmetadata for every generated Codex skillagents/openai.yamlbundle metadata file forgstackProblem
On this machine, the Codex
$picker only surfacedgstack-upgradereliably even though allgstack-*skill symlinks existed under~/.codex/skills/.The missing piece was Codex metadata:
gstackbundle had noagents/openai.yaml.agents/skills/gstack-*Codex skills also had noagents/openai.yamlFix
agents/openai.yamlfor each generated Codex skill using thegstack-*display nameagents/openai.yamlsogstackitself is exposed as a bundleagents/openai.yamlwhen presentRelated to #333.
Verification
bun run gen:skill-docs --host codexbun test test/gen-skill-docs.test.ts test/codex-e2e.test.tsbun test./setup --host codexcodex execprobe after setup:gstack-*set was incomplete in the picker symptom reported by the usercodex execlists:gstack, gstack-autoplan, gstack-benchmark, gstack-browse, gstack-canary, gstack-careful, gstack-cso, gstack-design-consultation, gstack-design-review, gstack-document-release, gstack-freeze, gstack-guard, gstack-investigate, gstack-land-and-deploy, gstack-office-hours, gstack-plan-ceo-review, gstack-plan-design-review, gstack-plan-eng-review, gstack-qa, gstack-qa-only, gstack-retro, gstack-review, gstack-setup-browser-cookies, gstack-setup-deploy, gstack-ship, gstack-unfreeze, gstack-upgrade