worktree-status

Audit git worktrees and report branch, dirty, and merge status.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/hvrryh-web/RadiantX --skill worktree-status-hvrryh-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree-status
Source: https://github.com/hvrryh-web/RadiantX/tree/main/.agents/skills/worktree-status
Command: npx skills add https://github.com/hvrryh-web/RadiantX --skill worktree-status-hvrryh-web

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit all git worktrees in the current project to report their branches, dirty state, and merge status.

Core Features & Use Cases

  • Collects and reports on every worktree, including branch, dirty state, and merge status.
  • Detects squash-merged branches via content diff to avoid false not merged flags.
  • Presents results in a clear Markdown table and guides safe cleanup decisions.

Quick Start

Run this skill in your repository to generate a live report of all worktrees, their branches, and cleanliness.

Frequently Asked Questions about worktree-status

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

FAQPage Schema
How do I check the status of all git worktrees in my project?

To check the status of git worktrees, you can run an audit that pulls the latest main and collects per-worktree information. It reports branch, dirty state, and merge status, presenting results in a Markdown table.

How can I find which git worktrees have uncommitted changes?

To find which git worktrees have uncommitted changes, run a worktree audit that collects per-worktree information. It reports the dirty state of each worktree in a clear Markdown table.

How do I detect squash-merged branches in git worktrees?

To detect squash-merged branches in git worktrees, the audit uses content diff against the latest main. This avoids false not merged flags that can occur with standard merge status checks.

Can I get cleanup guidance for git worktrees?

Yes, you can get cleanup guidance for git worktrees. The audit identifies which worktrees can be safely cleaned up and which branches are not merged, providing optional cleanup guidance alongside the results.

What is the best way to identify unmerged branches across git worktrees?

The best way to identify unmerged branches across git worktrees is to run an audit that pulls the latest main and checks merge status. It detects squash-merged branches via content diff to ensure accurate results.

Do I need any dependencies to audit git worktrees?

No dependencies are required to audit git worktrees. The skill operates independently to pull the latest main, collect per-worktree information, and present results as a Markdown table.