# Snapshot Env

> Capture a reproducible environment snapshot with exact tool versions, dependencies, git state, and system info. Use when user says 'snapshot my environment', 'capture env', 'save environment state', or before risky operations to enable reproduction.

- Skill: `hosaypeng/snapshot-env` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add hosaypeng/snapshot-env`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hosaypeng/snapshot-env/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: hosaypeng (https://skillmd.com/u/hosaypeng)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/hosaypeng/snapshot-env

---


# Environment Snapshot Task

## Objectives

Create a complete snapshot of the current environment so this agent run can be reproduced exactly.

## What to Capture

### 1. System Information
```json
{
  "system": {
    "os": "Darwin/Linux/Windows",
    "version": "OS version",
    "architecture": "x86_64/arm64",
    "hostname": "machine name",
    "user": "username"
  }
}
```

### 2. Tool Versions
Detect and record versions of:
- Python (`python --version`)
- Node.js (`node --version`)
- npm/yarn/pnpm
- Go (`go version`)
- Rust (`rustc --version`)
- Git (`git --version`)
- Docker (`docker --version`)
- Other relevant tools in PATH

### 3. Project Dependencies
Based on project type:
- **Python**: `requirements.txt` or `Pipfile.lock` or `poetry.lock`
- **Node.js**: `package-lock.json` or `yarn.lock` or `pnpm-lock.yaml`
- **Go**: `go.mod` and `go.sum`
- **Rust**: `Cargo.lock`

### 4. Environment Variables
Capture relevant env vars (excluding secrets):
- PATH
- SHELL
- LANG/LC_*
- *_VERSION variables
- Project-specific vars (ask user if unsure)

**Never capture**: passwords, API keys, tokens, credentials

### 5. Task Configuration
- Working directory
- Files involved
- Commands that were run
- Timestamp

### 6. Git Context (if in repo)
- Current branch
- Latest commit SHA
- Dirty/clean state
- Remote URL (without credentials)

## Output Format

Format both JSON and markdown snapshots per `~/.claude/skills/snapshot-env/references/snapshot_template.md`

## Process

1. **Detect Project Type**:
   - Scan working directory for project files
   - Identify languages and frameworks in use

2. **Gather System Info**:
   - Run system commands to get OS, arch, etc.
   - Record timestamp

3. **Capture Tool Versions**:
   - Check which tools are available
   - Record exact versions

4. **Extract Dependencies**:
   - Find lock files
   - Hash or include content
   - Note if dependencies are out of sync

5. **Capture Environment**:
   - Get env vars (sanitize secrets)
   - Record working directory

6. **Git Context**:
   - If in git repo, capture commit/branch
   - Note clean/dirty state

7. **Save Snapshots**:
   - Write JSON file
   - Write markdown file
   - Create README if needed

8. **Report to User**:
   - Show snapshot location
   - List what was captured
   - Note any warnings (dirty git state, missing tools, etc.)

## Acceptance Criteria

- Snapshot contains enough info to reproduce the environment
- Both JSON and markdown versions are created
- Secrets are not captured
- File hashes/checksums are included
- Timestamp is in ISO-8601 format
- User knows where to find the snapshot

## Constraints

- Never capture credentials, API keys, or secrets
- Sanitize environment variables
- Keep snapshot files in scratchpad only
- Make snapshots self-documenting
- Include warnings about non-reproducible state

## Troubleshooting

**Error: Tool not found (e.g., `node: command not found`)**
Cause: The tool isn't installed or isn't in the current PATH.
Fix: Record the tool as "not installed" in the snapshot instead of failing. Note it in the warnings section so the user knows the snapshot is incomplete for that tool.

**Error: Permission denied running version commands**
Cause: The tool binary exists but isn't executable, or requires elevated permissions.
Fix: Skip the tool and note the permission issue in the snapshot. Suggest the user check permissions with `ls -la $(which <tool>)`.

**Error: Scratchpad directory not writable**
Cause: Permissions or disk space prevent writing snapshot files.
Fix: Check with `df -h` and `ls -la`. Fall back to writing the snapshot to the current working directory or output it directly to the terminal.

Execute environment snapshot now.