Bug Fix: setup command fails to find root package.json
Track: fix-setup-glob-pattern-20260329
Overview
The /please-plugins:setup command instructs Claude to "Read package.json in the current working directory" (line 12), but this ambiguous instruction allows Claude to use the Glob tool first. In projects with node_modules/, hundreds of nested package.json files bury the root file beyond the Glob result limit (250), making the setup command unusable.
Root Cause
setup.md:12 uses ambiguous prose without constraining tool choice or path. The TypeScript hook check-dependencies.ts already handles this correctly with join(cwd, 'package.json').
Plan
Script delegation — add --setup CLI mode to check-dependencies.ts and rewrite setup.md to invoke it.
See: .please/docs/tracks/active/fix-setup-glob-pattern-20260329/plan.md
Bug Fix: setup command fails to find root package.json
Overview
The
/please-plugins:setupcommand instructs Claude to "Readpackage.jsonin the current working directory" (line 12), but this ambiguous instruction allows Claude to use the Glob tool first. In projects withnode_modules/, hundreds of nestedpackage.jsonfiles bury the root file beyond the Glob result limit (250), making the setup command unusable.Root Cause
setup.md:12uses ambiguous prose without constraining tool choice or path. The TypeScript hookcheck-dependencies.tsalready handles this correctly withjoin(cwd, 'package.json').Plan
Script delegation — add
--setupCLI mode tocheck-dependencies.tsand rewritesetup.mdto invoke it.See:
.please/docs/tracks/active/fix-setup-glob-pattern-20260329/plan.md