Files

TÂCHES 01c9115f3a fix(#478 ): respect commit_docs=false in all .planning commit paths (#482 )

* fix(execute-phase): pass file paths to subagents instead of content

The --include flag added in fa81821 caused orchestrator context bloat
by reading STATE, config, and plan files into the orchestrator's context,
then embedding all content in Task() prompts.

With multiple plans, this consumed 50-60%+ of context before execution.

Fix: Pass file paths only. Subagents read files themselves in their
fresh 200k context. Orchestrator stays lean (~10-15% as intended).

Fixes #479

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix: respect commit_docs=false in execute-plan and debugger workflows

Two code paths bypassed the commit_docs configuration check, causing
.planning files to be intermittently committed when commit_docs=false:

1. execute-plan.md: update_codebase_map step ran `git add .planning/codebase/*.md`
   unconditionally — now gated behind commit_docs check
2. gsd-debugger.md: used `git add -A` which stages .planning/ files — replaced
   with explicit individual file staging and proper commit_docs conditional

Fixes #478

https://claude.ai/code/session_013yS1F2VR3Jn2pdwqr5NuDo

* fix: route all .planning commits through gsd-tools.js CLI

Instead of wrapping direct git commands in markdown conditionals,
both bypass paths now use gsd-tools.js commit which has the
commit_docs check built in:

1. execute-plan.md: uses `gsd-tools.js commit --amend` for codebase
   map updates (new --amend flag added to CLI)
2. gsd-debugger.md: code commit uses direct git (no .planning files),
   planning docs commit uses gsd-tools.js commit

Also added --amend support to gsd-tools.js commit command so the
execute-plan codebase map step can amend the previous metadata commit.

Fixes #478

https://claude.ai/code/session_013yS1F2VR3Jn2pdwqr5NuDo

* docs: update reference docs to use gsd-tools.js CLI for all .planning commits

Reference documentation showed direct git add/commit patterns for
.planning files, which agents copy-paste and bypass the commit_docs
check. Updated all three reference files to show gsd-tools.js commit
as the canonical pattern:

- git-planning-commit.md: replaced manual bash conditionals with CLI
- git-integration.md: replaced direct git add/commit in initialization,
  plan-completion, and handoff examples
- planning-config.md: replaced conditional git example with CLI call

https://claude.ai/code/session_013yS1F2VR3Jn2pdwqr5NuDo

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

2026-02-08 08:09:03 -06:00

1.4 KiB

Raw Blame History

Git Planning Commit

Commit planning artifacts using the gsd-tools CLI, which automatically checks commit_docs config and gitignore status.

Commit via CLI

Always use gsd-tools.js commit for .planning/ files — it handles commit_docs and gitignore checks automatically:

node ~/.claude/get-shit-done/bin/gsd-tools.js commit "docs({scope}): {description}" --files .planning/STATE.md .planning/ROADMAP.md

The CLI will return skipped (with reason) if commit_docs is false or .planning/ is gitignored. No manual conditional checks needed.

Amend previous commit

To fold .planning/ file changes into the previous commit:

node ~/.claude/get-shit-done/bin/gsd-tools.js commit "" --files .planning/codebase/*.md --amend

Commit Message Patterns

Command	Scope	Example
plan-phase	phase	`docs(phase-03): create authentication plans`
execute-phase	phase	`docs(phase-03): complete authentication phase`
new-milestone	milestone	`docs: start milestone v1.1`
remove-phase	chore	`chore: remove phase 17 (dashboard)`
insert-phase	phase	`docs: insert phase 16.1 (critical fix)`
add-phase	phase	`docs: add phase 07 (settings page)`

When to Skip

commit_docs: false in config
.planning/ is gitignored
No changes to commit (check with git status --porcelain .planning/)

1.4 KiB Raw Blame History