mirror of
https://github.com/garrytan/gstack.git
synced 2026-11-18 14:14:37 +01:00
Keep skill_prefix after updates, retire the ClawHub install route, and stop misreading cross-repo issue refs (GST-2967) (#4454)
Three small fixes: `skill_prefix=true` now survives updates when gbrain is installed, the OpenClaw docs stop sending people to stale ClawHub skills, and `gstack-issue-links` no longer reads other repositories' issue numbers as gstack issues. Why: each one misleads users or /ship today (wrong skill names after every update, April 2026 skill builds, wrong `Refs #N` lines in PR bodies). Nothing to do as a reader. Thanks @fliaron (#4413) and @exGeni (#4421) for the detailed reports. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
This commit is contained in:
1 parent
f2d96dcba1
commit
b1c32824fd
13 files changed
+166
-39
No files matched your search
+8
-9
@@ -101,15 +101,14 @@ The orchestrator persists the plan link to its own memory store (brain repo,
|
||||
knowledge base, or whatever is configured in AGENTS.md). When the user is
|
||||
ready to build, spawn a FULL session that references the saved plan.
|
||||
|
||||
### Native methodology skills
|
||||
Published to ClawHub. Install with `clawhub install`:
|
||||
- `gstack-openclaw-office-hours` — Product interrogation (6 forcing questions)
|
||||
- `gstack-openclaw-ceo-review` — Strategic challenge (10-section review, 4 modes)
|
||||
- `gstack-openclaw-retro` — Operational retrospective (weekly review)
|
||||
### Methodology skills in the OpenClaw agent
|
||||
To run /office-hours, /plan-ceo-review or /retro in the OpenClaw agent itself,
|
||||
use native registration (see [Installation](#installation)): its `gstack` router
|
||||
skill serves the current version of each.
|
||||
|
||||
Source lives in `openclaw/skills/` in the gstack repo. These are hand-crafted
|
||||
adaptations of the gstack methodology for OpenClaw's conversational context.
|
||||
No gstack infrastructure (no browser, no telemetry, no preamble).
|
||||
gstack no longer publishes skills on ClawHub. If you installed the April 2026
|
||||
`gstack-openclaw-office-hours`, `gstack-openclaw-ceo-review` or
|
||||
`gstack-openclaw-retro` from there, remove them.
|
||||
|
||||
## Spawned session detection
|
||||
|
||||
@@ -175,7 +174,7 @@ For OpenClaw users: tell your OpenClaw agent "install gstack for openclaw."
|
||||
|
||||
The agent should:
|
||||
1. Install gstack-lite CLAUDE.md into its coding session templates
|
||||
2. Install the 4 native methodology skills
|
||||
2. Register gstack's native skills with `./setup --host openclaw` (below)
|
||||
3. Add dispatch routing to AGENTS.md
|
||||
4. Verify with a test spawn
|
||||
|
||||
|
||||
@@ -2,6 +2,11 @@
|
||||
|
||||
Moved verbatim from CLAUDE.md (token-load reduction).
|
||||
|
||||
**Status:** gstack's user docs no longer send anyone to ClawHub (#4421). Native
|
||||
registration (`./setup --host openclaw`) gives OpenClaw's agent the current
|
||||
/office-hours, /plan-ceo-review and /retro, and the gstack skills were removed
|
||||
from ClawHub on 2026-11-17.
|
||||
|
||||
## Workflow
|
||||
|
||||
Native OpenClaw skills live in `openclaw/skills/gstack-openclaw-*/SKILL.md`. These are
|
||||
|
||||
+9
-14
@@ -117,22 +117,17 @@ when Claude Code has gstack installed. Paste this to your OpenClaw agent:
|
||||
See [docs/OPENCLAW.md](OPENCLAW.md) for advanced dispatch routing and
|
||||
the gstack-lite/gstack-full prompt templates.
|
||||
|
||||
## Native OpenClaw Skills (via ClawHub)
|
||||
## /office-hours, /plan-ceo-review and /retro in OpenClaw
|
||||
|
||||
Four methodology skills that work directly in your OpenClaw agent, no Claude Code
|
||||
session needed. Install from ClawHub:
|
||||
Your OpenClaw agent can run these directly in chat, with no Claude Code session.
|
||||
They come with native registration: `./setup --host openclaw` registers gstack's
|
||||
`gstack` router skill, which lists them with every other workflow and serves
|
||||
the current version of each ([install, verify and remove](#agent-harnesses)).
|
||||
|
||||
```
|
||||
clawhub install gstack-openclaw-office-hours gstack-openclaw-ceo-review gstack-openclaw-retro
|
||||
```
|
||||
|
||||
| Skill | What it does |
|
||||
|-------|-------------|
|
||||
| `gstack-openclaw-office-hours` | Product interrogation with 6 forcing questions |
|
||||
| `gstack-openclaw-ceo-review` | Strategic challenge with 4 scope modes |
|
||||
| `gstack-openclaw-retro` | Weekly engineering retrospective |
|
||||
|
||||
These are conversational skills. Your OpenClaw agent runs them directly via chat.
|
||||
Earlier docs sent you to ClawHub for `gstack-openclaw-office-hours`,
|
||||
`gstack-openclaw-ceo-review` and `gstack-openclaw-retro`. Those were April 2026
|
||||
builds, and gstack no longer publishes skills on ClawHub. If you installed them,
|
||||
remove them, so your agent doesn't load an old copy next to the current one.
|
||||
|
||||
## Which agents a checkout renders for
|
||||
|
||||
|
||||
@@ -2278,6 +2278,9 @@ cross-repo `owner/repo#N` are `Refs`. A parenthesised named reference,
|
||||
token that is not a closure, reference, filler or version word, is a
|
||||
cross-repo `Refs name#N`, never a same-repo Refs line or a promotion
|
||||
candidate; `(see #12)`, `(closing #12)` and `(#301)` stay bare refs.
|
||||
Several in one parenthesis, `(founderstar #837, harness-evals #393)`, are each
|
||||
their own name's reference. `owner/repo#N` naming this repository is its own
|
||||
issue, so a `Fixes garrytan/gstack#N` trailer closes it.
|
||||
Same-repo references are printed as
|
||||
promotion candidates (`reference #N ← <commit line> (promote: fix #N)` on
|
||||
stderr, `candidates` in `--json`): the owner's `fix #N` reply reruns with
|
||||
|
||||
Reference in new issue
Block a user