19efcddfc7
* test(#941): regression test for managed-hooks-registry.cjs manifest omission Adds bug-941-managed-hooks-registry-manifest.test.cjs which verifies: - managed-hooks-registry.cjs appears in gsd-file-manifest.json after install - manifest covers the full HOOKS_TO_COPY set (forward-proof) - detect-custom-files reports 0 custom files after a clean install - manifest hook keys use forward slashes (cross-platform) All four assertions fail before the fix, confirming the bug is reproducible. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(#941): track managed-hooks-registry.cjs in file manifest The writeManifest() hooks loop in bin/install.js filtered hook filenames with `file.startsWith('gsd-') && (file.endsWith('.js') || file.endsWith('.sh'))`. managed-hooks-registry.cjs fails both predicates (wrong prefix, .cjs extension), so it was never recorded in gsd-file-manifest.json even though it is shipped to users as part of HOOKS_TO_COPY. detect-custom-files scans the installed hooks/ dir and reports any file with no manifest entry as a custom file, producing a perpetual false-positive "Found 1 custom file(s)" warning on every /gsd-update for all users. Fix: import HOOKS_TO_COPY from scripts/build-hooks.js and drive the manifest hooks loop from that set (as a Set for O(1) lookup), so the manifest set is structurally identical to the build set. Any future hook of any prefix or extension added to HOOKS_TO_COPY is automatically covered. The new regression test asserts full HOOKS_TO_COPY coverage and zero detect-custom-files false-positives after a clean install. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * chore(#941): add changeset for managed-hooks-registry.cjs manifest fix Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * test(#941): assert manifest hash matches installed hook contents (adversarial review) Strengthen the regression test to not only verify that the manifest KEY `hooks/managed-hooks-registry.cjs` is present after install, but also that the stored hash equals the SHA256 of the actual installed file bytes — the same algorithm used by the installer's fileHash() function. A future refactor that records the right key from the wrong path or content would now fail this assertion immediately. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
GSD Core
Git. Ship. Done.
English · Português · 简体中文 · 日本語 · 한국어
A light-weight meta-prompting, context engineering, and spec-driven development system for Claude Code, OpenCode, Gemini CLI, Kimi CLI, Kilo, Codex, Copilot, Cursor, Windsurf, and more.
What is GSD Core
GSD Core is a context-engineering and spec-driven development framework that drives AI coding agents (Claude Code, Codex, Gemini CLI, Kimi CLI, Copilot, Cursor, and more) through a disciplined phase loop. It solves context rot — the quality degradation that accumulates as an AI fills its context window — by running all heavy research, planning, and execution work in fresh-context subagents while keeping your main session lean.
How it works
Each milestone repeats the same five-step loop, one phase at a time:
- Discuss — capture implementation decisions before anything is planned
- Plan — research, decompose, and verify the plan fits a fresh context window
- Execute — run plans in parallel waves; each executor starts with a clean 200k-token context
- Verify — walk through what was built; diagnose and fix before declaring done
- Ship — create the PR, archive the phase, repeat for the next one
Quickstart
npx @opengsd/gsd-core@latest
The installer prompts for your runtime (Claude Code, OpenCode, Gemini CLI, Kimi CLI, Kilo, Codex, Copilot, Cursor, Windsurf, and more) and whether to install globally or locally. The installer is required for cross-runtime compatibility — do not copy files from agents/ or commands/ directly.
On another runtime or without Node.js? See Install on your runtime.
Once installed, start your first project:
/gsd-new-project
New here? Follow Your first project for a guided walkthrough from install to first shipped phase.
Documentation
Tutorials — learning by doing:
How-to guides — task-focused recipes:
Reference — authoritative facts:
Explanation — concepts and design decisions:
Full index: docs/README.md. Other languages: 日本語 · 한국어 · Português · 简体中文.
Why it works
Most AI-coding setups fail at scale because context bloat silently degrades output quality, there is no shared memory between sessions, and nothing verifies that code actually works. GSD Core solves all three: heavy work runs in fresh subagents, structured artifacts like STATE.md and CONTEXT.md survive session boundaries, and the verify step walks through what was built and generates fix plans before a phase is declared done. See docs/explanation/context-engineering.md for the full reasoning.
Troubleshooting? See docs/how-to/recover-and-troubleshoot.md.
Community
| Project | Platform |
|---|---|
| gsd-opencode | Original OpenCode port |
| Discord | Community support |
Star History
License
MIT License. See LICENSE for details.
Claude Code is powerful. GSD Core makes it reliable.