ct

Name: ct
Availability: InStock
Author: Opensoft

Resolve the latest Speckit worktree path and branch with navigation guidance.

Updated Apr 11, 2026

Search Tags:#automation #git #cli #navigation #worktree #developer-tools #speckit

Ready to run

npx skills add https://github.com/opensoft/dartwing-ocr-pipeline --skill ct-opensoft

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ct
Source: https://github.com/opensoft/dartwing-ocr-pipeline/tree/main/.claude/skills/ct
Command: npx skills add https://github.com/opensoft/dartwing-ocr-pipeline --skill ct-opensoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill helps developers quickly locate and switch to the latest Speckit worktree, reducing manual searching and context switching when multiple worktrees exist.

Core Features & Use Cases

Identifies the latest Speckit worktree by consulting the handoff state or by scanning the worktree root to pick the newest directory.
Returns essential context (WORKTREE_PATH and BRANCH_NAME) and provides guidance for proceeding with navigation or checkout.
Use Case: When you are integrating changes across multiple Speckit worktrees, run this helper to jump to the current active worktree without manual lookup.

Quick Start

Run the get-last-worktree.sh script with --json to retrieve the latest Speckit worktree path and branch.

Frequently Asked Questions about ct

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

FAQPage Schema

How do I find the latest Speckit worktree path and branch name?▼

To find the latest Speckit worktree, the tool resolves the current worktree path and branch name by checking handoff state or scanning the worktree root for the newest directory, returning structured JSON output.

What is the best way to switch to the current active Speckit worktree?▼

The best way to switch to the current active Speckit worktree is running a resolver script that returns structured navigation guidance, including the exact WORKTREE_PATH and BRANCH_NAME, reducing manual searching across multiple directories.

Do I need Git installed to resolve Speckit worktree contexts?▼

Yes, Git is required to resolve Speckit worktree contexts. The process enforces Git availability and validates repository context before determining and returning the current worktree path and branch name.

How does the Speckit worktree navigation mechanism handle multiple worktrees?▼

The Speckit worktree navigation mechanism handles multiple worktrees by consulting the handoff state or scanning the worktree root to pick the newest directory, automatically identifying the latest active context.

Can I retrieve Speckit worktree data as JSON for automation scripts?▼

Yes, you can retrieve Speckit worktree data as JSON for automation by running the get-last-worktree.sh script with the --json flag, which outputs structured fields including WORKTREE_PATH and BRANCH_NAME.