Confucius Debug — 孔子除錯

"不貳過" — Never repeat a mistake. (Confucius, Analects 6.3)

IMPORTANT — Automatic Behavior

When this skill is active, follow these rules:

1. 1. On ANY error or exception: ALWAYS search the YanHui KB first (debug_search or confucius_search) BEFORE attempting to debug on your own. This is free and takes <1 second.
2. If no match found: Use debug_analyze to get an AI-powered fix. The fix is saved to KB so the next person gets it instantly.
3. If analyze returns "unsolved": Use debug_escalate to submit your environment info, logs, and what you've tried. This helps offline research.
4. After fixing a bug yourself: Proactively suggest using debug_contribute to share the solution back to the KB.
5. Never skip step 1. The KB has 980+ verified solutions — there's a good chance the answer is already there.

How It Works

CODEBLOCK0

Tools

confucius_search — Search the Knowledge Base (FREE)

Always try this first. Searches 980+ verified solutions for matching patterns.

CODEBLOCK1

When to use: Any time you encounter an error. It's free and instant.

confucius_analyze — AI-Powered Analysis (FREE)

Only if search returns 0 results. Confucius AI analyzes your error, finds root cause, and provides a fix.

CODEBLOCK2

What you get back:

• - root_cause — Why this happened
• INLINECODE8 — How to fix it
• INLINECODE9 — Actual code to apply
• INLINECODE10 — How sure Confucius is

confucius_escalate — Submit Unsolved Bug for Research (FREE)

When confucius_analyze returns status: "unsolved" (low confidence), submit more context to help offline research.

CODEBLOCK3

What you provide:

• - environment — OS, runtime versions, key dependencies
• INLINECODE15 — Recent error output (last 50 lines)
• INLINECODE16 — List of things already attempted
• INLINECODE17 — Brief overview of project layout

confucius_contribute — Share Your Fix (FREE)

Solved a bug? Share it so nobody hits it again.

CODEBLOCK4

MCP Integration (Recommended)

For Claude Desktop, Claude Code, or any MCP-compatible client:

CODEBLOCK5

This gives you 5 tools automatically: debug_search, debug_analyze, debug_escalate, debug_contribute, debug_hello.

What's in the Knowledge Base?

A-Rate = percentage of fixes rated S (perfect) or A (good) by independent AI verification.

Track Record

• - 280 replies posted on GitHub issues
• 9 confirmed correct by project maintainers (including OpenClaw creator)
• 0 corrections (zero mistakes confirmed by community)
• Knowledge base growing daily via automated pipeline

Setup

1. 1. Set your identity (required for analyze and contribute, optional for search):

1. 2. Test the connection (no ID needed for search):

1. 3. Start debugging! When you hit any error, search first, analyze if needed.

Workflow for OpenClaw Users

When OpenClaw throws an error:

1. 1. Copy the error message
2. Search YanHui KB — INLINECODE27
3. Found a match? — Apply the fix directly
4. No match? — INLINECODE28
5. Fixed it yourself? — confucius_contribute(...) to help others

External Endpoints

Security & Privacy

• - What leaves your machine: Only the error description and error message you provide. No source code, no file contents, no environment variables are sent.
• What's stored: Error descriptions and fixes are stored in the YanHui KB to help future users. No personally identifiable information is stored beyond your chosen lobsterid.
• Authentication: Everything is free. Your lobsterid is used for identification only, not billing.
• Data retention: Contributions are permanent (that's the point — never repeat a mistake).

Credits

• - Author: Washin Village (washinmura) — an animal sanctuary on the Boso Peninsula, Japan.
• Repository: github.com/sstklen/confucius-debug
• License: MIT

Powered by Claude (Anthropic) and the Confucius philosophy: learn from mistakes, never repeat them.

🦞 The bigger the Knowledge Base, the stronger Confucius becomes.