Skill

repo-from-thread

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.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin claude-rudder

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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.

SKILL.md

Similar Skills

yeet

Facilitates GitHub contribution workflows including creating/updating pull requests, issues, discussions, and comments using GitHub CLI with semantic analysis for titles and descriptions.

11 files

paulrberg-agent-skills

update-claude-md

Updates CLAUDE.md with workflow decisions, tool preferences, conventions, and patterns from recent conversations. Ensures context persists across sessions.

ttal

conversation-context-export

Exports conversation context (purpose, intent, design decisions, constraints) to .dev/contexts/{sanitized-branch}.md for handoff to reviewers, other AIs, or new sessions. Triggers on phrases like 'export context' or 'save to .dev'.

1 file

conversation-context

Stats

Stars1

Forks0

Last CommitApr 27, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Repo From Thread

Steps

Ask the user:

Repo name (propose one based on the conversation topic).
Public or private.
Parent directory (default: ~/repos/github/my-repos/).

Synthesize the conversation so far into seed context. Do NOT dump the raw transcript — distill it. Cover:

What the project is and why it exists (the goal the user articulated).
Decisions already made in the thread.
Open questions / next steps.
Any file paths, commands, URLs, or constraints mentioned.

Create and initialize the repo:

mkdir -p <parent>/<name> && cd <parent>/<name>
git init -b main

Seed files:

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.

Initial commit, create GitHub repo, push:

gh repo create danielrosehill/<name> --<public|private> --source . --remote origin --push

Report: local path, GitHub URL, and suggest the user run /session-transfer:new-claude-at <path> to continue the work in a fresh session with the seeded context.

Notes

The value of this skill is the distillation in step 2 — a raw transcript dump is useless. Write the CLAUDE.md as if briefing a colleague who just walked in.

If the conversation is very short or context-thin, ask the user to add anything important you might have missed before committing.

Default to private unless the user says otherwise.

Repo From Thread

Steps

Ask the user:
- Repo name (propose one based on the conversation topic).
- Public or private.
- Parent directory (default: ~/repos/github/my-repos/).
Synthesize the conversation so far into seed context. Do NOT dump the raw transcript — distill it. Cover:
- What the project is and why it exists (the goal the user articulated).
- Decisions already made in the thread.
- Open questions / next steps.
- Any file paths, commands, URLs, or constraints mentioned.

Create and initialize the repo:

mkdir -p <parent>/<name> && cd <parent>/<name>
git init -b main

Seed files:
- 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.

Initial commit, create GitHub repo, push:

gh repo create danielrosehill/<name> --<public|private> --source . --remote origin --push

Report: local path, GitHub URL, and suggest the user run /session-transfer:new-claude-at <path> to continue the work in a fresh session with the seeded context.

Notes

The value of this skill is the distillation in step 2 — a raw transcript dump is useless. Write the CLAUDE.md as if briefing a colleague who just walked in.
If the conversation is very short or context-thin, ask the user to add anything important you might have missed before committing.
Default to private unless the user says otherwise.