obra
Option/config to disable git workflow
Is your feature request related to a problem? Please describe. I'm using the jj vcs to manage my repositories and claude is using git to manage commits, worktrees, branches, etc.
Describe the solution you'd like I'd like to be able to disable the git workflow skill completely (and maybe other git/vcs-related skills), without having to tinker with the fetched plugin source. An environment variable or a config file would solve this issue and allow for future options as well
Describe alternatives you've considered
- Fork the repo and remove the git skills - I'd have to maintain the patchset and babysit the repo to be up to date
- Make the changes in the locally downloaded plugin folder - I'd have to create a script to automate it whenever the plugin gets updated, probably through an additional plugin that just inserts a hook
Additional context Apart from jj, I don't like AI managing my git state, it messes with my workflow (although I see that the worktree is developed to fight that exact problem) - I just don't think it's for me
I'm in the middle of retooling to make it easier to customize or replace workflows locally. That worked just fine in the before-cc-plugins world, when you forked and cloned the skills repo.
Last night, I added a local overlay, but I don't love it.
What you're going to get once this is done should be a skills repo that the plugin clones into ~/.config/superpowers/ and that you can control, so you don't need to maintain patchesets.
A little further down the road, I think it should be possible to add skillsets. So you can swap in a jj workflow or a no-version control workflow. or a "the AI isn't allowed to write the tests" workflow. etc.
Jesse, I wonder why you decided to clone the skills repo into superpowers. My (maybe naive) take would be to convert the skill-groups into individual plugins that can be enabled/disabled separately. With skill-groups I mean the dirs under https://github.com/obra/superpowers-skills/tree/main/skills.
...but maybe this is what you mean with "skillsets" at the end.
The long term solution to this that obra suggests would of course be preferable to this, but I was fine for the time being by overriding the skill using the same name (I assume that this is what you mean by "local overlay") so here's how to do that for anyone curious:
- Create a directory with the same name as the skill you want to override at
~/.claude/skills(or the project equivalent at.claude/skill). - Copy the relevant
SKILL.mdfrom the plugin (or any other way you want)cp ~/.claude/plugins/cache/superpowers-marketplace/superpowers/<VERSION>/skills/using-git-worktrees/SKILL.md ~/.claude/skills/using-git-worktrees/ - Edit the local overlay skill at
~/.claude/skills/using-git-worktrees/SKILL.md. Personally I changed the relevant commands to use jujutsu workspaces instead of git worktrees but I imagine you can make it not do anything.
