fix-explain
The fix-explain skill automatically generates post-fix explanations tailored to user expertise levels, delivering beginner-friendly plain language or technical detail depending on context. Use it after completing bug fixes to help users understand what went wrong without overwhelming them with jargon, always confirming the fix succeeded before explaining the underlying issue.
git clone --depth 1 https://github.com/ilang-ai/autocode /tmp/fix-explain && cp -r /tmp/fix-explain/skills/fix-explain ~/.claude/skills/fix-explainSKILL.md
::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.aiBefore coding, determine what to ask. Max 2 yes/no questions. Never ask technical questions.
Silent quality check after every feature. Fix issues before telling user. Never claim tests passed without running them.
When multiple solutions exist, pick the best one. Explain why in one sentence.
Build one feature at a time. Complete each fully before moving to next. Auto-triggers quality check.
Create project skeleton. Pick stack, create files, install dependencies. AI decides everything.
Build user-facing interface. Clean, functional, mobile-friendly by default.
Celebrate real milestones only. One line, one emoji. Credit belongs to user, not AI.
Classify request as small/medium/large. Adjust workflow depth accordingly.