菜单
Disciplined debug session protocol. Read symptom → form hypothesis → verify before fixing → propose minimum-change fix. Pre-Action Gate prevents hasty rewrites that break unrelated code. Use when an error or unexpected behaviour appears and you want a focused diagnosis instead of guess-and-check.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate concise documentation from code. README, function docs, API references, architecture notes — written in plain language, with examples that work, no padding. Use when shipping or onboarding and you want docs that read fast and stay accurate.
Scope-guarded refactoring. Define target → identify minimum diff → preserve behaviour → verify with tests. Pre-Action Gate prevents scope drift into unrelated improvements. Use when you want a targeted refactor that does not turn into a 50-file rewrite.
Compress long content into structured summary. TLDR + key points + action items, length-tunable. Use for meeting notes, transcripts, long docs, threads, codebases. No padding, no editorial commentary.
Generate disciplined test cases. Focus on behaviour not implementation, cover edge cases without bloat, name tests for the case not the function. Use when writing tests for new code or filling gaps in coverage.
Extract and triage TODO/FIXME/HACK comments from a codebase. Categorize by urgency, group by file, identify stale TODOs older than threshold. Use during cleanup sprints, before releases, or when onboarding a new project.
Generate a concise commit message from the current git diff. Conventional commits format (feat/fix/refactor/etc). Use when staged changes are ready to commit and you want Claude to write the message instead of typing it manually.
| name | maji-debug |
| description | Disciplined debug session protocol. Read symptom → form hypothesis → verify before fixing → propose minimum-change fix. Pre-Action Gate prevents hasty rewrites that break unrelated code. Use when an error or unexpected behaviour appears and you want a focused diagnosis instead of guess-and-check. |
A skill that turns Claude into a debug partner who slows down to think, not a guess-and-check refactor machine.
Type maji-debug followed by:
Claude follows the 5-step protocol below.
State plainly:
If any of these missing → ASK before guessing.
Propose the most-likely cause in 1 sentence. If multiple plausible causes, list 2-3 ranked by likelihood.
Format:
Hypothesis 1 (most likely): [cause] because [evidence].
Hypothesis 2: [cause] because [evidence].
Hypothesis 3 (lower probability): [cause] because [evidence].
Run a check that confirms or denies the top hypothesis.
console.log / print / breakpointNEVER fix until hypothesis is verified. Guessing the fix wastes time and often introduces new bugs.
Before changing code, check:
Each "yes" to question 2 → STOP. Discuss scope with user before touching unrelated code.
Apply the smallest diff that resolves the verified hypothesis.
SYMPTOM
[1-sentence summary]
HYPOTHESIS
[1-sentence most-likely cause + brief evidence]
VERIFICATION
[How I checked + result]
FIX
[Code diff or pattern, minimum scope]
WHY
[1-sentence reasoning — what this fix does and why it's safe]
| ❌ Avoid | ✅ Do instead |
|---|---|
| "Try this and see if it works" | Verify hypothesis first, then fix |
| Refactoring entire file when bug is on line 42 | Touch only line 42 (or its immediate scope) |
| Fixing 3 bugs at once | Fix one bug per cycle, commit, then move to next |
| Suggesting a library swap as a "fix" | Library swaps are refactors, not bug fixes |
Adding try/catch without diagnosing root cause | Catch silences symptoms; find why it threw |
| "It's probably a race condition" without evidence | State as hypothesis, then verify with logs/test |
User input:
maji-debug — login form throws "Cannot read property 'email' of undefined"
File: src/auth/login.ts
Claude output:
SYMPTOM
TypeError on src/auth/login.ts when login form submits — accessing user.email on undefined.
HYPOTHESIS
Most likely: API response shape changed and user object is now nested under user.data.
Evidence: line 14 reads response.user.email; if response shape is { data: { user: {...} } }, this would throw.
VERIFICATION
Reading src/auth/login.ts:14 + src/api/types.ts...
Confirmed: api/types.ts line 8 shows LoginResponse type wraps user under data field.
FIX
src/auth/login.ts:14
- const email = response.user.email
+ const email = response.data.user.email
WHY
Aligns with current LoginResponse type. No other paths affected — this line is the only consumer.
maji-mode and maji-reviewmaji-mode ensures terse output (no padding, banned phrases)maji-review can run after fix to verify no regressions introducedmaji-commit writes the commit message after fix is verifiedCommon adjustments via fork:
maji-debug is part of MAJI Skills · By MAJI · No Codes, Only Vibes.