ワンクリックで
python-debugpy
Debug Python with pdb, breakpoint(), post-mortem inspection, and debugpy remote attach.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Debug Python with pdb, breakpoint(), post-mortem inspection, and debugpy remote attach.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Adapt designs to work across different screen sizes, devices, contexts, or platforms. Ensures consistent experience across varied environments.
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy to create intentional compositions.
Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report of issues with severity ratings and recommendations.
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude realizes its knowledge is outdated or incorrect, (6) A better approach is discovered for a recurring task. Also review learnings before major tasks.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
| name | python-debugpy |
| description | Debug Python with pdb, breakpoint(), post-mortem inspection, and debugpy remote attach. |
| metadata | {"requires":{"bins":["python3"]}} |
Use when Python code needs interactive debugging: hidden locals, confusing state mutation, failing tests, subprocesses, long-running services, or remote/headless attach.
Pick the smallest debugger that reaches the bad frame.
breakpoint(): local code, source edits ok, fastest path.python3 -m pdb: no source edit, launch from the beginning.python3 -m pdb -c continue: stop at an unhandled exception.debugpy: remote/headless process, DAP client, already-running PID, or service startup race.python3 -m pdb path/to/script.py arg1
python3 -m pdb -c continue path/to/script.py
python3 -c "import debugpy" || python3 -m pip install debugpy
python3 -m debugpy --listen 127.0.0.1:5678 --wait-for-client path/to/script.py
python3 -m debugpy --listen 127.0.0.1:5678 --wait-for-client -m package.module
python3 -m debugpy --listen 127.0.0.1:5678 --pid <pid>
For source-edit attach:
import debugpy
debugpy.listen(("127.0.0.1", 5678))
debugpy.wait_for_client()
debugpy.breakpoint()
For post-mortem:
import pdb, sys
try:
run()
except Exception:
pdb.post_mortem(sys.exc_info()[2])
raise
n, s, r, c, q.w, u, d, a, l, ll.p expr, pp expr, display expr.b file.py:42, b func, b file.py:42, condition, cl <num>.!statement; full REPL: interact.debugpy in the active env; do not add it as a project dependency unless the project already wants it.127.0.0.1; do not expose 0.0.0.0 unless isolated or tunnelled.debugpy --pid as injection; avoid security-sensitive or production targets unless explicitly approved.rg -n 'breakpoint\\(|pdb\\.set_trace|debugpy\\.' --type py.PYTHONBREAKPOINT=0 disables breakpoint().