RomanNum3ral
/
gstack
mirror of https://github.com/garrytan/gstack.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

chore(build): regenerate skill docs to current generator output 

📝 Summary:
• re-run `bun run gen:skill-docs` on unmodified templates and commit
  the drift — the working tree had stale generated output (blank-line
  churn) left uncommitted by an earlier regen
• 326 deletions across 10 SKILL.md + 6 sections files, whitespace and
  section-render drift only; no template changed in this commit

📊 Code Changes: 0 insertions, 326 deletions (net -326)
This commit is contained in:
Benjamin D. Smith 2026-07-18 14:06:50 +00:00
parent 2311e32d63
commit 5c37e4a933
16 changed files with 0 additions and 326 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
cso/SKILL.md
View File

@ -787,17 +787,7 @@ Replace `SKILL_NAME`, `OUTCOME`, and `USED_BROWSE` before running.
Skills that run plan reviews (`/plan-*-review`, `/codex review`) include the EXIT PLAN MODE GATE blocking checklist at the end of the skill, which verifies the plan file ends with `## GSTACK REVIEW REPORT` before ExitPlanMode is called. Skills that don't run plan reviews (operational skills like `/ship`, `/qa`, `/review`) typically don't operate in plan mode and have no review report to verify; this footer is a no-op for them. Writing the plan file is the one edit allowed in plan mode.
## Brain Context Load
**Skip this entire section if `gbrain` is not on PATH.**
Extract 2-4 keywords from the user's request. Search the brain:
`gbrain search "<keywords>"`. Read the top 3 results with
`gbrain get_page "<slug>"`. Use that context to inform your analysis.
If `gbrain search` returns no results or any non-zero exit, proceed
without brain context. Full search/read protocol + examples:
see `docs/gbrain-write-surfaces.md` §Context Load.
# /cso — Chief Security Officer Audit (v2)
@ -1270,28 +1260,7 @@ staleness detection: if those files are later deleted, the learning can be flagg
**Only log genuine discoveries.** Don't log obvious things. Don't log things the user
already knows. A good test: would this insight save time in a future session? If yes, log it.
## Save Results to Brain
**Skip this entire section if `gbrain` is not on PATH.**
After completing this skill, save the output:
```bash
gbrain put "security-audits/<feature-slug>" --content "$(cat <<'EOF'
---
title: "Security Audit: <feature name>"
tags: [security-audit, <feature-slug>]
---
<skill output in markdown>
EOF
)"
```
Then extract person/org entities and create stub pages for each one.
Throttle errors (exit 1 with "throttle"/"rate limit"/"busy") and any
other non-zero exit are transient — don't retry inline. Full entity-stub
template, throttle handling, and backlink protocol:
see `docs/gbrain-write-surfaces.md` §Save Template.
## Important Rules

31
design-consultation/SKILL.md
View File

@ -956,17 +956,7 @@ If `DESIGN_NOT_AVAILABLE`: Phase 5 falls back to the HTML preview page (still go
---
## Brain Context Load
**Skip this entire section if `gbrain` is not on PATH.**
Extract 2-4 keywords from the user's request. Search the brain:
`gbrain search "<keywords>"`. Read the top 3 results with
`gbrain get_page "<slug>"`. Use that context to inform your analysis.
If `gbrain search` returns no results or any non-zero exit, proceed
without brain context. Full search/read protocol + examples:
see `docs/gbrain-write-surfaces.md` §Context Load.
## Prior Learnings
@ -1229,28 +1219,7 @@ staleness detection: if those files are later deleted, the learning can be flagg
**Only log genuine discoveries.** Don't log obvious things. Don't log things the user
already knows. A good test: would this insight save time in a future session? If yes, log it.
## Save Results to Brain
**Skip this entire section if `gbrain` is not on PATH.**
After completing this skill, save the output:
```bash
gbrain put "design-systems/<feature-slug>" --content "$(cat <<'EOF'
---
title: "Design System: <feature name>"
tags: [design-system, <feature-slug>]
---
<skill output in markdown>
EOF
)"
```
Then extract person/org entities and create stub pages for each one.
Throttle errors (exit 1 with "throttle"/"rate limit"/"busy") and any
other non-zero exit are transient — don't retry inline. Full entity-stub
template, throttle handling, and backlink protocol:
see `docs/gbrain-write-surfaces.md` §Save Template.
## Important Rules

17
design-review/SKILL.md
View File

@ -803,17 +803,7 @@ Replace `SKILL_NAME`, `OUTCOME`, and `USED_BROWSE` before running.
Skills that run plan reviews (`/plan-*-review`, `/codex review`) include the EXIT PLAN MODE GATE blocking checklist at the end of the skill, which verifies the plan file ends with `## GSTACK REVIEW REPORT` before ExitPlanMode is called. Skills that don't run plan reviews (operational skills like `/ship`, `/qa`, `/review`) typically don't operate in plan mode and have no review report to verify; this footer is a no-op for them. Writing the plan file is the one edit allowed in plan mode.
## Brain Context Load
**Skip this entire section if `gbrain` is not on PATH.**
Extract 2-4 keywords from the user's request. Search the brain:
`gbrain search "<keywords>"`. Read the top 3 results with
`gbrain get_page "<slug>"`. Use that context to inform your analysis.
If `gbrain search` returns no results or any non-zero exit, proceed
without brain context. Full search/read protocol + examples:
see `docs/gbrain-write-surfaces.md` §Context Load.
# /design-review: Design Audit → Fix → Verify
@ -1994,14 +1984,7 @@ staleness detection: if those files are later deleted, the learning can be flagg
**Only log genuine discoveries.** Don't log obvious things. Don't log things the user
already knows. A good test: would this insight save time in a future session? If yes, log it.
## Save Results to Brain
**Skip this entire section if `gbrain` is not on PATH.**
If the skill output is worth preserving, save it via
`gbrain put "<slug>" --content "<frontmatter + markdown>"`. Full template
(heredoc body, frontmatter shape, entity-stub instructions, throttle
handling): see `docs/gbrain-write-surfaces.md` §Save Template.
## Additional Rules (design-review specific)

33
investigate/SKILL.md
View File

@ -832,19 +832,7 @@ Fixing symptoms creates whack-a-mole debugging. Every fix that doesn't address r
---
## Brain Context Load
**Skip this entire section if `gbrain` is not on PATH.**
Extract 2-4 keywords from the user's request. Search the brain:
`gbrain search "<keywords>"`. Read the top 3 results with
`gbrain get_page "<slug>"`. Use that context to inform your analysis.
If `gbrain search` returns no results or any non-zero exit, proceed
without brain context. Full search/read protocol + examples:
see `docs/gbrain-write-surfaces.md` §Context Load.
For structured-data extraction requests ("track this", "extract from emails", "build a tracker"), route to GBrain's data-research skill instead: `gbrain call data-research`.
## Phase 1: Root Cause Investigation
@ -1073,28 +1061,7 @@ staleness detection: if those files are later deleted, the learning can be flagg
**Only log genuine discoveries.** Don't log obvious things. Don't log things the user
already knows. A good test: would this insight save time in a future session? If yes, log it.
## Save Results to Brain
**Skip this entire section if `gbrain` is not on PATH.**
After completing this skill, save the output:
```bash
gbrain put "investigations/<feature-slug>" --content "$(cat <<'EOF'
---
title: "Investigation: <feature name>"
tags: [investigation, <feature-slug>]
---
<skill output in markdown>
EOF
)"
```
Then extract person/org entities and create stub pages for each one.
Throttle errors (exit 1 with "throttle"/"rate limit"/"busy") and any
other non-zero exit are transient — don't retry inline. Full entity-stub
template, throttle handling, and backlink protocol:
see `docs/gbrain-write-surfaces.md` §Save Template.
---

10
office-hours/SKILL.md
View File

@ -880,17 +880,7 @@ You are a **YC office hours partner**. Your job is to ensure the problem is unde
---
## Brain Context Load
**Skip this entire section if `gbrain` is not on PATH.**
Extract 2-4 keywords from the user's request. Search the brain:
`gbrain search "<keywords>"`. Read the top 3 results with
`gbrain get_page "<slug>"`. Use that context to inform your analysis.
If `gbrain search` returns no results or any non-zero exit, proceed
without brain context. Full search/read protocol + examples:
see `docs/gbrain-write-surfaces.md` §Context Load.
## Brain Context (preflight)

21
office-hours/sections/design-and-handoff.md
View File

@ -209,28 +209,7 @@ Present the reviewed design doc to the user via AskUserQuestion:
- B) Revise — specify which sections need changes (loop back to revise those sections)
- C) Start over — return to Phase 2
## Save Results to Brain
**Skip this entire section if `gbrain` is not on PATH.**
After completing this skill, save the output:
```bash
gbrain put "office-hours/<feature-slug>" --content "$(cat <<'EOF'
---
title: "Office Hours: <feature name>"
tags: [design-doc, <feature-slug>]
---
<skill output in markdown>
EOF
)"
```
Then extract person/org entities and create stub pages for each one.
Throttle errors (exit 1 with "throttle"/"rate limit"/"busy") and any
other non-zero exit are transient — don't retry inline. Full entity-stub
template, throttle handling, and backlink protocol:
see `docs/gbrain-write-surfaces.md` §Save Template.
## Brain Calibration Write-Back (Phase 2 / gated)

10
plan-ceo-review/SKILL.md
View File

@ -1143,17 +1143,7 @@ matches a past learning, display:
This makes the compounding visible. The user should see that gstack is getting
smarter on their codebase over time.
## Brain Context Load
**Skip this entire section if `gbrain` is not on PATH.**
Extract 2-4 keywords from the user's request. Search the brain:
`gbrain search "<keywords>"`. Read the top 3 results with
`gbrain get_page "<slug>"`. Use that context to inform your analysis.
If `gbrain search` returns no results or any non-zero exit, proceed
without brain context. Full search/read protocol + examples:
see `docs/gbrain-write-surfaces.md` §Context Load.
## Brain Context (preflight)

21
plan-ceo-review/sections/review-sections.md
View File

@ -828,28 +828,7 @@ staleness detection: if those files are later deleted, the learning can be flagg
**Only log genuine discoveries.** Don't log obvious things. Don't log things the user
already knows. A good test: would this insight save time in a future session? If yes, log it.
## Save Results to Brain
**Skip this entire section if `gbrain` is not on PATH.**
After completing this skill, save the output:
```bash
gbrain put "ceo-plans/<feature-slug>" --content "$(cat <<'EOF'
---
title: "CEO Plan: <feature name>"
tags: [ceo-plan, <feature-slug>]
---
<skill output in markdown>
EOF
)"
```
Then extract person/org entities and create stub pages for each one.
Throttle errors (exit 1 with "throttle"/"rate limit"/"busy") and any
other non-zero exit are transient — don't retry inline. Full entity-stub
template, throttle handling, and backlink protocol:
see `docs/gbrain-write-surfaces.md` §Save Template.
## Brain Calibration Write-Back (Phase 2 / gated)

21
plan-design-review/sections/review-sections.md
View File

@ -531,28 +531,7 @@ staleness detection: if those files are later deleted, the learning can be flagg
**Only log genuine discoveries.** Don't log obvious things. Don't log things the user
already knows. A good test: would this insight save time in a future session? If yes, log it.
## Save Results to Brain
**Skip this entire section if `gbrain` is not on PATH.**
After completing this skill, save the output:
```bash
gbrain put "design-reviews/<feature-slug>" --content "$(cat <<'EOF'
---
title: "Design Review: <feature name>"
tags: [design-review, <feature-slug>]
---
<skill output in markdown>
EOF
)"
```
Then extract person/org entities and create stub pages for each one.
Throttle errors (exit 1 with "throttle"/"rate limit"/"busy") and any
other non-zero exit are transient — don't retry inline. Full entity-stub
template, throttle handling, and backlink protocol:
see `docs/gbrain-write-surfaces.md` §Save Template.
## Brain Calibration Write-Back (Phase 2 / gated)

21
plan-devex-review/sections/review-sections.md
View File

@ -769,28 +769,7 @@ staleness detection: if those files are later deleted, the learning can be flagg
**Only log genuine discoveries.** Don't log obvious things. Don't log things the user
already knows. A good test: would this insight save time in a future session? If yes, log it.
## Save Results to Brain
**Skip this entire section if `gbrain` is not on PATH.**
After completing this skill, save the output:
```bash
gbrain put "devex-reviews/<feature-slug>" --content "$(cat <<'EOF'
---
title: "Devex Review: <feature name>"
tags: [devex-review, <feature-slug>]
---
<skill output in markdown>
EOF
)"
```
Then extract person/org entities and create stub pages for each one.
Throttle errors (exit 1 with "throttle"/"rate limit"/"busy") and any
other non-zero exit are transient — don't retry inline. Full entity-stub
template, throttle handling, and backlink protocol:
see `docs/gbrain-write-surfaces.md` §Save Template.
## Brain Calibration Write-Back (Phase 2 / gated)

10
plan-eng-review/SKILL.md
View File

@ -806,17 +806,7 @@ Replace `SKILL_NAME`, `OUTCOME`, and `USED_BROWSE` before running.
Skills that run plan reviews (`/plan-*-review`, `/codex review`) include the EXIT PLAN MODE GATE blocking checklist at the end of the skill, which verifies the plan file ends with `## GSTACK REVIEW REPORT` before ExitPlanMode is called. Skills that don't run plan reviews (operational skills like `/ship`, `/qa`, `/review`) typically don't operate in plan mode and have no review report to verify; this footer is a no-op for them. Writing the plan file is the one edit allowed in plan mode.
## Brain Context Load
**Skip this entire section if `gbrain` is not on PATH.**
Extract 2-4 keywords from the user's request. Search the brain:
`gbrain search "<keywords>"`. Read the top 3 results with
`gbrain get_page "<slug>"`. Use that context to inform your analysis.
If `gbrain search` returns no results or any non-zero exit, proceed
without brain context. Full search/read protocol + examples:
see `docs/gbrain-write-surfaces.md` §Context Load.
# Plan Review Mode

21
plan-eng-review/sections/review-sections.md
View File

@ -849,28 +849,7 @@ staleness detection: if those files are later deleted, the learning can be flagg
**Only log genuine discoveries.** Don't log obvious things. Don't log things the user
already knows. A good test: would this insight save time in a future session? If yes, log it.
## Save Results to Brain
**Skip this entire section if `gbrain` is not on PATH.**
After completing this skill, save the output:
```bash
gbrain put "eng-reviews/<feature-slug>" --content "$(cat <<'EOF'
---
title: "Eng Review: <feature name>"
tags: [eng-review, <feature-slug>]
---
<skill output in markdown>
EOF
)"
```
Then extract person/org entities and create stub pages for each one.
Throttle errors (exit 1 with "throttle"/"rate limit"/"busy") and any
other non-zero exit are transient — don't retry inline. Full entity-stub
template, throttle handling, and backlink protocol:
see `docs/gbrain-write-surfaces.md` §Save Template.
## Brain Calibration Write-Back (Phase 2 / gated)

17
qa/SKILL.md
View File

@ -846,17 +846,7 @@ branch name wherever the instructions say "the base branch" or `<default>`.
---
## Brain Context Load
**Skip this entire section if `gbrain` is not on PATH.**
Extract 2-4 keywords from the user's request. Search the brain:
`gbrain search "<keywords>"`. Read the top 3 results with
`gbrain get_page "<slug>"`. Use that context to inform your analysis.
If `gbrain search` returns no results or any non-zero exit, proceed
without brain context. Full search/read protocol + examples:
see `docs/gbrain-write-surfaces.md` §Context Load.
# /qa: Test → Fix → Verify
@ -1686,14 +1676,7 @@ staleness detection: if those files are later deleted, the learning can be flagg
**Only log genuine discoveries.** Don't log obvious things. Don't log things the user
already knows. A good test: would this insight save time in a future session? If yes, log it.
## Save Results to Brain
**Skip this entire section if `gbrain` is not on PATH.**
If the skill output is worth preserving, save it via
`gbrain put "<slug>" --content "<frontmatter + markdown>"`. Full template
(heredoc body, frontmatter shape, entity-stub instructions, throttle
handling): see `docs/gbrain-write-surfaces.md` §Save Template.
## Additional Rules (qa-specific)

31
retro/SKILL.md
View File

@ -856,17 +856,7 @@ When the user types `/retro`, run this skill.
- `/retro global` — cross-project retro across all AI coding tools (7d default)
- `/retro global 14d` — cross-project retro with explicit window
## Brain Context Load
**Skip this entire section if `gbrain` is not on PATH.**
Extract 2-4 keywords from the user's request. Search the brain:
`gbrain search "<keywords>"`. Read the top 3 results with
`gbrain get_page "<slug>"`. Use that context to inform your analysis.
If `gbrain search` returns no results or any non-zero exit, proceed
without brain context. Full search/read protocol + examples:
see `docs/gbrain-write-surfaces.md` §Context Load.
## Instructions
@ -1247,28 +1237,7 @@ staleness detection: if those files are later deleted, the learning can be flagg
**Only log genuine discoveries.** Don't log obvious things. Don't log things the user
already knows. A good test: would this insight save time in a future session? If yes, log it.
## Save Results to Brain
**Skip this entire section if `gbrain` is not on PATH.**
After completing this skill, save the output:
```bash
gbrain put "retros/<feature-slug>" --content "$(cat <<'EOF'
---
title: "Retro: <feature name>"
tags: [retro, <feature-slug>]
---
<skill output in markdown>
EOF
)"
```
Then extract person/org entities and create stub pages for each one.
Throttle errors (exit 1 with "throttle"/"rate limit"/"busy") and any
other non-zero exit are transient — don't retry inline. Full entity-stub
template, throttle handling, and backlink protocol:
see `docs/gbrain-write-surfaces.md` §Save Template.
### Step 10: Week-over-Week Trends (if window >= 14d)

10
ship/SKILL.md
View File

@ -842,17 +842,7 @@ branch name wherever the instructions say "the base branch" or `<default>`.
---
## Brain Context Load
**Skip this entire section if `gbrain` is not on PATH.**
Extract 2-4 keywords from the user's request. Search the brain:
`gbrain search "<keywords>"`. Read the top 3 results with
`gbrain get_page "<slug>"`. Use that context to inform your analysis.
If `gbrain search` returns no results or any non-zero exit, proceed
without brain context. Full search/read protocol + examples:
see `docs/gbrain-write-surfaces.md` §Context Load.
# Ship: Fully Automated Ship Workflow

21
ship/sections/adversarial.md
View File

@ -179,28 +179,7 @@ staleness detection: if those files are later deleted, the learning can be flagg
**Only log genuine discoveries.** Don't log obvious things. Don't log things the user
already knows. A good test: would this insight save time in a future session? If yes, log it.
## Save Results to Brain
**Skip this entire section if `gbrain` is not on PATH.**
After completing this skill, save the output:
```bash
gbrain put "releases/<feature-slug>" --content "$(cat <<'EOF'
---
title: "Release: <feature name>"
tags: [release, <feature-slug>]
---
<skill output in markdown>
EOF
)"
```
Then extract person/org entities and create stub pages for each one.
Throttle errors (exit 1 with "throttle"/"rate limit"/"busy") and any
other non-zero exit are transient — don't retry inline. Full entity-stub
template, throttle handling, and backlink protocol:
see `docs/gbrain-write-surfaces.md` §Save Template.
### Refresh learnings for the headline feature on this branch