skills.rest
eavichay
eavichayCOMMUNITY
Explore all skills by this author →
GitHub

git-worktree-list

Lists git worktrees with provenance metadata and optional JSON output for dashboards or CLI tools.

Updated Jul 7, 2026
Search Tags:#automation#git#developer tools#version control#worktree
One-click install
npx skills add https://github.com/eavichay/mycli --skill git-worktree-list
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-worktree-list
Source: https://github.com/eavichay/mycli/tree/main/.cursor/skills/git-worktree-list
Command: npx skills add https://github.com/eavichay/mycli --skill git-worktree-list

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the difficulty of tracking multiple active feature branches and their corresponding filesystem locations in complex projects using git worktrees.

Core Features & Use Cases

  • Provenance Tracking: Identifies worktrees created via manifest-based workflows.
  • Machine-Readable Output: Provides JSON support for integration into automated dashboard or CLI tools.
  • Use Case: Quickly verify which feature branches are currently checked out in your local environment and where they are located to avoid context-switching errors.

Quick Start

Use the git-worktree-list skill to display all active feature worktrees in the current repository.

Frequently Asked Questions about git-worktree-list

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

FAQPage Schema
How do I list active git worktrees and their filesystem locations?▼

To list active git worktrees, use this skill to display all checked-out feature branches and their corresponding paths. It targets manifest-based workflows to improve developer visibility and prevent context-switching errors in complex projects.

Can I get git worktree output in JSON format for automated dashboards?▼

Yes, you can get git worktree output in JSON format. This skill provides machine-readable output to support integration into automated dashboard or CLI tools, allowing you to programmatically track worktree provenance metadata.

What is a worktree-per-feature strategy and when do I need provenance tracking?▼

A worktree-per-feature strategy links separate filesystem directories to individual feature branches. You need provenance tracking when managing multiple active branches, to identify worktrees created via manifest-based workflows and avoid location errors.

Does listing git worktrees with provenance metadata require internal utility scripts?▼

Yes, resolving full provenance metadata requires access to the project's internal utility scripts. You also need a local git environment to successfully list active worktrees and identify manifest-based feature branching origins.

What's the best way to audit multiple git feature branches in local development?▼

The best way to audit local git feature branches is using this skill to instantly verify active worktrees and their locations. It provides visibility into manifest-based workflows, preventing context-switching errors across complex project environments.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
metric-space-aimetric-space-ai
2

ticket-monitoring-ingest

Ingests monitoring snapshots from systems like Prometheus and Grafana into ticket context via CLI.

Official
Intermediate
elsa-workflowselsa-workflows
7.9k

speckit-git-feature

Create git feature branches with sequential or timestamp-based names.

Official
Intermediate
OpenAuthorityOpenAuthority
8

git_checkout

Checkout a Git branch or commit with uncommitted change safeguards.

Official
Intermediate