AgentStack
SKILL verified MIT Self-run

Ae Ltd Worktree Mesh

skill-aegntic-cldcde-ae-ltd-worktree-mesh · by aegntic

Use when parallel branches are needed for feature work, hotfixes, or review fixes using git worktrees with minimal context switching. AE.LTD workflow for safe creation, usage, and cleanup.

No reviews yet
0 installs
10 views
0.0% view→install

Install

$ agentstack add skill-aegntic-cldcde-ae-ltd-worktree-mesh

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Ae Ltd Worktree Mesh? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

AE.LTD Worktree Mesh

What This Skill Does

Manages parallel Git worktrees for isolated feature work, hotfixes, and review fixes without context switching. Niche gem source: create-worktrees plugin from awesome-claude-code-toolkit.

  1. Create isolated worktrees for parallel tasks
  2. Map branch ownership across worktrees
  3. Clean up merged/obsolete worktrees safely

Quick Start

User: "I need to work on two features in parallel"
→ git worktree list → git worktree add ../repo-feature -b feature main

Workflow

  1. Inspect current worktrees.

Run git worktree list and map branch ownership.

  1. Create targeted worktree.

git worktree add ../- -b

  1. Isolate runtime config.

Do not duplicate secrets. Keep per-worktree local env overrides where needed.

  1. Keep each worktree single-purpose.

One task or ticket per worktree. Avoid mixed commits.

  1. Clean only when safe.

Remove merged/obsolete worktrees, then run git worktree prune.

Guardrails

  • Never remove worktrees with uncommitted changes.
  • Use git branch -d, not force delete, unless user explicitly approves.
  • Keep worktrees outside the main repo directory.
  • Use descriptive branch names tied to the task.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.