82fb847754
* chore: wire docs/agents config into AGENTS.md Agent skills section
Add the `## Agent skills` discovery block pointing the engineering
skills at the existing docs/agents/{issue-tracker,triage-labels,domain}.md
files (issue tracker, triage label mapping, single-context domain docs).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* fix(#214): make gsd-phase-researcher survive OpenCode write-tool truncation
OpenCode caps model output at OUTPUT_TOKEN_MAX=32000 and the thinking
budget shares that pool (upstream opencode#18108). A single oversized
`write` tool call for RESEARCH.md is truncated mid-payload, yielding
`JSON Parse error: Expected '}'`, which OpenCode misclassifies and then
doom-loops retrying identically. Short content writes fine; long
content fails 100% (reproducible, OpenCode 1.15.10).
Add a Step 6 write contract to agents/gsd-phase-researcher.md: keep the
single-Write default (no behavior change for Claude Code and other
runtimes that don't truncate), but on a truncation/invalid-tool failure
build the file incrementally via a sentinel-based Write -> Read -> Edit
sequence so no single tool-call payload is large enough to truncate;
never silently fall back to returning content (which truncates
identically). This is the upstream-recommended mitigation (write in
smaller chunks; use edit for follow-on writes).
Locked with a prompt-contract regression test mirroring the bug-222
write-contract pattern.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* chore(#214): add changeset for OpenCode write-truncation fix
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
3.6 KiB
Repository Guidelines
Active Discussions
For current work on Grok Build compatibility and multi-runtime synchronization across Grok Build, Claude Code, Gemini CLI, and Codex, see:
docs/discussions/grok-build-support-2026-05.md
Project Structure & Module Organization
This repository ships GSD as a Node.js CLI and SDK. Root package entry points live in bin/, scripts in scripts/, runtime hooks in hooks/, command definitions in commands/gsd/, and workflow/template content in get-shit-done/. Agent role files are in agents/; docs are in docs/; logos and terminal images are in assets/. Root tests are in tests/*.test.cjs. The TypeScript SDK is isolated under sdk/, with source and Vitest tests in sdk/src/.
Build, Test, and Development Commands
Use Node.js >=22.
npm install: install root dependencies.npm test: builds the SDK first, then runs rootnode:testsuites viascripts/run-tests.cjs.npm run test:coverage: runs root tests withc8and enforces 70% line coverage for included CommonJS library files.npm run build:hooks: rebuilds generated hook artifacts.npm run build:sdk: installs SDK dependencies and builds TypeScript.cd sdk && npm test: runs SDK Vitest unit and integration projects.cd sdk && npm run build: type-checks and emitssdk/dist/.
Coding Style & Naming Conventions
Match the existing style in the edited area. Root JavaScript is CommonJS, generally strict-mode, two-space indentation, semicolons, const/let, and node: imports for built-ins. SDK code is strict TypeScript using ESM/NodeNext. Keep command, workflow, and test filenames kebab-case, for example commands/gsd/plan-phase.md and tests/bug-2396-makefile-test-priority.test.cjs. Agent files use gsd-*.md. Avoid unrelated formatting and unnecessary dependencies.
Testing Guidelines
Root tests use Node’s built-in node:test and node:assert/strict; do not add Jest, Mocha, or Chai. Prefer helpers from tests/helpers.cjs for temporary projects, cleanup, and CLI execution. Name root tests *.test.cjs; run one with node --test tests/name.test.cjs. SDK tests use Vitest with *.test.ts for unit tests and *.integration.test.ts for integration tests.
Commit & Pull Request Guidelines
Recent history follows Conventional Commit prefixes such as fix:, feat:, and ci:, often with issue references: fix(#2623): resolve parent .planning root.... Keep commits scoped and descriptive.
Every PR must link an approved or confirmed issue with Closes #123, Fixes #123, or Resolves #123. Use the matching template in .github/PULL_REQUEST_TEMPLATE/. Include behavior changes, root cause when relevant, test evidence, affected platforms/runtimes, and update CHANGELOG.md or docs for user-facing changes.
Security & Configuration Tips
Do not commit secrets, local config, or generated worktree artifacts. Before release-facing changes, run the relevant scan scripts in scripts/, especially secret-scan.sh, base64-scan.sh, and prompt-injection-scan.sh.
Agent skills
Issue tracker
Issues live in GitHub Issues at open-gsd/gsd-core (via the gh CLI, always with --repo open-gsd/gsd-core). See docs/agents/issue-tracker.md.
Triage labels
Five canonical triage roles mapped to this repo's labels — needs-info→needs-reproduction, ready-for-agent→confirmed, ready-for-human→approved-enhancement/approved-feature, others default. See docs/agents/triage-labels.md.
Domain docs
Single-context — CONTEXT.md (domain glossary + recurring PR rules) and docs/adr/ at the repo root. See docs/agents/domain.md.