From a5f106e966ef54c371d5721b70dd98bda24e9d2a Mon Sep 17 00:00:00 2001 From: garrytan Date: Mon, 26 Oct 2026 22:55:05 +0000 Subject: [PATCH] docs: name the Blast radius section in the two Capy body-order lists The docs re-audit found capy/skill/gstack/SKILL.md (Merge asks) and docs/capy-install.md still listing the Capy PR body as What changed, Why, Approvals; both now match capy-pr.md.tmpl. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- capy/skill/gstack/SKILL.md | 2 +- docs/capy-install.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/capy/skill/gstack/SKILL.md b/capy/skill/gstack/SKILL.md index f30982f41..bbde9e51b 100644 --- a/capy/skill/gstack/SKILL.md +++ b/capy/skill/gstack/SKILL.md @@ -49,7 +49,7 @@ When you work for a Capy Captain (a crew thread) or straight for a person, gstac - **These always need a fresh ask:** a product or behaviour decision, spend over a stated cap, anything published outside the repository, a change to a threshold, budget or trial count, closing someone's contribution without landing it, and anything destructive. - **Record every answer.** Use `gstack-approvals add --ask … --words "" --by … --scope …`, or after an autoplan answer, `gstack-approvals import --autoplan --by `. `gstack-approvals render` prints the `## Approvals` table for your report and the PR body. Rows are secret-scanned, and on Capy they are mirrored to the private Drive folder. - **Plan approvals** use `gstack-owner-brief render --captain --out `. It prints before → after, why it matters, what caused this work, the big decisions (options, the pick, why, what would flip it) and what we need, with `rec` as the recommended one-word reply. Relay it whole. Gate codes appear only on its last line, which is for you. If it exits `CAPTAIN_BRIEF_INCOMPLETE`, add the missing plan sections first. -- **Merge asks.** /ship's PR body opens with `## What changed` (captioned before/after images from `gstack-pr-shots` or a UI screenshot, uploaded with Capy's PR asset tool), `## Why` and `## Approvals`. Your READY report attaches the key image. +- **Merge asks.** /ship's PR body opens with `## What changed` (captioned before/after images from `gstack-pr-shots` or a UI screenshot, uploaded with Capy's PR asset tool), `## Why`, `## Blast radius` and `## Approvals`. Your READY report attaches the key image. ## Before any push or pull request diff --git a/docs/capy-install.md b/docs/capy-install.md index 648367962..ae37a01fc 100644 --- a/docs/capy-install.md +++ b/docs/capy-install.md @@ -436,7 +436,7 @@ prints `CAPY: on` and a `capy-asks` block: decisions go through Capy (a crew thread asks its Captain, otherwise the person), plan approvals are rendered with `gstack-owner-brief render --captain`, answers are recorded with `gstack-approvals`, and /ship's PR body opens with before/after images -(`gstack-pr-shots`), Why and Approvals. The guide is +(`gstack-pr-shots`), Why, Blast radius and Approvals. The guide is [`capy/skill/gstack/captain.md`](../capy/skill/gstack/captain.md); `GSTACK_CAPY_ASKS=0` drops the block for one session. The controller's side (the READY contract, merge trains, the digest, the daily flaky pass, with templates for the