portal
Skill14 starsChanged 50 days agoMITView on GitHub
Creates a git worktree for isolated feature work; respects disableGit. Use to isolate a feature on its own branch.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- charlie947/reel-editing-skillstheir own version, first seen Nov 1, 2026
- frankieramirez/manatheir own version, first seen Oct 17, 2026
- tinyhumansai/portaltheir own version, first seen Oct 13, 2026
- kurtosis-tech/kurtosistheir own version, first seen Oct 8, 2026
- BuilderIO/agent-nativetheir own version, first seen Oct 8, 2026
- lbliii/mcportaltheir own version, first seen Oct 8, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- BuilderIO/agent-native★ 7.7ksame name
- kurtosis-tech/kurtosis★ 558same name
- meta-quest/agentic-tools★ 200same name
- charlie947/reel-editing-skills★ 9same name
- stevehansen/eidet★ 4same name
- frankieramirez/mana★ 1same name
- jord0-cmd/jord0.skills★ 1same name
- lbliii/mcportal★ 1same name
- tinyhumansai/portal★ 1same name
- subsquid-labs/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- accelerateSkill
- almanacSkill
- autopsySkill
- blueprintSkill
- certifySkill
- chronicleSkill
- confluenceSkill
- conjureSkill
- deploySkill
- divineSkill
- inscribeSkill
- jiraSkill
- knowledge-graphSkill
- magicSkill
- manifestSkill
- orchestrateSkill
- scrutinizeSkill
- sealSkill
- sentinelSkill
- statuslineSkill
- transmuteSkill
- unravelSkill
- wardSkill
- weaveSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Create an isolated git worktree for feature development.
- Very specific: line 14
Read .workspace/local/prefs.md for disableGit: true.
- Very specific: line 31
claude --worktree <name>: Use it when claude --help lists --worktree. - Very specific: line 32
Agent
isolation: worktree: Use it for a dispatched subagent that edits files in parallel with others. - Very specific: line 33
git sparse-checkoutin a monorepo: Use it when the repository has more than about 10,000 tracked files and the feature touches one or two … - Distinctive: line 34
Plain
git worktree add: Use it in every other case (the process above). - Distinctive: line 36
Keep each change small and state its intent in the branch name and the first commit (lore/git.md).
- Very specific: line 40
Create a feature directory: mkdir -p .features/<name>
- Distinctive: line 52
After /seal completes and the PR merges:
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/portal — Git Worktree Isolation
Create an isolated git worktree for feature development.
Check disableGit Mode
Read .workspace/local/prefs.md for disableGit: true. If set, skip all git operations and work in the current directory.
Process (git mode)
- Get branch name — if
$ARGUMENTSis non-empty, use it as the feature name directly. Otherwise ask: "What's this feature called? (I'll use it as the branch/worktree name.)" End your turn. Wait for their answer before creating anything. - Create worktree (one plain command, so it matches this skill's pre-approval):
git worktree add ../<repo-name>-<name> -b feature/<name> - Workspace files — tracked files (
.workspace/shared/) come with the branch; gitignored ones such as.workspace/local/prefs.mddon't. Worktrees that Claude Code creates itself (claude --worktree, subagent worktree isolation) copy the gitignored files listed in a.worktreeincludefile at the repo root, so listing.workspace/local/prefs.mdthere is a useful tip for the user. For this plaingit worktree add, copy any local file the new worktree needs (that copy goes through the normal permission prompt). - Confirm the new worktree path to the user
- Say: "Worktree created at
../<path>. Work there for isolation. Run /seal when ready to merge."
Alternatives at agent scale
Pick the lightest isolation that fits. Feature-detect each one. Do not ask the user to check a version.
claude --worktree <name>. Use it whenclaude --helplists--worktree. It starts a new session in its own worktree and copies the files listed in.worktreeinclude. Tell the user the command. Do not run it from this session.- Agent
isolation: worktree. Use it for a dispatched subagent that edits files in parallel with others. Set it in the agent's frontmatter or in theAgentcall when the tool accepts it. Claude Code removes the worktree when the agent made no change. git sparse-checkoutin a monorepo. Use it when the repository has more than about 10,000 tracked files and the feature touches one or two packages. After step 2, rungit -C ../<repo-name>-<name> sparse-checkout set --cone <package-dirs>. That command is not pre-approved, so it prompts. Add the shared config folders the build needs.- Plain
git worktree add. Use it in every other case (the process above).
Keep each change small and state its intent in the branch name and the first commit (lore/git.md).
Process (disableGit mode)
- Create a feature directory:
mkdir -p .features/<name> - Note: no git isolation — be careful about conflicts with other in-progress work
- Say: "Working in .features/
<name>/ (disableGit mode — no worktree created)."
Keep sibling worktrees in the loop
Worktrees isolate the files, not the consequences: a rename, a signature change, or a shared-dependency bump made here breaks whatever a sibling session is building on. When Claude Code's cross-session messaging is available, tell the affected session yourself instead of letting it discover the breakage — ListAgents finds the sessions working the other worktrees, SendMessage delivers one self-contained sentence about what landed.
Feature-detect it: no ListAgents, or no peer listed, means carry on exactly as before and note the change in your own summary. It isn't available in every environment, and a session inside a container can't see one on the host. See lore/cross-session.md.
Cleanup After Merge
After /seal completes and the PR merges:
git worktree remove ../<repo-name>-<name>
git branch -d feature/<name>Obstacles
This is a thin git-worktree utility. If a worktree cannot be created (branch already exists, dirty tree), report it in prose to the caller and stop; it emits no structured upward Obstacles block.
See lore/obstacles.md.
Completion Signal
"Portal open. Worktree at <path>, branch <branch>. Start implementation or run /orchestrate."
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

