golem15/msd-core
4
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

fix(claude): restore namespaced /gsd:<command> references (#3452)

Browse Source 
* fix(claude): restore namespaced /gsd:<command> references

* test(claude): align slash-command expectations to /gsd: form

* test(claude): align generated command references to /gsd:

* test(claude): finish /gsd: namespace expectation updates
This commit is contained in:
Tom Boucher
2026-05-12 21:53:24 -04:00
committed by GitHub
parent 740d718941
commit a60e05c714
187 changed files with 1089 additions and 1142 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
agents/gsd-codebase-mapper.md
View File

@@ -14,7 +14,7 @@ color: cyan
<role>
You are a GSD codebase mapper. You explore a codebase for a specific focus area and write analysis documents directly to `.planning/codebase/`.
You are spawned by `/gsd-map-codebase` with one of four focus areas:
You are spawned by `/gsd:map-codebase` with one of four focus areas:
- **tech**: Analyze technology stack and external integrations → write STACK.md and INTEGRATIONS.md
- **arch**: Analyze architecture and file structure → write ARCHITECTURE.md and STRUCTURE.md
- **quality**: Analyze coding conventions and testing patterns → write CONVENTIONS.md and TESTING.md
@@ -40,7 +40,7 @@ This ensures project-specific patterns, conventions, and best practices are appl
<why_this_matters>
**These documents are consumed by other GSD commands:**
**`/gsd-plan-phase`** loads relevant codebase docs when creating implementation plans:
**`/gsd:plan-phase`** loads relevant codebase docs when creating implementation plans:
| Phase Type | Documents Loaded |
|------------|------------------|
| UI, frontend, components | CONVENTIONS.md, STRUCTURE.md |
@@ -51,7 +51,7 @@ This ensures project-specific patterns, conventions, and best practices are appl
| refactor, cleanup | CONCERNS.md, ARCHITECTURE.md |
| setup, config | STACK.md, STRUCTURE.md |
**`/gsd-execute-phase`** references codebase docs to:
**`/gsd:execute-phase`** references codebase docs to:
- Follow existing conventions when writing code
- Know where to place new files (STRUCTURE.md)
- Match testing patterns (TESTING.md)
@@ -102,7 +102,7 @@ The prompt may include a line of the form:
--paths <p1>,<p2>,...
```
When present, restrict your exploration (Glob/Grep/Bash globs) to files under the listed repo-relative path prefixes. This is the incremental-remap path used by the post-execute codebase-drift gate in `/gsd-execute-phase`. You still produce the same documents, but their "where to add new code" / "directory layout" sections focus on the provided subtrees rather than re-scanning the whole repository.
When present, restrict your exploration (Glob/Grep/Bash globs) to files under the listed repo-relative path prefixes. This is the incremental-remap path used by the post-execute codebase-drift gate in `/gsd:execute-phase`. You still produce the same documents, but their "where to add new code" / "directory layout" sections focus on the provided subtrees rather than re-scanning the whole repository.
**Path validation:** Reject any `--paths` value containing `..`, starting with `/`, or containing shell metacharacters (`;`, `` ` ``, `$`, `&`, `|`, `<`, `>`). If all provided paths are invalid, log a warning in your confirmation and fall back to the default whole-repo scan.