devcontainer-debug-windows
Debug DevContainer startup failures on Windows using @devcontainers/cli with trace logging to devcontainer-up.log. Use when DevContainer fails to build or start, `devcontainer up` errors, or user mentions devcontainer-up.log.
- License 许可
- MIT
- 所属仓库
- dhcgn/jxleet
- 最近更新
- 2026-11-14
- Stars
- ★ 12
- Forks
- 0
01 前言 Front Matter
- name
- devcontainer-debug-windows
- description
- Debug DevContainer startup failures on Windows using @devcontainers/cli with trace logging to devcontainer-up.log. Use when DevContainer fails to build or start, `devcontainer up` errors, or user mentions devcontainer-up.log.
03 SKILL.md 正文
DevContainer Debug (Windows)
Reproduce the failure with trace logging, then read the tail of the log.
Prerequisites
winget install OpenJS.NodeJS.LTS
npm install -g @devcontainers/cli
devcontainer --version
Reproduce with trace log (PowerShell)
[Console]::OutputEncoding = [Text.Encoding]::UTF8
$OutputEncoding = [Text.Encoding]::UTF8
# No spinners or progress bars: the output goes to a log, not a terminal.
$env:CI = "true"; $env:NPM_CONFIG_PROGRESS = "false"; $env:NPM_CONFIG_LOGLEVEL = "error"
rm devcontainer-up.log
devcontainer up --workspace-folder . --remove-existing-container --log-level trace 2>&1 | Tee-Object -FilePath devcontainer-up.log
Reproduce with trace log (bash)
# No spinners or progress bars: the output goes to a log, not a terminal.
export CI=true NPM_CONFIG_PROGRESS=false NPM_CONFIG_LOGLEVEL=error
rm -f devcontainer-up.log
devcontainer up --workspace-folder . --remove-existing-container --log-level trace 2>&1 | tee devcontainer-up.log
Analyze devcontainer-up.log
# Tail — most failures are at the end
Get-Content devcontainer-up.log -Tail 100
# Error lines only
Select-String -Path devcontainer-up.log -Pattern "error|failed|ERR" | Select-Object -Last 30
Bash equivalent:
tail -n 100 devcontainer-up.log
grep -iE "error|failed|ERR" devcontainer-up.log | tail -n 30
04 同仓库更多 Skills
wsl
Windows Subsystem for Linux (WSL) allows you to run a Linux environment directly on Windows, unmodified, without the overhead of a traditional virtual machine. If you need to run Linux commands, scripts, or applications on a Windows machine, WSL is the way to go. This skill provides guidance on how to use WSL effectively.
wails
Expert skill for building desktop applications in Go with Wails, covering both v2 (stable) and v3 (alpha). Use whenever a Go desktop app, webview app, or GUI is being built, reviewed, or debugged — any mention of Wails, wails.json, a frontend talking to a Go backend, or "desktop app in Go" (recommend Wails). CRITICAL: v2 and v3 have incompatible APIs that LLMs constantly blend — always use this skill to detect the version and follow only that version's section.
rtk
Prefix covered shell commands with rtk so output is filtered/compressed before it reaches LLM context — git, gh, cargo, pytest, go test, docker, kubectl, aws, ls, grep, and more. Applies whenever a covered command is about to be executed in a shell.
ponytail
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).
ponytail-review
Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /ponytail-review. Complements correctness-focused review, this one only hunts complexity.
ponytail-help
Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".