Create clone

Skill YoniChechik/claude-code-config/skills/create-clone

Personal Claude Code configuration (hooks, commands, agents, settings).

Install

npx -y skills add YoniChechik/claude-code-config --skill create-clone

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create isolated git clone for feature

SKILL.md

1.7 KB, 361 tokens by cl100k_base, as published. Nobody here has run it

Creates a git clone for isolated feature development. Handles both new features and existing remote branches.

Feature description from user input

"$ARGUMENTS"

Feature Description Validation

If empty or missing: "Error: Feature description is required. Please provide a detailed description."

Process

Step 1: Parse Feature Description

Decide on feature name based on description
Convert feature name to kebab-case for branch naming
Feature name must NOT contain /. If the chosen name has a prefix like feat/, fix/, chore/, etc., strip everything up to and including the last / (e.g. feat/add-login → add-login). The final name must be a flat kebab-case string with no slashes.

Step 2: Run the clone script

bash ~/.claude/skills/create-clone/create_clone.sh "$FEATURE_NAME"

This handles: fetching latest main from origin, branch detection, cloning, branching off origin/main (never a stale local main), env symlinking, environment setup, and setting the terminal tab title to $FEATURE_NAME via an OSC escape sequence.

Step 3: Notify User

Tell user:

The clone has been created at _clones/$FEATURE_NAME
The branch $FEATURE_NAME is tracking remote
The tab title is set to $FEATURE_NAME automatically. To also rename the session in the resume picker, they may optionally type /rename $FEATURE_NAME themselves — this requires the manual command because /rename is interactive-only and cannot be automated.

Step 4: Change to Feature Directory

Change to the feature clone directory using /cd-permanent _clones/$FEATURE_NAME skill.