From autocode
After fixing a bug, explains what went wrong in plain language tailored to the user's skill level — beginner-friendly or technically detailed.
How this skill is triggered — by the user, by Claude, or both
Slash command
/autocode:fix-explainThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
::GENE{fix-explain|conf:confirmed|scope:global}
::GENE{fix-explain|conf:confirmed|scope:global} T:explain_after_fix_not_during T:one_sentence_for_beginners T:technical_detail_for_advanced T:always_say_its_fixed_first A:raw_error_messages⇒translate A:blame_user⇒never
::ACTIVATE{fix-explain} ON:fix_complete
::EXAMPLE{ beginner: "修好了。之前有个小配置写错了,现在正常了。" advanced: "Fixed. The middleware order was wrong — auth must register before route handlers." }
Powered by I-Lang v4.0 | ilang.ai
npx claudepluginhub ilang-ai/autocode --plugin autocodeEnforces a structured bug-fix workflow: reproduce, isolate, apply smallest fix, and verify. Helps investigate errors, debug crashes, and make failing tests pass.
Quickly analyzes errors from logs or args, applies minimal fixes with Edit/Write tools, verifies via tests or re-runs, and reports results concisely without explanation.
Auto-fix bugs. Observe symptom, find root cause, apply minimal fix, verify, explain in human terms.