- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add microsoft/win-dev-skills --skill windbg-diagnostic-method -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add microsoft/win-dev-skills --skill windbg-diagnostic-method -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add microsoft/win-dev-skills --skill windbg-diagnostic-method -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add microsoft/win-dev-skills --skill windbg-diagnostic-method -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/microsoft/win-dev-skills/tree/HEAD/plugins/windbg/skills/windbg-diagnostic-method게시자 제공
Apply this method alongside the bug-family-specific skill selected for an investigation. Pattern matches route the investigation; they do not prove the root cause.
Prefer direct evidence in this order:
Never claim commands, source access, or artifacts that are unavailable in the session.
.exr -1, .ecxr, stack, and registers..bugcheck, !analyze -v, then documented context/trap
recovery for that code.candidate-pending-verification.These are the complete bug-family routes. Continue evidence-led reasoning for unsupported families; never dispatch to an absent skill.
Confidence is explanatory judgment, not measured probability.
candidate-pending-verification, set the
fix to null or a verification plan, and name the evidence/fix matrix needed.MODULE_NAME.Diagnosis confidence and fix confidence are separate. Every proposed fix must
declare fix_confidence and one fix_code_path_coverage value:
Lower confidence is always allowed when evidence quality, path coverage, or alternatives warrant it. Never raise confidence to fit the table.
Before finalizing a full diagnosis:
contrarian
agent once with the complete proposed diagnosis.CHALLENGED, test the counter-hypothesis with direct
evidence, then downgrade confidence or remain pending verification.Record contrarian_loopback as the Boolean true or false.
A full report contains these H2 sections in order:
The Trigger Verification section must distinguish observed, contradictory, and missing evidence plus fix validation. Mermaid must reflect verified evidence. The JSON summary must include:
diagnosis_statusrouting_pathroot_causeconfidencefix_confidencefix_code_path_coveragecontrarian_reviewcontrarian_loopbackAfter writing the report, run the bundled validator with PowerShell 7:
pwsh -NoProfile -File <skill-directory>\scripts\validate-diagnosis-output.ps1 `
-Path <diagnosis-markdown-path>
Use the installed windbg-diagnostic-method directory for
<skill-directory>. The script checks each section body independently,
requires at least two alternatives, accepts explicit or implicit Mermaid
participants, parses the JSON summary, and exits nonzero on failure.
Correct failed checks and rerun the script before presenting the report as structurally complete. Structural validation does not replace technical review.
Dumps, traces, ETLs, CABs, source, paths, tokens, and memory contents can be
sensitive. Obtain authorization before capture, configuration changes, or
sharing. Verifier and Page Heap can disrupt workloads and require a recoverable
test plan plus restoration steps. Public feedback follows FEEDBACK.md and
defaults to a minimal reviewed summary with no automatic attachments.
For feedback about this method or validator, follow the package FEEDBACK.md.
Do not attach private diagnosis files automatically.
Use with every WinDbg plugin investigation to apply evidence-first reasoning, confidence calibration, contrarian review, structured reporting, and deterministic validation. Not a bug-family-specific t
---name: windbg-diagnostic-methoddescription: Use with every WinDbg plugin investigation to apply evidence-first reasoning, confidence calibration…---# plugins/windbg/skills/windbg-diagnostic-method/SKILL.md개요
Use with every WinDbg plugin investigation to apply evidence-first reasoning, confidence calibration, contrarian review, structured reporting, and deterministic validation. Not a bug-family-specific triage skill.
FAQ
게시자에게서 plugins/windbg/skills/windbg-diagnostic-method/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/microsoft/win-dev-skills에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.