branch-base
by blackironj · ★ 0 · updated 21 Oct 2026
Start new branches and PRs from your integration branch (origin/dev by default); ask which base when a repo has none
Install
/plugin marketplace add blackironj/claude-mods/plugin install branch-base@blackironj-modsThen run /reload-plugins or start a new session. Requires Claude Code 2.1.287+.
What it hooks into
From an automated scan with claude plugin validate, not a security review. Mods run with your permissions; read the code before installing.
- Events
tool.call- API calls
$.env.get$.process.run$.ui.ask- Can see
Bash calls- Reach
- level 2 of 3 runs processesreads env varsdraws
Origin
- How it got here
- Automated scan of public GitHub repos, via the CC0 dataset awesome-claude-code-mods (scan of ).
- Repository
- github.com/blackironj/claude-mods
- Path in repo
branch-base- Source commit
215a4b4the exact code the scan read- Author
- @blackironj
- License
- MIT
- First published
- Last pushed
- First listed here
Name and description come from the mod's own manifest. We link to the code; we don't host it, and it stays under its author's license.
More from blackironj/claude-mods
approve-blocked
blackironj/claude-mods
When the auto-mode classifier blocks a Bash command, ask you Run or Don't run instead of having Claude tell you to run it with !
deploy-watch
blackironj/claude-mods
Watch GitHub Actions runs for the commit you pushed or merged; /ci pane and a toast when they finish
prod-guard
blackironj/claude-mods
Confirm production kubectl/helm/IAM mutations before they run (also inside aws-vault exec), require an explicit kube context, and hand interactive aws-vault commands to you
read-only-lock
blackironj/claude-mods
After a look-only prompt (English or Korean), block edits and mutating commands until you unlock
secret-guard
blackironj/claude-mods
Block Bash access to .env and Claude config files; mask tokens and keys in Bash and Read output