Systematic Debugging

by microsoft

Systematic Debugging is a Quality skill for Claude Code, published by microsoft in FluidFramework.

4.9K stars583 forkson microsoft/FluidFrameworkAdded 2026/07/19Repository updated 2026/08/06

View source on GitHub Download repo ZIP

collaborationcrdtdatastructuredistributedfluidfluid-frameworkmicrosoftrealtime

Install in seconds

Install Systematic Debugging

Copy Systematic Debugging into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/microsoft/FluidFramework/tree/main/.agency/plugins/nori/skills/systematic-debugging ~/.claude/skills/systematic-debugging

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/microsoft/FluidFramework.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: .agency/plugins/nori/skills/systematic-debugging/SKILL.md in microsoft/FluidFramework
Installs to: ~/.claude/skills/systematic-debugging
Collection: One of 31 skills cataloged from this repository
Category: Quality — 1897 skills

What Systematic Debugging does

A systematic four-phase debugging framework (root cause investigation, pattern analysis, hypothesis testing, and implementation) for when you encounter any bug, test failure, or unexpected behavior, ensuring you understand the issue before attempting fixes.

Systematic Debugging is cataloged under Quality on DirSkills. Systematic Debugging comes from a repository tagged collaboration, crdt, datastructure, distributed and fluid.

Documentation

README

Excerpt

Systematic Debugging

Overview

Random fixes waste time and create new bugs. Quick patches mask underlying issues.

Core principle: ALWAYS find root cause before attempting fixes. Symptom fixes are failure.

Violating the letter of this process is violating the spirit of debugging.

The Iron Law

NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST

If you haven't completed Phase 1, you cannot propose fixes.

When to Use

Use for ANY technical issue:

Test failures
Bugs in production
Unexpected behavior
Performance problems
Build failures
Integration issues

Use this ESPECIALLY when:

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Systematic Debugging

What else does microsoft publish alongside Systematic Debugging?
Systematic Debugging is one of 31 skills that DirSkills catalogs from microsoft/FluidFramework, the repository it ships in. Its siblings there include API Changes Review, Brainstorming and Building UI/UX. Each one is a separate skill with its own page in this directory, installs the same way Systematic Debugging does, and is maintained by microsoft in that same repository. The rest of the collection is listed on the microsoft/FluidFramework page.
How does Systematic Debugging compare to other Quality skills?
Systematic Debugging ranks #301 by stars among the 1897 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Systematic Debugging against them. Open each page to compare what they document and how they install.