[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NSNBT6CZC8HFB9MZ2NJD2T":3,"skill-same:01M6NSNBT6CZC8HFB9MZ2NJD2T":88},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":13,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6NSNBT6CZC8HFB9MZ2NJD2T","debugging-code",null,"Interactively debug source code — set breakpoints, step through execution line by line, inspect live variable state, evaluate expressions against the running program, and navigate the call stack to trace root causes.","duc-duy-1612\u002FOnline-Delivery-Systems-Web","duc-duy-1612","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192231384?v=4","01M6NSDKQQDKVTHZ8DZMZ1VYY6","01M6NSDKW8DDVTQHBT1HBDDJPT",0,"MIT","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdebugging-code\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"debugging","code","debugging code","master","navigate","evaluate","inspect","tree","line","critical","call","community","github","stack","execution","SET","https","license","state","debug","2026-11-10 10:12:30",false,"---\nname: debugging-code\ndescription: \"Interactively debug source code — set breakpoints, step through execution line by line, inspect live variable state, evaluate expressions against the running program, and navigate the call stack to trace root causes.\"\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002FAlmogBaku\u002Fdebug-skill\u002Ftree\u002Fmaster\u002Fskills\u002Fdebugging-code\nsource_repo: AlmogBaku\u002Fdebug-skill\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002FAlmogBaku\u002Fdebug-skill\u002Fblob\u002Fmaster\u002FLICENSE\n---\n\n# Interactive Debugger\n## When to Use\n\nUse this skill when you need interactively debug source code — set breakpoints, step through execution line by line, inspect live variable state, evaluate expressions against the running program, and navigate the call stack to trace root causes. Use when a program crashes, raises unexpected exceptions, produces...\n\n\nUse when a program crashes, produces wrong output, or you need to understand exactly\nhow execution reached a particular state — and running it again with more print statements\nwon't give you the answer fast enough.\n\nYou can pause a running program at any point, read live variable values and the call stack\nat that exact moment, step forward line by line or jump to the next breakpoint, and\nevaluate arbitrary expressions against the live process — all without restarting.\n\n## Setup\n\nThis skill uses `dap`, a CLI tool that background daemon to interact with the debugger via the DAP Protocol, maintain\nthe debugger state, so you can simply interact with it with multiple calls.\n\nIf `dap` isn't installed (check: `command -v dap`), install it NOW.\nAsk\u002Fnotify the user before proceeding to install it.\n\nFrom Homebrew (macOS)\n\n```bash\nbrew install AlmogBaku\u002Ftap\u002Fdap\n```\n\nInstaller script:\n\n```bash\nbash scripts\u002Finstall-dap.sh\n```\n\nInstall from sources:\n\n```bash\ngo install github.com\u002FAlmogBaku\u002Fdebug-skill\u002Fcmd\u002Fdap@latest\n```\n\nThis tool is open-sourced and available on [GitHub](https:\u002F\u002Fgithub.com\u002FAlmogBaku\u002Fdebug-skill), maintained and follows\nbest practices.\n\nSupports natively Python, Go, Node.js\u002FTypeScript, Rust, C\u002FC++, and any other language that supports DAP.\n\nIf a debugger backend is missing or fails to start, see `references\u002Finstalling-debuggers.md`\n\nFor all commands and flags: `dap --help` or `dap \u003Ccmd> --help`.\n\n## Starting a Session\n\n`dap debug \u003Cfile>` launches the program under the debugger. Backend is auto-detected from the file extension.\n\nChoose your starting strategy based on what you know:\n\n- **Have a hypothesis** — set a breakpoint where you expect the bug: `dap debug script.py --break script.py:42`\n- **Conditional breakpoint** — only stop when a condition is met: `dap debug script.py --break \"script.py:42:x > 5\"` (\n  always quote specs with conditions)\n- **Multi-file app** — breakpoints across modules: `--break src\u002Fapi\u002Froutes.py:55 --break src\u002Fmodels\u002Fuser.py:30`\n- **No hypothesis, small program** — walk from entry: `dap debug script.py --stop-on-entry` (avoid for large projects —\n  startup code is noisy; bisect with breakpoints instead)\n- **Exception, location unknown** — `dap debug script.py --break-on-exception raised` (Python) \u002F `all` (Go\u002FJS)\n- **Remote process** — `dap debug --attach host:port --backend \u003Cname>`\n- **Process already running (stuck server, live issue)** — attach without restarting:\n  `dap debug --pid \u003CPID> --backend \u003Cname>`\n  > **macOS + Go gotcha:** `dlv --pid` requires SIP disabled (`csrutil disable`).\n  > Prefer starting the program under the debugger instead or attaching to a remote debugger!\n\n**Session isolation:** `--session \u003Cname>` keeps concurrent agents from interfering.\nTip: You might want to use your session id(${CLAUDE_SESSION_ID}) if available.\n\nRun `dap debug --help` for all flags, backends, and examples.\n\n## The Debugging Mindset\n\nReach for a debugger when reading source alone can't validate the root cause.\nA debugger lets you *observe* what *does* happen: actual values, actual path, actual state.\nWhen that diverges from what *should* happen, you've found your bug.\n\n**Two strikes, rethink.** If two hypotheses fail at the same location, your mental model is wrong.\nRe-read the code, form a *completely different* theory with different breakpoints.\n\n**Escalate gradually.** Start with `dap eval` to test a quick hypothesis. Use conditional breakpoints\nto filter noise. Fall back to full breakpoints + stepping only when you need interactive control.\n\n**Mimic the user journey.** If you're debugging a user flow, set breakpoints along the path you expect the code to take.\nIf you expected `compute()` to be called, but it never is, then the bug is in the caller — not `compute()`, but whatever\nwas supposed to call it.\n\n**Set breakpoints instead of prints.** When you feel the urge to print something, set a breakpoint instead.\n\n## Know Your State\n\nEvery `dap` execution command returns full context automatically: current location, source, locals, call stack, and\noutput. At each stop, ask:\n\n- Do the local variables have the values I expected?\n- Is the call stack showing the code path I expected?\n- Does the output so far reveal anything unexpected?\n\n**Trace causation up the stack.** If a value is wrong at frame 0, check `dap eval \"\u003Cexpr>\" --frame 1` to see what the\ncaller passed. Keep going up (`--frame 2`, `--frame 3`) until you find the frame where the value first became wrong —\nthat's the origin of the bug, not the symptom.\n\nExample output at a stop:\n\n```\nStopped at compute() · script.py:41\n  39:   def compute(items):\n  40:       result = None\n> 41:       return result\nLocals: items=[]  result=None\nStack:  main [script.py:10] → compute [script.py:41]\nOutput: (none)\n```\n\nIf the program exits before hitting your breakpoint:\n\n```\nProgram terminated · Exit code: 1\n```\n\n→ Move breakpoints earlier, or restart with `--stop-on-entry`.\n\n## Forming a Hypothesis\n\nBefore setting a breakpoint: *\"I believe the bug is in X because Y.\"* A good hypothesis is falsifiable — your next\nobservation will confirm or disprove it. No hypothesis yet? Bisect with two breakpoints to narrow the search space, or\nsee starting strategies above.\n\n## Setting Breakpoints Strategically\n\n- Set where the problem *begins*, not where it *manifests*\n- Exception at line 80? Root cause is upstream — start earlier\n- Uncertain? Bisect: `--break f:20 --break f:60` — wrong state before or after halves the search space\n\n**Where to break:**\n\n- **Boundaries** — where data crosses a format, representation, or module boundary; state is cleanest here\n- **State transitions** — the line that assigns or mutates the corrupted value\n- **Wrong branch** — the condition whose inputs led to the bad path\n- **Antipatterns** — don't break inside library code; break at the call site instead. Don't use unconditional breaks in\n  tight loops — use conditions.\n\n### Managing Breakpoints Mid-Session\n\nAs you learn more, add breakpoints deeper in the suspect code and remove ones that have\nserved their purpose — progressive narrowing without restarting:\n\n```bash\ndap continue --break app.py:50              # add breakpoint deeper, then continue\ndap continue --remove-break app.py:20       # drop a breakpoint you're done with\ndap break add app.py:42 app.py:60           # add multiple breakpoints at once\ndap break list                              # see what's set\ndap break clear                             # start fresh\n```\n\nIf a breakpoint is on an invalid line or the adapter adjusts it, `dap` warns you in the output.\n\n### Conditional Breakpoints\n\nStop only when a condition is true — essential for loops, hot paths, and specific input values.\nSyntax: `\"file:line:condition\"` (always quote).\n\n```bash\ndap debug app.py --break \"app.py:42:i == 100\"            # skip 99 iterations, stop on the one that matters\ndap debug app.py --break \"app.py:30:user_id == 123\"      # reproduce a user-specific bug\ndap continue --break \"app.py:50:len(items) == 0\"         # catch the empty-list case mid-session\n```\n\n### Invariant Breakpoints\n\nConditional breakpoints as runtime assertions — stop the *moment* something goes wrong:\n\n```bash\ndap debug app.py --break \"bank.py:68:balance \u003C 0\"          # catch the overdraft\ndap debug app.py --break \"pipe.py:30:type(val) != int\"     # type violation\n```\n\n## Navigating Execution\n\nAt each stop, choose how to advance based on what you suspect:\n\nIf you're stepping more than 3 times in a row, you need a breakpoint, not more steps.\n\n```bash\ndap step                         # step over — trust this call, advance to next line\ndap step in                      # step into — suspect what's inside this function\ndap step out                     # step out — you're in the wrong place, return to caller\ndap continue                     # jump to next breakpoint\ndap continue --to file:line      # run to line (temp breakpoint, auto-removed)\ndap context                      # re-inspect current state without stepping\ndap output                       # drain buffered stdout\u002Fstderr without full context\ndap inspect \u003Cvar> --depth N      # expand nested\u002Fcomplex objects\ndap pause                        # interrupt a running\u002Fhanging program\ndap restart                      # restart with same args and breakpoints\ndap threads                      # list all threads\ndap thread \u003Cid>                  # switch thread context\n```\n\nEach stop shows the current `file:line` so you always know where you are.\n\nUse `dap eval \"\u003Cexpr>\"` to probe live state without stepping:\n\n```bash\ndap eval \"len(items)\"\ndap eval \"user.profile.settings\"\ndap eval \"expected == actual\"       # test hypothesis on live state\ndap eval \"self.config\" --frame 1    # frame 1 = caller (may be a different file)\n```\n\nAvoid eval expressions that call methods with side effects — they mutate program state and can corrupt your debugging\nsession. Stick to read-only access unless you're intentionally testing a fix.\n\n## Skipping Ahead\n\nWhen you need a quick look at a specific line without committing to a permanent breakpoint, use\n`dap continue --to file:line`. It's a disposable breakpoint — stops once, then vanishes. Good for\n\"I just want to see what `x` looks like at line 50\" without managing breakpoint lifecycle.\n\n## Advanced Scenarios\n\nFor advanced scenarios — hangs, concurrency bugs, deeply nested state, loop bisection —\nsee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fadvanced-techniques.md`.\n\n## Walkthrough\n\n**Bug: `compute()` returns `None`**\n\n```\nHypothesis: result not assigned before return\n→ dap debug script.py --break script.py:41\n  Locals: result=None, items=[]   ← wrong, and input is also empty\n\nNew hypothesis: caller passing empty list\n→ dap eval \"items\" --frame 1      → []   ← confirmed\n→ dap step out                    → caller at line 10, no guard for empty input\n→ dap continue --break script.py:8 --remove-break script.py:41\n  ← narrowing: add breakpoint at data source, drop the one we're done with\n  Stopped at main():8, items loaded from config as []\n\nRoot cause: missing guard. Fix → dap stop.\n```\n\n**No hypothesis (exception, unknown location):**\n\n```\nException: TypeError, location unknown\n→ dap debug script.py --break-on-exception raised\n  Stopped at compute():41, items=None\nRoot cause: None passed where list expected.\n```\n\n## Verify Your Fix\n\nWhile paused at the bug, use `eval` to test your proposed fix expression against the live state. If it\nworks in eval, it'll work in code. Then edit and `dap restart` to confirm end-to-end.\n\nAfter applying a fix, re-run the same scenario to verify. `dap restart` re-runs with the same args and\nbreakpoints — a fast feedback loop. Don't trust that a fix works until you've observed the correct\nbehavior at the same breakpoint where you found the bug.\n\n## Cleanup\n\nThe `dap` session is usually automatically terminated when the program exits or after an idle timout.\nWhen the app is not closed properly (e.g. you killed it while debugging), you can terminate it manually: `dap stop`.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Interactive Debugger\n## When to Use\n\nUse this skill when you need interactively debug source code — set breakpoints, step through execution line by line, inspect live variable state, evaluate expressions against the running program, and navigate the call stack to trace root causes. Use when a program crashes, raises unexpected exceptions, produces...\n\n\nUse when a program crashes, produces wrong output, or you need to understand exactly\nhow execution reached a particular state — and running it again with more print statements\nwon't give you the answer fast enough.\n\nYou can pause a running program at any point, read live variable values and the call stack\nat that exact moment, step forward line by line or jump to the next breakpoint, and\nevaluate arbitrary expressions against the live process — all without restarting.\n\n## Setup\n\nThis skill uses `dap`, a CLI tool that background daemon to interact with the debugger via the DAP Protocol, maintain\nthe debugger state, so you can simply interact with it with multiple calls.\n\nIf `dap` isn't installed (check: `command -v dap`), install it NOW.\nAsk\u002Fnotify the user before proceeding to install it.\n\nFrom Homebrew (macOS)\n\n```bash\nbrew install AlmogBaku\u002Ftap\u002Fdap\n```\n\nInstaller script:\n\n```bash\nbash scripts\u002Finstall-dap.sh\n```\n\nInstall from sources:\n\n```bash\ngo install github.com\u002FAlmogBaku\u002Fdebug-skill\u002Fcmd\u002Fdap@latest\n```\n\nThis tool is open-sourced and available on [GitHub](https:\u002F\u002Fgithub.com\u002FAlmogBaku\u002Fdebug-skill), maintained and follows\nbest practices.\n\nSupports natively Python, Go, Node.js\u002FTypeScript, Rust, C\u002FC++, and any other language that supports DAP.\n\nIf a debugger backend is missing or fails to start, see `references\u002Finstalling-debuggers.md`\n\nFor all commands and flags: `dap --help` or `dap \u003Ccmd> --help`.\n\n## Starting a Session\n\n`dap debug \u003Cfile>` launches the program under the debugger. Backend is auto-detected from the file extension.\n\nChoose your starting strategy based on what you know:\n\n- **Have a hypothesis** — set a breakpoint where you expect the bug: `dap debug script.py --break script.py:42`\n- **Conditional breakpoint** — only stop when a condition is met: `dap debug script.py --break \"script.py:42:x > 5\"` (\n  always quote specs with conditions)\n- **Multi-file app** — breakpoints across modules: `--break src\u002Fapi\u002Froutes.py:55 --break src\u002Fmodels\u002Fuser.py:30`\n- **No hypothesis, small program** — walk from entry: `dap debug script.py --stop-on-entry` (avoid for large projects —\n  startup code is noisy; bisect with breakpoints instead)\n- **Exception, location unknown** — `dap debug script.py --break-on-exception raised` (Python) \u002F `all` (Go\u002FJS)\n- **Remote process** — `dap debug --attach host:port --backend \u003Cname>`\n- **Process already running (stuck server, live issue)** — attach without restarting:\n  `dap debug --pid \u003CPID> --backend \u003Cname>`\n  > **macOS + Go gotcha:** `dlv --pid` requires SIP disabled (`csrutil disable`).\n  > Prefer starting the program under the debugger instead or attaching to a remote debugger!\n\n**Session isolation:** `--session \u003Cname>` keeps concurrent agents from interfering.\nTip: You might want to use your session id(${CLAUDE_SESSION_ID}) if available.\n\nRun `dap debug --help` for all flags, backends, and examples.\n\n## The Debugging Mindset\n\nReach for a debugger when reading source alone can't validate the root cause.\nA debugger lets you *observe* what *does* happen: actual values, actual path, actual state.\nWhen that diverges from what *should* happen, you've found your bug.\n\n**Two strikes, rethink.** If two hypotheses fail at the same location, your mental model is wrong.\nRe-read the code, form a *completely different* theory with different breakpoints.\n\n**Escalate gradually.** Start with `dap eval` to test a quick hypothesis. Use conditional breakpoints\nto filter noise. Fall back to full breakpoints + stepping only when you need interactive control.\n\n**Mimic the user journey.** If you're debugging a user flow, set breakpoints along the path you expect the code to take.\nIf you expected `compute()` to be called, but it never is, then the bug is in the caller — not `compute()`, but whatever\nwas supposed to call it.\n\n**Set breakpoints instead of prints.** When you feel the urge to print something, set a breakpoint instead.\n\n## Know Your State\n\nEvery `dap` execution command returns full context automatically: current location, source, locals, call stack, and\noutput. At each stop, ask:\n\n- Do the local variables have the values I expected?\n- Is the call stack showing the code path I expected?\n- Does the output so far reveal anything unexpected?\n\n**Trace causation up the stack.** If a value is wrong at frame 0, check `dap eval \"\u003Cexpr>\" --frame 1` to see what the\ncaller passed. Keep going up (`--frame 2`, `--frame 3`) until you find the frame where the value first became wrong —\nthat's the origin of the bug, not the symptom.\n\nExample output at a stop:\n\n```\nStopped at compute() · script.py:41\n  39:   def compute(items):\n  40:       result = None\n> 41:       return result\nLocals: items=[]  result=None\nStack:  main [script.py:10] → compute [script.py:41]\nOutput: (none)\n```\n\nIf the program exits before hitting your breakpoint:\n\n```\nProgram terminated · Exit code: 1\n```\n\n→ Move breakpoints earlier, or restart with `--stop-on-entry`.\n\n## Forming a Hypothesis\n\nBefore setting a breakpoint: *\"I believe the bug is in X because Y.\"* A good hypothesis is falsifiable — your next\nobservation will confirm or disprove it. No hypothesis yet? Bisect with two breakpoints to narrow the search space, or\nsee starting strategies above.\n\n## Setting Breakpoints Strategically\n\n- Set where the problem *begins*, not where it *manifests*\n- Exception at line 80? Root cause is upstream — start earlier\n- Uncertain? Bisect: `--break f:20 --break f:60` — wrong state before or after halves the search space\n\n**Where to break:**\n\n- **Boundaries** — where data crosses a format, representation, or module boundary; state is cleanest here\n- **State transitions** — the line that assigns or mutates the corrupted value\n- **Wrong branch** — the condition whose inputs led to the bad path\n- **Antipatterns** — don't break inside library code; break at the call site instead. Don't use unconditional breaks in\n  tight loops — use conditions.\n\n### Managing Breakpoints Mid-Session\n\nAs you learn more, add breakpoints deeper in the suspect code and remove ones that have\nserved their purpose — progressive narrowing without restarting:\n\n```bash\ndap continue --break app.py:50              # add breakpoint deeper, then continue\ndap continue --remove-break app.py:20       # drop a breakpoint you're done with\ndap break add app.py:42 app.py:60           # add multiple breakpoints at once\ndap break list                              # see what's set\ndap break clear                             # start fresh\n```\n\nIf a breakpoint is on an invalid line or the adapter adjusts it, `dap` warns you in the output.\n\n### Conditional Breakpoints\n\nStop only when a condition is true — essential for loops, hot paths, and specific input values.\nSyntax: `\"file:line:condition\"` (always quote).\n\n```bash\ndap debug app.py --break \"app.py:42:i == 100\"            # skip 99 iterations, stop on the one that matters\ndap debug app.py --break \"app.py:30:user_id == 123\"      # reproduce a user-specific bug\ndap continue --break \"app.py:50:len(items) == 0\"         # catch the empty-list case mid-session\n```\n\n### Invariant Breakpoints\n\nConditional breakpoints as runtime assertions — stop the *moment* something goes wrong:\n\n```bash\ndap debug app.py --break \"bank.py:68:balance \u003C 0\"          # catch the overdraft\ndap debug app.py --break \"pipe.py:30:type(val) != int\"     # type violation\n```\n\n## Navigating Execution\n\nAt each stop, choose how to advance based on what you suspect:\n\nIf you're stepping more than 3 times in a row, you need a breakpoint, not more steps.\n\n```bash\ndap step                         # step over — trust this call, advance to next line\ndap step in                      # step into — suspect what's inside this function\ndap step out                     # step out — you're in the wrong place, return to caller\ndap continue                     # jump to next breakpoint\ndap continue --to file:line      # run to line (temp breakpoint, auto-removed)\ndap context                      # re-inspect current state without stepping\ndap output                       # drain buffered stdout\u002Fstderr without full context\ndap inspect \u003Cvar> --depth N      # expand nested\u002Fcomplex objects\ndap pause                        # interrupt a running\u002Fhanging program\ndap restart                      # restart with same args and breakpoints\ndap threads                      # list all threads\ndap thread \u003Cid>                  # switch thread context\n```\n\nEach stop shows the current `file:line` so you always know where you are.\n\nUse `dap eval \"\u003Cexpr>\"` to probe live state without stepping:\n\n```bash\ndap eval \"len(items)\"\ndap eval \"user.profile.settings\"\ndap eval \"expected == actual\"       # test hypothesis on live state\ndap eval \"self.config\" --frame 1    # frame 1 = caller (may be a different file)\n```\n\nAvoid eval expressions that call methods with side effects — they mutate program state and can corrupt your debugging\nsession. Stick to read-only access unless you're intentionally testing a fix.\n\n## Skipping Ahead\n\nWhen you need a quick look at a specific line without committing to a permanent breakpoint, use\n`dap continue --to file:line`. It's a disposable breakpoint — stops once, then vanishes. Good for\n\"I just want to see what `x` looks like at line 50\" without managing breakpoint lifecycle.\n\n## Advanced Scenarios\n\nFor advanced scenarios — hangs, concurrency bugs, deeply nested state, loop bisection —\nsee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fadvanced-techniques.md`.\n\n## Walkthrough\n\n**Bug: `compute()` returns `None`**\n\n```\nHypothesis: result not assigned before return\n→ dap debug script.py --break script.py:41\n  Locals: result=None, items=[]   ← wrong, and input is also empty\n\nNew hypothesis: caller passing empty list\n→ dap eval \"items\" --frame 1      → []   ← confirmed\n→ dap step out                    → caller at line 10, no guard for empty input\n→ dap continue --break script.py:8 --remove-break script.py:41\n  ← narrowing: add breakpoint at data source, drop the one we're done with\n  Stopped at main():8, items loaded from config as []\n\nRoot cause: missing guard. Fix → dap stop.\n```\n\n**No hypothesis (exception, unknown location):**\n\n```\nException: TypeError, location unknown\n→ dap debug script.py --break-on-exception raised\n  Stopped at compute():41, items=None\nRoot cause: None passed where list expected.\n```\n\n## Verify Your Fix\n\nWhile paused at the bug, use `eval` to test your proposed fix expression against the live state. If it\nworks in eval, it'll work in code. Then edit and `dap restart` to confirm end-to-end.\n\nAfter applying a fix, re-run the same scenario to verify. `dap restart` re-runs with the same args and\nbreakpoints — a fast feedback loop. Don't trust that a fix works until you've observed the correct\nbehavior at the same breakpoint where you found the bug.\n\n## Cleanup\n\nThe `dap` session is usually automatically terminated when the program exits or after an idle timout.\nWhen the app is not closed properly (e.g. you killed it while debugging), you can terminate it manually: `dap stop`.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":32,"source":48,"license":14,"date_added":49,"description":7,"source_repo":50,"source_type":34,"license_source":51},"https:\u002F\u002Fgithub.com\u002FAlmogBaku\u002Fdebug-skill\u002Ftree\u002Fmaster\u002Fskills\u002Fdebugging-code",1782864000000,"AlmogBaku\u002Fdebug-skill","https:\u002F\u002Fgithub.com\u002FAlmogBaku\u002Fdebug-skill\u002Fblob\u002Fmaster\u002FLICENSE","main","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills\u002Fdebugging-code","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612","2026-10-25 23:50:58",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill debugging-code",{"tool":64,"command":65},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill debugging-code",{"tool":67,"command":68},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill debugging-code","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdebugging-code\u002FSKILL.md",true,[72,78,82],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fadvanced-techniques.md","REFERENCE","参考文档",2021,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdebugging-code\u002Freferences\u002Fadvanced-techniques.md",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Finstalling-debuggers.md",2258,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdebugging-code\u002Freferences\u002Finstalling-debuggers.md",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Finstall-dap.sh","SCRIPT","脚本",2215,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdebugging-code\u002Fscripts\u002Finstall-dap.sh",[89,117,141,163,187,210],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":100,"publishedAt":43},"01M6Q0FA5FZ410Z33Z3TFQ4DBA","zero-trust","Implement zero-trust network architecture. Configure identity-based access, micro-segmentation, and continuous verification. Use when implementing modern security architectures.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzero-trust\u002FSKILL.md",[95],{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[101,102,103,104,105,106,91,107,108,109,110,111,34,52,112,32,113,114,115,116],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","only","active","scope","scripts","relevant","implementing",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":43},"01M6Q0F1YZJW3KX5FBKEVZ8CV4","zcode-delegate","Delegate coding tasks to the Z.AI ZCode CLI only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzcode-delegate\u002FSKILL.md",[],[124,125,126,127,128,129,130,131,132,133,134,135,136,111,137,34,138,139,32,140],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":43},"01M6Q0ETK41VGNMYEXW0T00AJN","youtube-transcript","Fetch YouTube transcripts through DeepAPI or local fallback tooling and save clean text output.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript\u002FSKILL.md",[],[148,149,150,151,35,152,153,40,39,154,155,156,157,34,52,158,159,160,161,162],"transcript","youtube transcript","youtube","safe","codex","research","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":176,"publishedAt":43},"01M6Q0EPPH2PVMDW40017F8WX0","youtube-transcript-skills","Fetch YouTube video transcripts, search videos\u002Fchannels, browse channels, and extract playlists via the getyoutubetranscript.com API - free tier, no card required.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript-skills\u002FSKILL.md",[169,172,175],{"categoryNo":170,"categoryName":171,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":173,"categoryName":174,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[148,149,150,177,151,178,35,152,40,179,180,181,182,155,183,34,52,184,185,186],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":197,"publishedAt":43},"01M6Q0EAB96PX83W5PTE8A0R8D","youtube-notetaker","Turn YouTube talks into local study notes with slides, transcripts, editable annotations, and a markdown-backed viewer.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-notetaker\u002FSKILL.md",[193,196],{"categoryNo":194,"categoryName":195,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":173,"categoryName":174,"taxonomyType":98,"taxonomyTypeDesc":99},[150,198,199,128,151,200,201,202,24,40,181,203,204,205,206,52,207,158,208,209],"youtube notetaker","notetaker","workflow","official","notes","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":217,"publishedAt":43},"01M6Q0E55F0GW5MX48V8HXS8B5","youtube-full","Fetch YouTube transcripts, search videos, browse channels, and extract playlists via TranscriptAPI — no yt-dlp, no Google API key, works from any cloud server.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-full\u002FSKILL.md",[216],{"categoryNo":170,"categoryName":171,"taxonomyType":98,"taxonomyTypeDesc":99},[218,150,219,220,151,178,179,221,222,180,181,182,155,223,183,34,52,184,224,161],"youtube full","full","google","server","dlp","credits","automatic"]