DevOps Bootstrap Manager
Overview
This skill automates the complete environment setup and dependency initialization workflow for development projects. It handles toolchain verification, package management, and environment validation across multiple technology stacks.
Supported Environments
- Rust: Cargo-based projects with automatic dependency resolution
- Node.js: npm/yarn/pnpm package installation
- Python: pip/pipenv/poetry environment setup
- Go: Module initialization and vendor management
Usage
Invoke this skill when cloning or checking out a new repository to prepare the local development environment. The skill will detect the project type and execute the appropriate initialization sequence.
Procedure
The bootstrap process follows these steps in order:
- Repository Analysis
- Detect project type by scanning for manifest files (Cargo.toml, package.json, requirements.txt, go.mod)
- Identify required toolchain versions
- Validate directory structure
Dependency Installation
- For Rust projects: Execute
cargo checkto fetch and validate dependencies - For Node.js projects: Run appropriate package manager install command
- For Python projects: Set up virtual environment and install packages
- For Go projects: Execute
go mod downloadand verify modules
- For Rust projects: Execute
Toolchain Verification
- Confirm required compiler/interpreter versions are installed
- Check for compatibility issues with project requirements
- Report any missing or outdated tools
Environment Validation
- Run basic sanity checks (build test, import test, etc.)
- Verify environment variables are properly configured
- Test that critical paths and resources are accessible
Session Ready Notification
- Display repository path
- Show command to start development session
- Print any project-specific setup notes or warnings
Configuration
Environment Variables
The skill respects standard environment configuration:
CARGO_HOME: Rust package cache locationNODE_ENV: Node.js environment modeVIRTUAL_ENV: Python virtual environment pathGOPATH: Go workspace directory
Custom Initialization Hooks
Projects can define custom bootstrap scripts that will be detected and executed:
.claude/setup.sh: Shell script run after dependency installation.claude/bootstrap.json: Configuration overrides for initialization behavior
Safety Constraints
- Never remove existing worktrees without explicit user confirmation
- Scope all filesystem operations to the target repository directory
- Do not modify global toolchain installations or system configuration
- Preserve existing environment variable settings unless overridden by project config
Troubleshooting
Issue: Dependency installation fails with network errors
- Solution: Check internet connectivity and package registry availability. Consider using local mirrors or cached dependencies.
Issue: Toolchain version mismatch detected
- Solution: Update local toolchain to match project requirements, or use version managers (rustup, nvm, pyenv) to install correct versions.
Issue: Permission denied during setup
- Solution: Verify write permissions in the repository directory and package cache locations.
Examples
Example 1: Rust Project Bootstrap
# User provides repo path
Repository: [REDACTED_ABSOLUTE_PATH]
# Skill executes:
cd [REDACTED_ABSOLUTE_PATH] && cargo check
# Output:
✓ Rust toolchain verified (rustc 1.75.0)
✓ Dependencies resolved (45 crates)
✓ Build check passed
Ready to start session:
cd [REDACTED_ABSOLUTE_PATH] && claude
Example 2: Multi-Stack Monorepo
# Repository contains both Rust backend and Node.js frontend
Repository: [REDACTED_ABSOLUTE_PATH]
# Skill detects both environments and initializes:
- Backend: cargo check
- Frontend: npm install
# Validates both environments are ready
Related Skills
dependency-updater: Manage and upgrade project dependenciestoolchain-manager: Install and configure development toolchainsworkspace-initializer: Set up multi-project workspaces
Best Practices
- Run immediately after git clone to ensure environment consistency
- Re-run after switching branches if dependencies have changed
- Combine with CI/CD pipelines for automated environment preparation
- Document project-specific requirements in README or setup scripts
- Use lockfiles (Cargo.lock, package-lock.json) for reproducible builds