| name | environment-maintenance |
| description | Use when touching Docker, CI, dependencies, runtime compatibility, or repository-level development environment instructions. |
Environment Maintenance
Tool Commands
Use the command packet before applying this skill's workflow:
python3 tools/agent_tools/skill_tool_commands.py show --skill environment-maintenance --format text
Execute the required and task-matching conditional commands that the packet prints.
- Treat
CONTAINER_OPERATIONS.md as the source of truth for Dockerfile, docker/, .devcontainer/, validator, and Makefile target ownership. This skill is only the routing checklist.
- Update
docker/packs/*.toml, docker/codex-container-profiles.toml, and docker/python-execution-rules.toml when runtime selection behavior changes.
- When the main server host assumptions change, update
documents/server-host-contract.md and the server layout templates in the same change.
- Start from
agents/templates/environment_change_proposal.md when proposing a new repo-wide tool or dependency.
- Update dependency definitions and related docs in the same change.
- Check CI and local validation commands together.
- Use
CONTAINER_OPERATIONS.md, documents/coding-conventions-project.md, documents/github-first-module-and-devcontainer-policy.md, documents/tools/README.md, documents/server-host-contract.md, and docker/README.md.
- Do not canonize host-global installs as the repository default.
- Follow
CONTAINER_OPERATIONS.md when deciding whether a tool belongs in repo-local Dockerfile / docker/ or AgentCanon-owned .devcontainer/.
- Update mechanical enforcement in
tools/docker_dependency_validator.sh when the boundary changes.
- When environment or CI validation failure drives a repair, record the
validation-failure-response packet (
failing_contract, observation_level,
cause_classification, intent_preservation, and evidence) before
downscoping validation or weakening an oracle.
