garrytan / garrytan/gstack

Better support for project-local installs?

Open
#1,524 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
133k
Forks
19.9k
Avg merge
18h 46m
Merged PRs (30d)
26

Description

I’m trying to understand the intended install model for GStack.

Right now the recommended setup seems to be installing it globally under ~/.claude/skills/gstack, while the --local option exists but is marked as deprecated.

This is a bit confusing for my use case. I use different workflows in different projects. Some projects may need GStack, but others may not. If GStack is installed globally, it feels like it can show up in projects where I didn’t really intend to use it.

I also noticed that some state seems to live under ~/.gstack, so even a “local” install does not feel fully local or easy to clean up.

Would you consider supporting a cleaner project-local install mode? For example:

my-project/
.claude/skills/gstack/
.gstack/

That way, if I remove the project directory, the GStack setup and state for that project are removed too.

I understand that a global install may be easier for keeping one shared version updated. But for people who use different workflows across projects, a project-local option would make GStack easier and safer to try.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.