メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Diligence-grade product and technical analysis for the ae.ltd proof-agent concept, including comparison against Cursor and Omnara, MVP and production architecture, red-team review, and build-vs-buy evaluation. Use when Codex needs to create or critique PRDs, tech specs, competitive diligence, leadership memos, or multi-agent evaluation packs for agent-runtime, demo-agent, or proof-agent products.
Use when creating or upgrading CLAUDE.md instructions and selecting the right template baseline for repo size, architecture, and team constraints. AE.LTD template decision workflow.
Use when coding decisions depend on current library/framework APIs and you need version-accurate docs before implementation. AE.LTD workflow tuned for fast, verifiable doc grounding.
Use when scaffolding or extending MCP servers, adding tools/resources/prompts, or hardening MCP tool schemas and handlers. AE.LTD workflow tuned for production-ready MCP delivery.
Use when unit tests look green but confidence is low and mutation testing is needed to expose weak assertions. AE.LTD workflow for targeted mutation runs and actionable test hardening.
Use when converting plain-language automation goals into production-ready n8n workflow JSON with retries, error paths, and credential-safe placeholders. AE.LTD automation blueprint workflow.
| name | ae-ltd-worktree-mesh |
| description | 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. |
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.
User: "I need to work on two features in parallel"
→ git worktree list → git worktree add ../repo-feature -b feature main
Inspect current worktrees.
Run git worktree list and map branch ownership.
Create targeted worktree.
git worktree add ../<repo>-<task> -b <branch> <base>
Isolate runtime config. Do not duplicate secrets. Keep per-worktree local env overrides where needed.
Keep each worktree single-purpose. One task or ticket per worktree. Avoid mixed commits.
Clean only when safe.
Remove merged/obsolete worktrees, then run git worktree prune.
git branch -d, not force delete, unless user explicitly approves.