Attach the current or a new vibing.nvim chat to an already-existing git worktree via natural language — no separate UI. Use when the user wants to switch/attach a chat to an existing worktree ("let's go into the auth-fix worktree", "attach to worktree X", "continue in the feature-y worktree").
Scanned 8/31/2026
Install to Claude Code
npx -y skills add shabaraba/vibing.nvim --skill vibing-worktree-attach --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Vibing Worktree Attach?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/shabaraba-vibing-worktree-attach)More formats (shields.io, HTML) on the badges page.
---
name: vibing-worktree-attach
description: Attach the current or a new vibing.nvim chat to an already-existing git worktree via natural language — no separate UI. Use when the user wants to switch/attach a chat to an existing worktree ("let's go into the auth-fix worktree", "attach to worktree X", "continue in the feature-y worktree").
---
# vibing-worktree-attach
Git worktrees provide isolated working directories for parallel development. This skill points
this chat's own `working_dir` frontmatter at an already-existing worktree — it never creates one
(see the `vibing-worktree-create` skill for that) and never runs `git worktree add`.
## Attach — "what worktrees are there? — let's go into the auth one"
Works the same whether this is a brand-new chat's first exchange or mid-conversation in an
existing one.
1. Surface candidates (see the `vibing-worktree-list` skill):
```bash
git worktree list --porcelain
```
2. Once the user picks one, follow steps 3-5 of the `vibing-worktree-create` skill to point this
chat's own `working_dir` frontmatter at the chosen worktree's path via the `vibing-nvim` MCP
tools — the worktree already exists, so there's no `git worktree add` step to run first, and
there's no new chat buffer to open (the current conversation continues, and its next turn
already runs in the chosen worktree).
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.