claude-runtime-debug
Skill65 starsChanged 5 months agoNo licenceView on GitHub
This skill should be used when the user asks to diagnose Claude Code CLI/runtime behavior, including “运行时调试”, “命令输出不一致”, “退出码”, “debug log”, or “InteractiveTerminal 快速复现”. It covers --print, stdout/stderr, exit codes, --debug/--debug-file, non-network settings parity, output formats, hooks, and focused single-process PTY/TUI smoke checks. Use claude-network-debug for proxy/OAuth/network/MITM, claude-source-binary-analysis for static extraction, and claude-agent-workflow-validation for strict Agent/Workflow lifecycle or pane evidence.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- claude-agent-workflow-validationSkill
- claude-code-feature-validationSkill
- claude-network-debugSkill
- claude-source-binary-analysisSkill
- fork-binary-testingSkill
- fork-pr-flowSkill
- fork-release-wikiSkill
- multiturn-parity-sweepSkill
- release-validationSkill
The file
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.