Skip to content

docs: add Health Stack section to pin /health to the fast path#2312

Open
jaimedhenriques wants to merge 1 commit into
garrytan:mainfrom
jaimedhenriques:chore/gstack-health-stack
Open

docs: add Health Stack section to pin /health to the fast path#2312
jaimedhenriques wants to merge 1 commit into
garrytan:mainfrom
jaimedhenriques:chore/gstack-health-stack

Conversation

@jaimedhenriques

@jaimedhenriques jaimedhenriques commented Jul 21, 2026

Copy link
Copy Markdown

What

Adds a ## Health Stack section to CLAUDE.md so /health targets the real quality gates on this repo instead of auto-detecting tools that don't exist here.

Why

/health auto-detects tsconfig.json, biome/eslint, knip, and shellcheck — none of which gstack uses (Bun runs TypeScript directly; slop-scan is the linter). It also runs the full bun test script, which spawns browser integration tests that hang in non-interactive agent shells. The result is a dashboard that either scores nothing or times out.

The new section pins the fast deterministic test tier plus slop-scan, and notes that the full bun test still has to run in a real terminal before a PR.

- test: bun test test/skill-validation.test.ts test/gen-skill-docs.test.ts test/hermetic-wiring.test.ts
- lint: npx slop-scan scan .

Scope

Docs only. One file. No behavior change.

🤖 Generated with Claude Code

https://claude.ai/code/session_01BV2RsGpwAdbDid7yAHBtXK

Made with Orca 🐋

gstack has no tsconfig/biome/knip/shellcheck, and the full `bun test`
script spawns browser integration tests that hang in non-interactive
agent shells. Document the fast deterministic tier plus slop-scan so
/health completes and targets the real quality gates.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BV2RsGpwAdbDid7yAHBtXK

Co-authored-by: Orca <help@stably.ai>
@trunk-io

trunk-io Bot commented Jul 21, 2026

Copy link
Copy Markdown

Merging to main in this repository is managed by Trunk.

  • To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant