Skip to content

Guide agents to debug before adding temporary logs - #129

Merged
Oz Zafar (ozzafar) merged 1 commit into
microsoft:mainfrom
ozzafar:ozzafar/issue-5-trigger-debug-skill
Aug 19, 2026
Merged

Guide agents to debug before adding temporary logs#129
Oz Zafar (ozzafar) merged 1 commit into
microsoft:mainfrom
ozzafar:ozzafar/issue-5-trigger-debug-skill

Conversation

@ozzafar

Copy link
Copy Markdown
Contributor

Summary

  • improve debug-live skill discovery for runtime bugs, failing tests, exceptions, crashes, hangs, wrong values, and unexpected output
  • direct agents to use live debugger inspection instead of adding temporary logs, print statements, or console output
  • explain in MCP initialization instructions why debug-live should be invoked first: it provides breakpoint strategy, step-and-inspect workflow, and root-cause guidance
  • distinguish debugger logpoints from source-code logging for hot or timing-sensitive paths

Validation

pm run compilen- pm run lintn-
pm test (136 passing)

Improve debug-live discovery and instruct runtime investigations to load its breakpoint and root-cause workflow before adding temporary source-code logs.\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>\nCopilot-Session: 32ca52f0-95b2-4ab4-8de8-cc870a9df789
@ozzafar
Oz Zafar (ozzafar) force-pushed the ozzafar/issue-5-trigger-debug-skill branch from 32369c2 to 1f22d03 Compare August 18, 2026 18:56
@ozzafar
Oz Zafar (ozzafar) merged commit 1f22d03 into microsoft:main Aug 19, 2026
3 of 6 checks passed
Matthias Hertel (MatthiasHertelArm) pushed a commit to MatthiasHertelArm/CMSIS-Developer-Assistant that referenced this pull request Aug 20, 2026
Port of microsoft/DebugMCP#129, in embedded flavour. The skill description
gains the trigger vocabulary (runtime bugs, faults, crashes, hangs, failing
tests, wrong/null values, unexpected output) and a debugger-first rule: do
not start a runtime investigation by adding printf over UART/ITM, LED
toggles or trace macros - on a Cortex-M that is a rebuild, reflash and
reset per hypothesis and it moves the timing you are observing. Halt and
inspect instead; add_logpoint only knowing it still stops the core per hit.

The MCP server now sends instructions at initialize pointing at the
cmsis-debug-live skill (and at get_debug_instructions for harnesses that do
not load skills), start_debugging says the same in one sentence, and the
get_debug_instructions guide carries the same rule so the two stay
consistent.
Sourabh Mehta (soumeh01) pushed a commit to Open-CMSIS-Pack/CMSIS-Developer-Assistant that referenced this pull request Aug 21, 2026
Port of microsoft/DebugMCP#129, in embedded flavour. The skill description
gains the trigger vocabulary (runtime bugs, faults, crashes, hangs, failing
tests, wrong/null values, unexpected output) and a debugger-first rule: do
not start a runtime investigation by adding printf over UART/ITM, LED
toggles or trace macros - on a Cortex-M that is a rebuild, reflash and
reset per hypothesis and it moves the timing you are observing. Halt and
inspect instead; add_logpoint only knowing it still stops the core per hit.

The MCP server now sends instructions at initialize pointing at the
cmsis-debug-live skill (and at get_debug_instructions for harnesses that do
not load skills), start_debugging says the same in one sentence, and the
get_debug_instructions guide carries the same rule so the two stay
consistent.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant