ring:creating-worktrees
Creating an isolated git worktree for parallel branch work: selects the directory by priority order, verifies/adds .gitignore safety, auto-installs the detected toolchain's dependencies, runs a baseline test, and reports readiness. Use before a feature that needs isolation from the main workspace or before executing an implementation plan. Skip for a quick fix on the current branch or when already in the feature's worktree.
What this skill does
# Using Git Worktrees ## When to use - Starting feature that needs isolation from main workspace - Before executing implementation plan - Working on multiple features simultaneously ## Skip when - Quick fix in current branch → stay in place - Already in isolated worktree for this feature → continue - Repository doesn't use worktrees → use standard branch workflow ## Sequence **Runs before:** ring:writing-plans Git worktrees create isolated workspaces sharing the same repository for parallel branch work. **Announce at start:** "Using ring:creating-worktrees skill to set up isolated workspace." ## Directory Selection (priority order) 1. Existing `.worktrees/` or `worktrees/` directory 2. CLAUDE.md preference (`grep -i "worktree.*director" CLAUDE.md`) 3. Ask user: `.worktrees/` (project-local, hidden) OR `~/.config/ring/worktrees/<project>/` (global) ```bash ls -d .worktrees worktrees 2>/dev/null ``` ## Safety Verification **Project-local directories only:** Verify `.gitignore` before creating: ```bash grep -q "^\.worktrees/$\|^worktrees/$" .gitignore ``` Not in `.gitignore` → add it → commit → proceed. (Prevents accidentally tracking worktree contents.) **Global directory** (`~/.config/ring/worktrees`): No verification needed. ## Creation Steps ```bash # 1. Detect project name project=$(basename "$(git rev-parse --show-toplevel)") # 2. Create worktree git worktree add "$path" -b "$BRANCH_NAME" && cd "$path" # 3. Auto-detect and run setup [ -f package.json ] && npm install [ -f Cargo.toml ] && cargo build [ -f requirements.txt ] && pip install -r requirements.txt [ -f pyproject.toml ] && poetry install [ -f go.mod ] && go mod download # 4. Verify clean baseline npm test / cargo test / pytest / go test ./... ``` **If tests fail:** Report failures, ask whether to proceed. **If tests pass:** Report: `Worktree ready at <path> | Tests passing (<N> tests) | Ready to implement <feature>` ## Quick Reference | Situation | Action | |-----------|--------| | `.worktrees/` exists | Use it (verify .gitignore) | | Both `.worktrees/` and `worktrees/` exist | Use `.worktrees/` | | Neither exists | Check CLAUDE.md → ask user | | Directory not in .gitignore | Add immediately + commit | | Tests fail during baseline | Report failures + ask | ## Non-Negotiables - Project-local directories MUST be in .gitignore before creation - Baseline test verification REQUIRED before proceeding with work - Directory selection MUST follow priority order - Dependency installation MUST run (auto-detect from project files) ## Integration Pairs with **finishing-a-development-branch** for cleanup and **ring:running-dev-cycle** for work.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.