claude-stuff plugin
A plugin monorepo: atomic Git commits, parallel work in Jujutsu, pull request review and PHP code style.
- 64 ★ on the repository
- Last commit
Extended access
Why this level
- The git-workflow and jj-workflow skills rewrite history: amend, fixup, rebase, bookmark deletion.
- Pull request comments are posted through `gh` on your behalf after approval.
Install
- Works in
Manual install
npx skills add paulinevos/claude-stuffInstalls all skills into any supported agent. The `--list` flag previews the set without installing.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The git-workflow and jj-workflow skills rewrite history: amend, fixup, rebase, bookmark deletion.
- Pull request comments are posted through `gh` on your behalf after approval.
This is third-party code. Review the repository files before installing.
What it does
claude-stuff gathers five plugins installed through the `vos` marketplace. The `git-workflow` plugin keeps work in atomic commits: skills route a change to the right commit through amend, edit in place or fixup, resolve merge conflicts, undo merges and rebases through the reflog and find the regressing commit with bisect. The `jj-workflow` plugin organizes parallel work of several agents in Jujutsu: a separate workspace and bookmark per slice of the task, granular revisions, stacks of dependent slices and cleanup at the end. Without Jujutsu it falls back to git worktrees. The `pr-reviewer` plugin picks pull requests awaiting your review and launches a reviewer per PR following that project's rules, one that only plans comments. There is also `php-style` with object calisthenics principles and `amp-workflow` for Amp.
Who it is for. Developers who keep Git history in tidy commits, run several agents on one repository or work through a pull request queue.
Good fit when
- A change belongs to an existing commit and should be folded into it rather than left separate.
- A merge or rebase went wrong and must be undone through the reflog.
- Several agents work on slices of one task and each needs its own folder and bookmark.
- A review queue piled up and you want comment drafts following each project's rules.
- PHP is written by object calisthenics rules: one indent level, no else, no getters.
Not a fit when
- The repository's history is free-form and atomic commits are not wanted.
- The `pr-reviewer` plugin will not work without `gh` and the Solo MCP server.
- You do not use Jujutsu and do not want to switch: then only the git worktree fallback is useful.
Example request
This change belongs to the third commit of the branch. Pick the right method and fold it in without breaking the rest of the history.Limitations
This is the author's personal set, so the rules reflect her process: atomic commits, rebase over merge, PHP style by object calisthenics. The `pr-reviewer` plugin needs `gh` and the Solo MCP server, and the mapping of repositories, checkouts and projects is kept in `~/.claude/pr-reviewer/projects.json`. The reviewer only plans comments, and they are posted after your approval. Jujutsu workspaces are created outside the working copy, in `../<repo>.workspaces/<slice>`. The Amp plugin targets Amp CLI and its limits.
How to disable. Run `/plugin uninstall` for the relevant plugin, for example `git-workflow@vos`. Skills installed through `npx skills` are removed from the agent's skills folder by hand.
FAQ
How do I install the claude-stuff plugins?
Through `npx skills add paulinevos/claude-stuff`, which works with any supported agent, and `--list` previews the set without installing. For Claude Code run `/plugin marketplace add paulinevos/claude-stuff`, then `/plugin install git-workflow@vos`.
Which skills are in git-workflow?
Four: `maintain-atomic-commits` routes a change through amend, edit or fixup, `resolve-merge-conflict` resolves conflicts, `undo-op` reverts through the reflog, `bisect-debug` finds the regressing commit.
How does jj-workflow work without Jujutsu?
If there is no `.jj` directory or submodules matter, the plugin falls back to git worktrees. Workspaces are created in `../<repo>.workspaces/<slice>` and never inside a working copy.
Does pr-reviewer post comments itself?
No. The reviewer plans comments, and the `collect-review-findings` skill first asks you to approve them, then posts. `gh` and the Solo MCP server are required.
What do the repository benchmarks check?
The `benchmarks/` directory holds measurements of the context skills occupy and of their quality on given cases. The `benchmark-skills.rb` and `benchmark-skill-quality.rb` scripts run them.
Discussion
No questions or reviews yet.
Related
PluginsA Claude Code plugin marketplace by Frad LEE: Git and GitFlow, GitHub, refactoring, memory, research, image generation and interface work
A plugin that readies a project for Claude Code: guidance, tests, review, TDD, refactoring and a resumable fix loop
A marketplace of 23 plugins for Claude Code: git and pull requests, code review, TDD, specs and delegation to other models
Plugins for git, Python and accessibility in one place: 400+ skills, subagents and hooks against dangerous agent commands.
Claude Code plugins: plan, work and review commands, subagents, hooks and writing skills in a practical minimalism spirit.
A marketplace of small Claude Code plugins: path previews, context and token meters, a smart /commit and turn rollback.
README in short
The author calls the repository her mono-repo for assorted Claude stuff and invites use. Each plugin is described by a table of skills with conditions of use.