菜单
Create a new GitHub repo seeded with context from the current conversation. Use when the user says "repo from thread", "repo from chat", "let's turn this conversation into a repo", or "create a repo to manage this project" mid-conversation.
用 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 | repo-from-thread |
| description | Create a new GitHub repo seeded with context from the current conversation. Use when the user says "repo from thread", "repo from chat", "let's turn this conversation into a repo", or "create a repo to manage this project" mid-conversation. |
Mid-conversation, the user realizes the work being discussed deserves its own GitHub repo. Spin one up and seed it with the context accumulated so far, so a fresh Claude session in that repo can pick up where this thread left off.
~/repos/github/my-repos/).mkdir -p <parent>/<name> && cd <parent>/<name>
git init -b main
README.md — short project description.CLAUDE.md — the distilled context from step 2, framed as instructions for a fresh Claude session ("This repo was spun out of a conversation on . Context so far: …").context/thread-origin.md — longer-form notes on decisions, open questions, next steps.gh repo create danielrosehill/<name> --<public|private> --source . --remote origin --push
/session-transfer:new-claude-at <path> to continue the work in a fresh session with the seeded context.