菜单
Create a new repo that starts from the current repo's state but takes a new direction — copy the code, seed CLAUDE.md with the revised approach, and push. Use when the user says "fork this in a new direction", "new repo from here with a new approach", or "branch this into a new project".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user points at a GitHub repo (an agent skill, MCP server, or "Claude plugin"-ish project) and wants to install or register it. Routes between native plugin install, MCP server registration, and adding to the user's third-party marketplace. Triggers on phrases like "install this from GitHub", "add this skill to my setup", "register this as a third-party plugin", "is this available as a Claude plugin".
Reference and worked example for the CONTEXT.md / CLAUDE.md two-file workflow. Use when the user asks "what is CONTEXT.md", how the human-context vs agent-briefing split works, or wants a copyable example pair to seed a new repo. Pairs with the operational skills (context-to-claude, claude-to-context, add-to-context, remove-from-context, manual-context-update, chunk-repo-context) — this skill explains the model; those skills do the work.
Use when the user wants to prune and chunk a bloated CLAUDE.md into a structured context/ store with pipeline folders and subagent templates. Triggers on phrases like "chunk claude", "prune CLAUDE.md", "set up context store", "split CLAUDE.md".
Use when the user wants to strip AI-generated style tics from documentation — emojis, excessive lists, all-caps filenames, fragmented structure. Triggers on phrases like "declaude the docs", "clean up documentation style", "remove emojis from docs", "apply style guide".
Use when the user wants to install a new user-level slash command at ~/.claude/commands/. Triggers on phrases like "install a slash command", "add a /command", "create a user-level slash command", "save this as a slash command".
Save a Claude Code plan (from ExitPlanMode, design discussion, or multi-step task) to persistent storage. ONLY invoke when the user explicitly asks to save/stash/store a plan (e.g. "save this plan", "stash the plan", "store the plan in the planning repo"). Do NOT auto-invoke after planning. Routes to the active project's `planning/` folder when one exists, else to the user's configured central planning repo.
| name | fork-new-direction |
| description | Create a new repo that starts from the current repo's state but takes a new direction — copy the code, seed CLAUDE.md with the revised approach, and push. Use when the user says "fork this in a new direction", "new repo from here with a new approach", or "branch this into a new project". |
Spin the current repo off into a brand-new repository that inherits the current code state but is briefed for a different direction. The new repo's CLAUDE.md captures the revised approach so the next Claude session can pick up cleanly.
This is a session-transfer pattern: the handover is encoded in the new repo's CLAUDE.md rather than a HANDOVER.md.
root=$(git rev-parse --show-toplevel)
name=$(basename "$root")
parent=$(dirname "$root")
<name>-v2 or similar).CLAUDE.md..git), so history stays with the original:
mkdir "$parent/<new-name>"
rsync -a --exclude='.git' "$root/" "$parent/<new-name>/"
cd "$parent/<new-name>"
git init -b main
CLAUDE.md in the new repo. Structure:
<original-name> at commit <sha> on <date>.README.md with a brief note that this repo is a new-direction fork of <original>.git add -A
git commit -m "Initial commit: fork from <original-name>@<short-sha> with new direction"
gh repo create danielrosehill/<new-name> --private --source . --remote origin --push
--public if the user asked for public.).git, so the new repo starts with a clean history and a single origin commit.