Repository navigation
Conversation
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
garrytan
added a commit
that referenced
this pull request
Mar 23, 2026
4 tasks done
24601
pushed a commit
to 24601/gastack
that referenced
this pull request
Mar 29, 2026
Collaborator
|
Closing — the codebase has changed significantly since this was opened and this no longer applies to current main. Thanks for the contribution. |
capy-ai Bot
added a commit
that referenced
this pull request
Nov 6, 2026
…rgeted-only reader (GST-1607) (#4064) * review-plan: a granted fix round after the targeted read plans one targeted-only reader (GST-1607) After the owner granted a fix round past the loop cap, the granted round's fix moved the product patch the targeted record names, so the receipt asked for a fresh targeted read while the plan printed done (harness-evals #271). With that --grant (checked against the approval record as before), any change since the read except plain docs now plans NEXT: targeted on the GST-1598 route: one targeted reader on HEAD for the head classes. A head with no targeted class adds no reader; no grant keeps done. The Capy pass program now runs a targeted manifest's voices stage, so a NEXT: targeted pass driven through it creates its reader (it activated voices only for fix-check). Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * docs: changelog fragment for GST-1607 Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * docs: review-policy names the granted case in the targeted-only skip list (docs audit) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --------- Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Users evaluating gstack in a project fork have no way to avoid installing skills globally to
~/.claude/skills/. The--localflag installs to./.claude/skills/in the current working directory so Claude Code picks them up for that project only.Changes
setup- add--localflag to argument parser--localis set, overrideSKILLS_DIRto$(pwd)/.claude/skills/and create the directory--localis combined with--host codex(Codex doesn't read project-local skills)gstack ready (project-local).with the install path in outputDefault behavior (
./setupwithout--local) is unchanged.Usage
Testing
bun testpasses (2 pre-existing Codex generation failures unrelated to this change).This contribution was developed with AI assistance (Claude Code).
Fixes #229