framework_eng/rules/dap-bsl-debugger/SKILL.md
When the runtime path is unclear, enable BSL DAP debugging
npx skillsauth add steelmorgan/1c-agent-based-dev-framework dap-bsl-debuggerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Trigger: there is a reproducible BSL code execution scenario, and you need to see the actual stop in the procedure, the stack, variable values, or step-by-step execution. When triggered, apply the
dap-bsl-code-debug-procedureskill (framework/skills/tool-usage/diagnostics/dap-bsl-code-debug-procedure/SKILL.md).
Use the interactive debugger only when its benefit outweighs the risk of stopping execution. For productive or dangerous scenarios, first obtain a safe window/environment; if there is none, do not connect the debugger and use less invasive diagnostics.
GUARD: before finishing, make sure to remove all breakpoints, release the stopped thread, perform detach, and report that the debugger state has been cleared. If detach did not work or ibInDebug / a stuck debug session remains, perform force_detach and verify the targets again.
depends_on:
development
1C server maintenance webhooks: container restart and external component cache cleanup
development
Interactive DAP debugging of a single BSL procedure
tools
Rules for using RLM tools for project search and navigation in 1C/BSL
development
Creates web applications and routes on Winow (a web server on OneScript and Autumn). Use when working with a web server on OneScript, routing, or Winow controllers.