.claude/skills/auto-claude-workspace/SKILL.md
Auto-Claude workspace and git worktree management. Use when reviewing changes, merging builds, managing branches, or understanding isolation strategy.
npx skillsauth add adaptationio/skrillz auto-claude-workspaceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Git worktree isolation, branch management, and merge operations.
Auto-Claude uses git worktrees for complete isolation:
project-root/
├── .git/ # Main git directory
├── src/ # Your project files
├── .auto-claude/ # Auto-Claude data
│ └── specs/ # Spec definitions
└── .worktrees/ # Isolated workspaces
└── auto-claude/
└── 001-feature/ # Feature worktree
├── src/ # Copy of project
└── ... # Changes made here
main (or your current branch)
└── auto-claude/{spec-name} # Isolated branch per spec
Key Principles:
cd apps/backend
# Review what was built
python run.py --spec 001 --review
Output shows:
# Navigate to worktree
cd .worktrees/auto-claude/001-feature/
# Run your project
npm run dev
# or
python manage.py runserver
# or your project's run command
# Test the feature
# ...
# Return to backend
cd ../../apps/backend
# Merge completed build into your project
python run.py --spec 001 --merge
This:
auto-claude/001-feature into current branch# Discard if you don't want the changes
python run.py --spec 001 --discard
This:
# Create new worktree
git worktree add .worktrees/experiment -b experiment-branch
# Work in it
cd .worktrees/experiment
# make changes...
# Return and cleanup
cd ../..
git worktree remove .worktrees/experiment
git worktree list
# Remove worktrees for deleted directories
git worktree prune
Auto-Claude uses AI to resolve merge conflicts:
If AI merge fails:
# Navigate to worktree
cd .worktrees/auto-claude/001-feature/
# Attempt manual merge
git merge main
# Resolve conflicts in your editor
code .
# Complete merge
git add .
git commit -m "Resolved merge conflicts"
# Return and complete
cd ../../apps/backend
python run.py --spec 001 --merge
# List all branches
git branch -a
# See auto-claude branches
git branch | grep auto-claude
# Delete local branch
git branch -d auto-claude/old-feature
# Delete remote branch (if pushed)
git push origin --delete auto-claude/old-feature
# Set default base branch in .env
echo "DEFAULT_BRANCH=develop" >> apps/backend/.env
# View worktree info
cat .auto-claude/specs/001-feature/worktree.json
{
"worktree_path": ".worktrees/auto-claude/001-feature",
"branch_name": "auto-claude/001-feature",
"base_branch": "main",
"created_at": "2024-01-01T10:00:00Z",
"status": "active"
}
Each worktree is completely isolated:
Review changes thoroughly
python run.py --spec 001 --review
Test in worktree
cd .worktrees/auto-claude/001-feature/
npm test
npm run build
Check for conflicts
git diff main...auto-claude/001-feature
Run full test suite
npm test
Verify functionality
npm run dev
# Test manually
Commit and push when ready
git push origin main
# List and remove old worktrees
git worktree list
git worktree remove .worktrees/auto-claude/old-feature
# Or use discard command
python run.py --spec old --discard
# Remove existing worktree
git worktree remove .worktrees/auto-claude/001-feature
# Retry build
python run.py --spec 001
# Delete existing branch
git branch -D auto-claude/001-feature
# Retry build
python run.py --spec 001
# Manual resolution
cd .worktrees/auto-claude/001-feature/
git merge main --no-commit
# Resolve each file
git status
code path/to/conflicted/file
# Complete
git add .
git commit
cd ../../apps/backend
# Remove and recreate
git worktree remove --force .worktrees/auto-claude/001-feature
git worktree prune
# Delete spec and restart
rm -rf .auto-claude/specs/001-feature
python spec_runner.py --task "Your task"
development
Setup secure web-based terminal access to WSL2 from mobile/tablet via ttyd + ngrok/Cloudflare/Tailscale. One-command install, start, stop, status. Use when you need remote terminal access, web terminal, browser-based shell, or mobile access to WSL2 environment.
development
Complete development workflows where Claude writes the code while Gemini and Codex provide research, planning, reviews, and different perspectives. Claude remains the main developer. Use for complex projects requiring expert planning and multi-perspective reviews.
development
Systematic progress tracking for skill development. Manages task states (pending/in_progress/completed), updates in real-time, reports progress, identifies blockers, and maintains momentum. Use when tracking skill development, coordinating work, or reporting progress.
testing
Comprehensive testing workflow orchestrating functional testing, example validation, integration testing, and usability assessment. Sequential workflow for complete skill testing from examples through scenarios to integration validation. Use when conducting thorough testing, pre-deployment validation, ensuring skill functionality, or comprehensive quality checks.