speckit-ctp

Retrieve the latest Speckit worktree path and metadata via get-last-worktree.sh.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/opensoft/dartwing-ocr-pipeline --skill speckit-ctp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-ctp
Source: https://github.com/opensoft/dartwing-ocr-pipeline/tree/main/plugins/speckit/skills/speckit-ctp
Command: npx skills add https://github.com/opensoft/dartwing-ocr-pipeline --skill speckit-ctp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides quick access to the latest Speckit worktree path and metadata, enabling fast context switching across worktrees.

Core Features & Use Cases

  • Retrieves and reports WORKTREE_PATH, BRANCH_NAME, BASE_BRANCH, and SOURCE for the current Speckit worktree.
  • Verifies whether the current checkout matches the reported WORKTREE_PATH and clearly indicates if a fallback or handoff state was used.
  • Use Case: A developer switches between Speckit worktrees and needs immediate confirmation of the active worktree before running commands.

Quick Start

Ask Speckit-ctp to display the latest Speckit worktree path and metadata

Frequently Asked Questions about speckit-ctp

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

FAQPage Schema
How do I check the current git worktree path and branch metadata?

To check your git worktree path and branch metadata, retrieve the latest Speckit worktree details. This reports the WORKTREE_PATH, BRANCH_NAME, BASE_BRANCH, and SOURCE, while verifying whether your current checkout directory matches the active worktree path.

What is a git worktree fallback and when is it used for context switching?

A git worktree fallback is used when handoff state is unavailable during context switching. The system locates the latest worktree path using the worktree-root fallback, clearly indicating in the metadata output whether the result originated from the fallback or the active handoff state.

How do I verify my current directory matches the active git worktree before running commands?

Verifying your current directory against the active git worktree involves checking the reported WORKTREE_PATH against your current path. The metadata output explicitly indicates whether your current checkout matches the latest worktree, preventing accidental commands in the wrong branch.

Does this worktree metadata tool require any specific dependencies or components?

This worktree metadata tool requires no external dependencies or components. It functions by running the get-last-worktree.sh script with the --json flag to parse and report the essential worktree path, branch, and source information directly.

Why does my git worktree show a different base branch than expected?

Your git worktree may show a different base branch than expected because the metadata reflects the BASE_BRANCH recorded in the handoff state or worktree-root fallback. Check the reported SOURCE field to determine where the branch information was retrieved from.