Skip to main content

/

/

Stats

Actions

Tags

Stats

Actions

Tags

ClaudePluginHub

Community directory for discovering and installing Claude Code plugins.

Find plugins for your stack

Instant recommendations from real install data.

Product

Browse Plugins
Marketplaces
Pricing
About
Contact

Resources

Learning Center
Blog
Weekly Digest
Claude Code Docs
Plugin Guide
Plugin Reference
Plugin Marketplaces

Community

Browse on GitHub
Get Support

Legal

Terms of Service
Privacy Policy

Browse · Plugins · Top Plugins · Marketplaces · Components · Technologies · Skills · Agents · Commands · Hooks · MCP Servers · LSP Servers · Output Styles · Themes · Monitors

Categories · Productivity · Development · Testing · Deployment · Security · Documentation · Data · Utilities

© 2025 ClaudePluginHub

Community Maintained · Not affiliated with Anthropic

ClaudePluginHub

ClaudePluginHub

Tools Learn Pricing

Search everything...

clone | dx

Home
Skills
dx
clone

Skill

clone

From dx

Clones current Claude Code conversation via bash script to branch and experiment with alternatives. Locate cloned session with claude -r marked [CLONED timestamp].

developer-tools

Popularity

Stars

9,087

Forks

707

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/dx:clone

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Clone the current conversation so the user can branch off and try a different approach.

SKILL.md

16 lines · ~226 tokens

Stats

LanguageHTML

Stars9,087

Forks707

MaintenanceExcellent

Last CommitJul 6, 2026

Actions

View Source View Plugin View on GitHub View README

Tags

conversation-clone

claude-workflow

duplicate-session

Stats

LanguageHTML

Stars9,087

Forks707

MaintenanceExcellent

Last CommitJul 6, 2026

Actions

View Source View Plugin View on GitHub View README

Tags

conversation-clone

claude-workflow

duplicate-session

Clone the current conversation so the user can branch off and try a different approach.

Steps:

Get the current session ID and project path: tail -1 ~/.claude/history.jsonl | jq -r '[.sessionId, .project] | @tsv'
Find clone-conversation.sh with bash: find ~/.claude -name "clone-conversation.sh" 2>/dev/null | sort -V | tail -1
- This finds the script whether installed via plugin or manual symlink
- Uses version sort to prefer the latest version if multiple exist
Run: <script-path> <session-id> <project-path>
- Always pass the project path from the history entry, not the current working directory
Tell the user they can access the cloned conversation with claude -r and look for the one marked [CLONED <timestamp>] (e.g., [CLONED Jan 7 14:30])

$

npx claudepluginhub ykdojo/claude-code-tips --plugin dx

Similar Skills

half-clone

9.1k

Clones the later half of a conversation into a new session, discarding earlier context to reduce token usage while preserving recent work.

View half-clone

Conversation History Sparse

29

Sparsely samples Claude and Codex conversation histories to infer worktree focus and restore session context without loading full transcripts.

claude-commands

View Conversation History Sparse

session-management

279

Manages Claude Code sessions using /rename, /resume, and CLI commands for naming, checkpointing, and resuming workflows in debugging, feature development, PR reviews, and investigations.

View session-management