Devcontainer
Wire up DevContainers / GitHub Codespaces — `devcontainer.json`, container images, secrets, VS Code features, port forwarding. NOT for tuning Copilot itself (use `copilot-config`).From its SKILL.md
npx -y skills add event4u-app/agent-config --skill devcontainerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 19 stars19 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
4.4 KB, 921 tokens by cl100k_base, as published. Nobody here has run it
devcontainer
When to use
Use this skill when working with DevContainer configuration, GitHub Codespaces setup, or development environment standardization.
Do NOT use when:
- Local Docker setup without Codespaces (use
dockerskill) - Production deployment (use
aws-infrastructureskill)
Procedure: Modify DevContainer
- Gather context — read
.devcontainer/devcontainer.json, check.devcontainer/for env files and docs, checkagents/overrides/skills/devcontainer.mdfor project-specific overrides. - Identify change type — classify: image change, feature addition, secret addition, extension change, or env var change.
- Make the change — edit
devcontainer.json(or related files). Follow conventions below for secrets, features, and environment variables. - Build and verify — run
devcontainer buildto confirm the container builds. Check that extensions load and ports forward correctly. - Document — if adding a new secret or dependency, update the onboarding docs in
.devcontainer/.
Architecture
Custom image
DevContainers typically use a pre-built custom image hosted on a container registry (GHCR, ECR, Docker Hub). Read devcontainer.json for the image URL.
The image should include:
- Language runtime (PHP, Node.js, Python, etc.)
- Package managers (Composer, npm, etc.)
- Common development tools
Features (installed on top of the image)
Common features:
| Feature | Purpose |
|---|---|
git | Git version control |
github-cli | GitHub CLI (gh) for API access |
docker-in-docker | Run Docker inside the DevContainer |
Secrets management
Secrets can be managed via:
- File mounts:
.devcontainer/.secrets/<NAME>→/run/secrets/<NAME> - GitHub Codespaces secrets: configured in the repository settings
- Environment variables: in
.devcontainer/devcontainer.env
Read devcontainer.json for the actual secret definitions and requirements.
Workspace
- Workspace folder: typically
/workspaceor/workspaces/{repo-name} - Mount type: bind mount from local workspace
- Container name and hostname: defined in
devcontainer.json
IDE integration
- VS Code Live Share for collaborative development
- IDE extensions can be pre-configured in
devcontainer.json
Conventions
Adding new secrets
- Add the secret definition to
devcontainer.json→secretssection. - Add a bind mount from
.devcontainer/.secrets/<NAME>to/run/secrets/<NAME>. - Document the secret with
descriptionanddocumentationUrl. - Mark as required or optional.
Modifying the base image
- If the base image is maintained in a separate repository, do NOT change the image tag without coordination.
- Prefer adding features over modifying the base image.
Environment variables
- Runtime env vars go in
.devcontainer/devcontainer.env. - Secrets go in
.devcontainer/.secrets/(gitignored). - Do NOT hardcode secrets in
devcontainer.json.
Output format
- Updated devcontainer.json or related configuration files
- Summary of changes and rebuild requirements
Auto-trigger keywords
- DevContainer
- Codespaces
- dev environment
- container setup
Validate
- Verify the DevContainer builds successfully (
devcontainer build). - Confirm all required extensions and features are installed.
- Check that port forwarding and volume mounts work as expected.
Gotcha
- DevContainer rebuilds are slow — test configuration changes incrementally, not all at once.
- Secrets in devcontainer.json are visible in version control — use Codespaces secrets instead.
- Extensions in devcontainer.json install on EVERY rebuild — keep the list short.
Do NOT
- Do NOT commit secret files — they should be gitignored.
- Do NOT change the workspace mount path without updating all related configs.
- Do NOT remove required secrets without checking which services depend on them.
- Do NOT switch base images without team approval.
Related
- Skill:
docker— Docker setup, multi-stage Dockerfile, compose services - Skill:
traefik— local reverse proxy with real domains and HTTPS - Rule:
docker-commands.md— commands run inside Docker
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.