Menu
Use this skill when working with Dev Containers, devcontainer.json, or Dev Container CLI for setup, review, validation, or troubleshooting.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Audit the structural and logical integrity of a mathematics paper โ quantifier scope, domain-of-definition guards, proof/computation honesty, theorem hierarchy, contribution-list discipline (mapping every claimed contribution to its formal result, prior baseline, concrete gain, and independent significance), stale claims, notation accuracy at introduction, standing assumptions, and undefined relation symbols or coined terms in summary prose โ without touching prose style or rhetorical prose inflation (structural inflation of contribution lists and result hierarchy is in scope).
Audit a LaTeX mathematics document for notation drift โ symbols used under different names across sections, orphaned macros, undeclared aliases (including cross-language pairs where a term defined in one language is later used in another), symbols or relation signs used with no definition site anywhere, symbol reuse across scopes, and first-use-after-gap without back-reference โ without evaluating mathematical correctness or prose style.
Review or rewrite mathematical prose so an edit, paraphrase, terminology migration, or explanatory description preserves the exact mathematical meaning fixed by its semantic source โ referent identity, operation versus result, domain/codomain and representation level, quantifier and equality mode, role and provenance, notation role, and classified-before-replacement terminology migration with concept-cluster synchronization โ without auditing claim-versus-proof strength (use math-claim-integrity), notation bookkeeping (use math-notation-consistency), Japanese style or translation events (use wabun-math-style), or audience prerequisites and ordering (use exposition-flow).
Detect and correct Japanese-language anti-patterns in mathematical writing โ epistemic hedges weakening proved claims, incorrect verb tense, passive/active confusion in proofs, ambiguous particles, unjustified ๆใใ, decorative connectives, redundant meta-discourse, double negation, stacked ใฎ, generic/general conflation, borrowed non-mathematical vocabulary, vague category names for explicit formulas, full-width semicolons or untranslated English, canonical-terminology drift, and translation-level concept conflation โ without evaluating mathematical correctness or structural hierarchy.
Turn repository-grounded source material into a self-contained, audience-admissible document or presentation by modelling the intended audience, extracting information units with explicit discourse roles, and enforcing dependency-ordered exposition in which every load-bearing statement follows the prerequisites needed to interpret it โ without factual verification or citation checking (use sot-integrity), prose polishing (use deslop-prose), mathematical-correctness review (use the mathematical-writing skills), or typography and slide layout.
Workspace-level Git cleanup โ discover repositories under the current directory and prune merged branches, merged linked worktrees, stale remote-tracking refs, and stale worktree metadata.
| name | devcontainer-cli |
| description | Use this skill when working with Dev Containers, devcontainer.json, or Dev Container CLI for setup, review, validation, or troubleshooting. |
Use this skill when a task involves .devcontainer/, devcontainer.json, Dev Container Features/Templates, or Dev Container CLI commands.
devcontainer.json.devcontainer/ contents, referenced Docker/Compose files, and lifecycle scripts as the current implementation; treat the official specification and CLI behaviour as the correctness authority when editor defaults disagree..devcontainer/, Dockerfile, Compose files, and referenced scripts before editing..devcontainer/ contents, referenced Docker/Compose files, and lifecycle scripts only when needed for the task.image for simple reusebuild for project-specific toolingdockerComposeFile for multi-service environmentsonCreateCommand, updateContentCommand, or postCreateCommand; keep postStartCommand and postAttachCommand lightweight, idempotent, and fast.remoteUser and containerUser carefully, especially for Linux bind-mount permissions.Use CLI validation when the task requires runtime verification and the environment has Dev Container CLI, Docker/Compose access, and approval for execution steps.
devcontainer read-configuration --workspace-folder <repo>devcontainer build --workspace-folder <repo>devcontainer up --workspace-folder <repo>devcontainer exec --workspace-folder <repo> <cmd>devcontainer run-user-commands --workspace-folder <repo>If runtime validation cannot run, complete a static review and state exactly which validation steps remain unverified.
When reviewing or authoring a Dev Container, check:
Check in roughly this order:
Provide: