wb300

Manage Git branches, worktrees, and coding agents for parallel development.

Updated May 20, 2026
One-click install
npx skills add https://github.com/RealEmmettS/shaughv-code --skill wb300
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wb300
Source: https://github.com/RealEmmettS/shaughv-code/tree/main/plugins/shaughv-code/skills/wb300
Command: npx skills add https://github.com/RealEmmettS/shaughv-code --skill wb300

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the management of Git branches, worktrees, and coding agents, making it easier to monitor and coordinate parallel development activities.

Core Features & Use Cases

  • Branch Inspection: Quickly view active branches, worktrees, and their corresponding agents.
  • Lifecycle Tracking: Understand the state of each branch (editing, uncommitted, committed, pushed, merged, etc.).
  • Merge Risk Assessment: Predict potential merge conflicts before they occur.
  • Clean-Up Guidance: Identify and safely remove unnecessary branches and worktrees.
  • Use Case: Imagine you're managing a project with multiple branches, and you want to ensure that everything is ready for the next merge. Using wb300, you can get a comprehensive view of the branch hierarchy, identify any conflicts, and determine which branches are ready to merge.

Quick Start

To inspect the state of branches and worktrees for the current repository, use the wb300 agent command.

Frequently Asked Questions about wb300

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage multiple Git worktrees and branches for parallel coding agents?

To manage Git worktrees and branches for parallel coding agents, you can use this Skill to monitor branch lifecycles, track active worktrees, and coordinate concurrent development efforts through a centralized inspection command.

Can I predict merge conflicts between Git branches before they happen?

Yes, you can predict merge conflicts before they happen. The Skill performs merge risk assessment across active branches to identify potential conflicts early, helping you avoid failed merges during collaborative parallel development.

What is the best way to clean up unnecessary Git branches and worktrees?

The best way to clean up Git branches and worktrees is using automated clean-up guidance. The Skill identifies unnecessary branches and worktrees, offering safe removal suggestions based on their current lifecycle state.

Does this branch management tool support JSON output for scripting integration?

Yes, the branch management tool supports JSON output. It provides structured data for branch states, worktree mappings, and merge risks, allowing you to integrate the results directly into your automated scripts.

Do I need a specific Git environment to track parallel branch lifecycles?

You need a standard Git environment to track parallel branch lifecycles. The Skill operates as an agent requiring Git to inspect worktrees, monitor states like committed or pushed, and assess merge risks without additional dependencies.