special-place-administrator/systematic-debugging
skills/systematic-debugging/SKILL.md
Four-phase root cause analysis: observe, hypothesize, verify, fix. Enforces investigation before code changes and stops guess-and-check debugging.
development
Updated Apr 23, 2026
$ install --global
skillsauthnpx skillsauth add special-place-administrator/citadel_codex systematic-debuggingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 1:00 AM20.7s1 file scanned
SKILL.md
- name:
- systematic-debugging
- description:
- >-
- Four-phase root cause analysis:
- observe, hypothesize, verify, fix. Enforces
Systematic Debugging
Identity
No fixes without root cause investigation first.
Protocol
Phase 1: Observe and reproduce
- Read the error, stack trace, or bug report carefully.
- Reproduce the issue and capture exact trigger conditions.
- Isolate the failing component, function, or workflow.
Phase 2: Hypothesize and verify
- Write up to three hypotheses for the cause.
- Define one verification step for each hypothesis.
- Gather evidence before changing logic.
Phase 3: Root cause
- Explain why the bug happens, not just where.
- Trace the failure back to the incorrect assumption or broken data flow.
- Check for the same pattern elsewhere in the codebase.
Phase 4: Implement and verify
- Add a reproducing test when the repo has a suitable test harness.
- Apply the smallest fix that resolves the root cause.
- Re-run the relevant checks and confirm the issue is actually closed.
Emergency Stop Rule
If two fixes fail in a row, stop and return to hypothesis verification. A third guess is not progress.
Exit Protocol
---HANDOFF---
- Bug: {problem statement}
- Root cause: {one-line cause}
- Fix: {what changed}
- Verified: {checks run}
- Related: {similar patterns found or none}
---
Related Skills
special-place-administrator/triage
development
VerifiedTrustedCommunity
GitHub issue and PR investigator. Pulls open issues/PRs, classifies them, searches the codebase for root cause or reviews contributed code, proposes fixes with file:line references, and optionally implements fixes. Handles both issues and pull requests.
SKILL.mdUpdated Apr 23, 2026
special-place-administrator/test-gen
development
VerifiedTrustedCommunity
Generate and verify tests — happy path, edge cases, error paths — using the project's own framework and patterns
SKILL.mdUpdated Apr 23, 2026
special-place-administrator/setup
testing
VerifiedTrustedCommunity
First-run experience for the harness. Detects the project stack, scaffolds the .citadel/ state directory, generates configuration, runs one real task as a demo, and prints a reference card of all available skills. Gets someone from install to first `do` command in 5 minutes.
SKILL.mdUpdated Apr 23, 2026
special-place-administrator/session-handoff
data-ai
VerifiedTrustedCommunity
Summarize the current session into a compact HANDOFF block for the next session or delegated agent.
SKILL.mdUpdated Apr 23, 2026