agentsclimarketplace

Gitflow setup

Skill jagp/claude-session-guardrails/gitflow-worktrees/skills/gitflow-setup

Enable Claude Code's background worktree isolation for the gitflow-worktrees plugin. Use when installing gitflow-worktrees or when the user wants background agents to run in isolated, gitflow-named worktrees.From its SKILL.md

Install
npx -y skills add jagp/claude-session-guardrails --skill gitflow-setup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.1 KB, 213 tokens by cl100k_base, as published. Nobody here has run it

gitflow-setup

Turn on background worktree isolation so each background agent runs in its own git worktree — whose branch this plugin's WorktreeCreate hook will name feature/*.

  1. Show the current setting:

    sh "${CLAUDE_PLUGIN_ROOT}/bin/setup.sh"
    
  2. Explain the trade-off: isolation stops background agents from colliding in the main working tree, at the cost of more worktrees to track. Recommend pairing it with the fear-of-abandonment audit so nothing gets stranded.

  3. If the user consents, enable it:

    sh "${CLAUDE_PLUGIN_ROOT}/bin/setup.sh" --enable
    
  4. Report the new value. Note that it applies to newly-spawned background agents, and that the exact accepted value ("worktree" vs an alternative) may depend on the Claude Code version — the setup script prints a fallback if the first is rejected.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,629. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.