portal

Create isolated Git worktrees with feature branches for parallel development.

12|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Alexander-Tyagunov/magician --skill portal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: portal
Source: https://github.com/Alexander-Tyagunov/magician/tree/main/skills/portal
Command: npx skills add https://github.com/Alexander-Tyagunov/magician --skill portal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Isolate feature development by using Git worktrees so work in progress remains isolated from the main branches.

Core Features & Use Cases

  • Create a dedicated worktree and a new feature branch (feature/<name>) to separate development tasks.
  • Workspace context propagates automatically via the worktree-init.sh hook to ensure consistent environment across worktrees.
  • Supports disableGit mode by reading .workspace/local/prefs.md and skipping git operations when disabled.
  • Cleanup after merge by removing the worktree and deleting the feature branch.

Quick Start

Run /portal to create an isolated feature worktree and begin development.

Frequently Asked Questions about portal

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I isolate feature development work from my main git branch?▼

You can isolate feature development by creating a dedicated git worktree and a new feature branch. This separates your work in progress from shared branches so parallel development tasks remain independent.

What is a git worktree and when should I use one for parallel feature work?▼

A git worktree is a linked working directory that lets you checkout multiple branches simultaneously. Use it for parallel feature work, testing in isolated contexts, or PR preparation without affecting shared branches.

Can I skip git operations when creating isolated workspaces?▼

Yes, you can skip git operations by enabling disableGit mode. The tool reads .workspace/local/prefs.md and automatically skips git operations when this mode is enabled.

How do I clean up a git worktree after merging a feature branch?▼

Worktree cleanup after merge involves removing the worktree directory and deleting the associated feature branch. This post-merge process ensures stale branches and isolated directories do not accumulate.

Does workspace context propagate automatically to new git worktrees?▼

Yes, workspace context propagates automatically via the worktree-init.sh hook. This ensures consistent environment configuration across all newly created worktrees.

What is the best way to manage multiple feature branches without switching context?▼

Using git worktrees is an effective approach for managing multiple feature branches without context switching. Each worktree provides an isolated working directory for a specific branch, enabling simultaneous parallel development.