
Bkff Git
- Updated June 19, 2026
- kbrockhoff/brockhoff-tools-claude
Bkff-git is an agent skill that runs git status, branch, commit, sync, and PR management for worktree-based development.
About
Bkff-git is the git lifecycle plugin in the Brockhoff Claude toolkit, aimed at developers who run agents on worktree-based branches instead of a single dirty working tree. It wraps everyday commands—status, branch creation, commits, sync with remotes, and PR management—so the agent can execute a disciplined git flow without ad-hoc shell recipes. Use it while implementing spec-driven work from the main bkff plugin: keep feature branches isolated, land commits with clear intent, and open or update pull requests from the same session. It is intentionally narrower than full DevOps automation; it focuses on the developer git loop that connects local agent edits to reviewable PRs. Confidence is moderate because detailed command surfaces live in the plugin source rather than the short catalog blurb.
- Worktree-oriented git lifecycle for parallel agent tasks
- Status, branch, commit, and sync commands as one plugin
- Pull request management from the agent session
- Companion to bkff spec-driven development workflows
- Git lifecycle abstraction for Claude brockhoff-tools
Bkff Git by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add kbrockhoff/brockhoff-tools-claude/plugin install bkff-git@brockhoff-toolsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Last updated | June 19, 2026 |
|---|---|
| Repository | kbrockhoff/brockhoff-tools-claude ↗ |
What it does
Manage git status, branches, commits, sync, and PRs in a worktree-based agent development setup.
Who is it for?
Best when you're pairing bkff spec-driven loops with git worktrees and agent-driven commits and PRs.
Skip if: Repos that forbid agent git access, or teams that only use hosted CI/CD with no local branch strategy.
When should I use this skill?
You need agent-driven git status, branching, commits, sync, or PR steps in a worktree-based bkff development session.
What you get
Agents follow a worktree-friendly git lifecycle with isolated branches, synced remotes, and managed PRs ready for review.
- Branches and commits from agent sessions
- Synced remote state
- Pull requests created or updated for review
By the numbers
- Five git lifecycle areas: status, branch, commit, sync, and PR management
Files
Git lifecycle commands for worktree-based development: status, branch, commit, sync, and PR management
bkff-git
Source: ./plugins/bkff-git
{ "name": "bkff-git", "source": "./plugins/bkff-git", "description": "Git lifecycle commands for worktree-based development: status, branch, commit, sync, and PR management" }
Related skills
How it compares
Agent-wrapped git and PR commands for worktrees, not a full CI/CD or release orchestration skill.
FAQ
Who is bkff-git for?
Developers using brockhoff-tools-claude who want agents to handle git and PR steps safely alongside bkff spec-driven work.
When should I use bkff-git?
During Build while branching and committing in worktrees, and during Ship when syncing and opening or updating pull requests.
Is bkff-git safe to install?
Review the Security Audits panel on this page; git plugins can modify branches and remotes—scope agent permissions and protect main.