Skip to content

fix: add --local flag for project-scoped gstack install#271

Open
mvanhorn wants to merge 1 commit intogarrytan:mainfrom
mvanhorn:osc/229-setup-local-install
Open

fix: add --local flag for project-scoped gstack install#271
mvanhorn wants to merge 1 commit intogarrytan:mainfrom
mvanhorn:osc/229-setup-local-install

Conversation

@mvanhorn
Copy link

Summary

Users evaluating gstack in a project fork have no way to avoid installing skills globally to ~/.claude/skills/. The --local flag installs to ./.claude/skills/ in the current working directory so Claude Code picks them up for that project only.

Changes

  • setup - add --local flag to argument parser
  • When --local is set, override SKILLS_DIR to $(pwd)/.claude/skills/ and create the directory
  • Error if --local is combined with --host codex (Codex doesn't read project-local skills)
  • Show gstack ready (project-local). with the install path in output

Default behavior (./setup without --local) is unchanged.

Usage

cd my-project
git clone https://github.com/garrytan/gstack .claude/skills/gstack
cd .claude/skills/gstack
./setup --local

Testing

bun test passes (2 pre-existing Codex generation failures unrelated to this change).

This contribution was developed with AI assistance (Claude Code).

Fixes #229

Users evaluating gstack in a project fork currently have no way to
avoid polluting their global ~/.claude/skills/ directory. The --local
flag installs skills to ./.claude/skills/ in the current working
directory instead, so Claude Code picks them up only for that project.

Codex is not supported in local mode (it doesn't read project-local
skill directories). Default behavior is unchanged.

Fixes garrytan#229
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow for true isolation at setup

1 participant