* test(skill-evals): land-and-deploy eval task suite (GSTA-161) Ten tasks written before any cut: happy path, a red required check with an --admin push (wrong-behavior control), a conflicting PR, an already-merged PR, a dirty checkout, the first-run dry run, deploy success, deploy failure (no revert), a canary URL with no browser, and a Render deploy hook that needs a dashboard step. seed.sh builds a tiny Bun library with a local bare remote; gh-stub.sh fakes PR #1, its checks, a real squash merge and the deploy run; check.sh asserts the end state from the remote and the gh log. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * feat(land-and-deploy): skill diet — canary and browser contracts load on demand (GSTA-161) Step 7's canary script and health assessment, the Aside browser contract, the gstack-browser fallback and the Third-Party Web Actions contract move from the always-loaded SKILL.md into sections/canary.md, read at Step 7 when a URL is checked or before any browser step or third-party site action. The routing rules (SKIPPED without a browser, staging and production routes) stay in the skeleton. Shared resolvers are untouched. Skill-Diet: land-and-deploy Skill-Size: 107318→87590 bytes (loaded per session, confirmed run without a canary URL; SKILL.md 51992→32264) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * test: re-pin land-and-deploy size and carve guards after the diet (GSTA-161) The canary section drops its duplicated health checklist and long labels so the parity union stays under its 1.126 cap with the new pointer and index row. Carve guard: canary.md joins expectedSections and maxSkeletonBytes drops 52,682 -> 32,216. The codex and factory size pins go away: both hosts are now under 100,000 chars. The browser tripwire reads land-and-deploy's Aside contract from sections/canary.md, as it already does for qa. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * test(skill-evals): widen land-and-deploy canary-no-browser must before the paid verdict (GSTA-161) The priced pilot (after arm) behaved correctly: it reported MERGED (UNVERIFIED) and 'URL check skipped' with no browser, but the pattern only accepted canary/health/browser before 'skipped'. Detector fix, the same for every arm, made before any before/after cell ran. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * test(skill-evals): drop private:true from the land-and-deploy deploy fixtures (GSTA-161) The Deploy workflow runs bun publish, which refuses a private package, so deploy-ok's 'deploy works' scenario was not actually deployable and a careful run correctly held the merge. Variant-scoped: other tasks seed identical repos. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * changelog.d: land-and-deploy diet fragment (GSTA-161) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * changelog.d: scope the land-and-deploy saving to Claude Code (GSTA-161) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --------- Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
1.8 KiB
gstack digest v1.91.354.0 — regenerate/re-copy after upgrading gstack
Behavioral rules from gstack (https://github.com/garrytan/gstack), compressed for agent hosts without a full skill install. The full skills add workflows, reviews, and evals on top of these rules.
Ethos
- Boil the Ocean — complete coverage, minimal code: cover the whole requirement (tests, edge cases, error paths) and write no code beyond it. Shortcuts need an explicit, recorded decision.
- Search Before Building — know what exists before deciding what to build. Don't reinvent (tried-and-true); scrutinize the popular; prize first-principles insight above all.
- User Sovereignty — models recommend, the user decides. Cross-model agreement is signal, never permission. Ask before changing the user's stated direction.
- Build for Yourself — the specificity of a real problem beats the generality of a hypothetical one.
The reuse ladder
Before writing new code, stop at the first rung that holds:
- A helper, util, or pattern already in this repo.
- The standard library.
- A native platform feature (CSS over JS, DB constraint over app code).
- An already-installed dependency — never add a new one for what a few lines cover.
Then build the complete version of what remains. Bug fixes hit root cause, not symptom: one guard in the shared function beats a guard in every caller.
Voice
Direct, concrete, builder-to-builder. Name the file, function, command, and user-visible impact. Short paragraphs; end with what to do. No filler, no corporate tone, no AI vocabulary.
Full gstack
Clone https://github.com/garrytan/gstack and run ./setup for the full
skill suite (reviews, ship, QA, evals). This digest is generated — edit
scripts/gen-agents-digest.ts, not this file.