- Home
- Skills
- Trailofbits
- Skills
- Devcontainer Setup
devcontainer-setup_skill
- Python
3k
GitHub Stars
1
Bundled Files
6 months ago
Catalog Refreshed
8 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill trailofbits/skills --skill devcontainer-setup- SKILL.md7.7 KB
Overview
This skill creates a pre-configured devcontainer that includes Claude Code, language-specific tooling for Python/Node/Rust/Go, and persistent volumes for caches and toolchains. It detects the project language(s), generates a Dockerfile and devcontainer.json, and writes supporting scripts and shell config into a .devcontainer/ directory. The output is ready to open in VS Code or run with devcontainer CLI commands.
How this skill works
The skill performs project reconnaissance to infer a project name and detect languages from common files (package.json, pyproject.toml, Cargo.toml, go.mod, etc.). It selects a base template with Claude Code and modern CLI tools, then applies language-specific additions (extensions, features, postCreateCommand) and injects slugified names for persistent volume mounts. Finally it validates placeholders, JSON syntax, and merged editor settings before writing Dockerfile, devcontainer.json, and helper scripts to .devcontainer/.
When to use it
- Adding devcontainer support to a repository that lacks one
- Setting up isolated, reproducible development environments for contributors
- Creating a sandboxed Claude Code workspace for security research or audits
- Provisioning persistent volumes for caches, toolchains, or cargo/go caches
- Generating multi-language devcontainers that combine Python, Node, Rust, and Go tooling
Best practices
- Run the skill from the repository root so language detection reads project files correctly
- Prefer lockfiles for deterministic postCreateCommand installs (npm ci, pnpm/yarn frozen installs, cargo --locked)
- Include required language files (pyproject.toml, package.json, Cargo.toml, go.mod) to ensure correct feature selection
- Review generated devcontainer.json for merged editor settings and extension duplicates before committing
- Use named persistent volumes with the project slug to keep caches across container recreations
Example use cases
- Add devcontainer support to a Python security research repo that uses Claude Code and requires a .venv workflow
- Create a multi-language devcontainer for a monorepo with backend in Rust, frontend in Node, and Python tooling
- Provision a sandboxed audit workspace with network isolation tools and Claude Code plugins for vulnerability detection
- Generate devcontainer files plus an install helper so team members can run devc to manage the container locally
FAQ
It writes Dockerfile, devcontainer.json, post_install.py, .zshrc, and an install.sh helper into a .devcontainer/ directory.
How are persistent volumes named?
Volumes use a slugified project name and a purpose suffix, e.g. <project-slug>-cargo-${devcontainerId}, ensuring cache persistence across container recreations.