🧰
DevOpsHTML

Capture Environment

by pedrohcgs

Capture Environment is a DevOps skill for Claude Code, published by pedrohcgs in claude-code-my-workflow.

1.5K stars2.9K forkson pedrohcgs/claude-code-my-workflowAdded 2026/08/19+1% in starsRepository updated 2026/06/10
academic-writingcausal-inferenceclaude-codeclaude-code-skillseconometricseconomicslatexquartoreproducible-researchresearch-workflow
Install in seconds
Install Capture Environment
Copy Capture Environment into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/pedrohcgs/claude-code-my-workflow/tree/main/.claude/skills/capture-environment ~/.claude/skills/capture-environment

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/pedrohcgs/claude-code-my-workflow.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
.claude/skills/capture-environment/SKILL.md in pedrohcgs/claude-code-my-workflow
Installs to
~/.claude/skills/capture-environment
Collection
One of 25 skills cataloged from this repository
Category
DevOps798 skills

What Capture Environment does

Capture Environment snapshots a project’s software stack for a replication package, including language versions, package locks, seeds, and RNG settings. Use it before releasing or handing off analysis code so others can rebuild the same environment.

Capture Environment is cataloged under DevOps on DirSkills. Capture Environment comes from a repository tagged academic-writing, causal-inference, claude-code, claude-code-skills and econometrics.

Documentation

README

/capture-environment — snapshot the computational environment

A replication package that runs on the author's laptop in 2026 and nowhere else in 2029 is not reproducible. This skill captures the exact computational environment — language versions, package versions, seeds, RNG kind, and (optionally) the OS layer — so a referee, the AEA Data Editor, or future-you can reconstruct it. It detects which stack the project uses and emits the artifacts that stack's ecosystem expects, then verifies the lockfile installs clean.

This is the opening of the README. Read the full README on GitHub.

Commands Capture Environment provides

Slash commands named in this skill’s SKILL.md, listed in the order they first appear.

  • /capture-environment
  • /audit-reproducibility
  • /commit
  • /data-analysis
  • /stata-replication
  • /simulation-study

Frequently asked about Capture Environment

  • What else does pedrohcgs publish alongside Capture Environment?

    Capture Environment is one of 25 skills that DirSkills catalogs from pedrohcgs/claude-code-my-workflow, the repository it ships in. Its siblings there include Audit Reproducibility, Checkpoint and Coauthor Brief. Each one is a separate skill with its own page in this directory, installs the same way Capture Environment does, and is maintained by pedrohcgs in that same repository. The rest of the collection is listed on the pedrohcgs/claude-code-my-workflow page.

  • How does Capture Environment compare to other DevOps skills?

    Capture Environment ranks #331 by stars among the 798 DevOps skills in this catalog. The most-starred ones next to it are Backend Patterns, API Connector Builder and Migration. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Capture Environment against them. Open each page to compare what they document and how they install.

More from pedrohcgs/claude-code-my-workflow

Capture Environment is one of 25 skills cataloged on DirSkills from pedrohcgs/claude-code-my-workflow.

See all 25 skills
🔍
2w ago

Audit Reproducibility

Audit Reproducibility compares numeric claims in a manuscript against actual analysis outputs and reports PASS/FAIL per claim against tolerance thresholds. Use it before submission, before releasing a replication package, or after a major revision to catch mismatches between the paper and the code.
Quality
1.5K2.9K
📌
2w ago

Checkpoint

Checkpoint saves a structured state snapshot before stopping or handing off, capturing the active plan, recent decisions, file pointers with line numbers, open questions, and next actions. Use it before a break, model switch, or collaborator handoff when you need to resume quickly.
AI Engineering
1.5K2.9K
🤝
2w ago

Coauthor Brief

Coauthor Brief generates a Markdown handoff brief for co-authors or future selves, summarizing git changes, artifact status, open questions, and local reproduction steps. Use it when onboarding a collaborator, sending a co-author the repo, or doing a periodic sync.
Automation
1.5K2.9K
🚀
2w ago

Commit, PR, and Merge

Commit, PR, and Merge stages changes, verifies quality gates, commits with a descriptive message, creates a pull request, and merges to main when the user explicitly asks to commit or ship changes.
Automation
1.5K2.9K
📄
2w ago

Compile Beamer LaTeX Slides

Compile Beamer LaTeX Slides compiles Beamer LaTeX slide decks using XeLaTeX with a 3-pass build sequence (xelatex, bibtex, xelatex twice). Use it when the user asks to compile, build slides, rebuild PDF, run latex, or render tex files in Slides/*.tex.
Automation
1.5K2.9K
🗜️
2w ago

Compress Session

Compress Session distills the current Claude Code conversation into a structured note (decisions made, open questions, file pointers, next 1–3 actions) saved to quality_reports/session_logs/ before auto-compaction truncates context. Use when context is approaching the auto-compact threshold, after long pipelines, or when the user asks to compress or distill the session.
AI Engineering
1.5K2.9K