一键导入
qmistake
Record mistakes so they are never repeated. When the user points out a mistake, confirms it and saves to .qe/MISTAKE.md. Loaded at every session start.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Record mistakes so they are never repeated. When the user points out a mistake, confirms it and saves to .qe/MISTAKE.md. Loaded at every session start.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when collecting verified project-local coding guidance into .claude/skills based on the project tech stack, with TTL and user-edit protection.
Shows QE Framework usage overview. With no arg, prints the full catalog. With a skill name arg (e.g., /Qhelp Qcommit), reads that skill's SKILL.md and summarizes it in the user's language. Also supports find/search skills mode via reference/find-skills.md.
QE framework (Query Executor) initial setup. Creates the QE state directory, client-specific instruction/config artifacts, and .gitignore entries in a new project, then auto-analyzes the project. Use when the user wants to initialize a project or set up the framework.
Diagnoses and repairs QE installation health across qe-framework, MCP client config, and the project .qe directory. Use for 'doctor', 'check QE health', dependency verification, corrupted .qe state, or repair guidance. Distinct from Qupdate, which updates installed assets.
Use when executing a TASK_REQUEST/VERIFY_CHECKLIST or when already-changed code needs the test-review-fix quality loop. With no flag it auto-selects sequential or parallel-wave execution; `-verify` runs verification. Use Qautoresearch for iterative code-optimization loops and Qscenario-test for scenario/E2E.
Use when a plan or task needs spec documents: TASK_REQUEST and VERIFY_CHECKLIST. Use Qplan for roadmap/phases; use Qexecute after the spec exists.
| name | Qmistake |
| description | Record mistakes so they are never repeated. When the user points out a mistake, confirms it and saves to .qe/MISTAKE.md. Loaded at every session start. |
| invocation_trigger | When the user says something was wrong, points out a mistake, corrects behavior, or says "don't do that again". Also triggered by /Qmistake directly. |
| recommendedModel | haiku |
Records mistakes that Claude made so they are never repeated. Each mistake is stored in .qe/MISTAKE.md which is loaded at every session start via the session-start hook.
/Qmistake directlyParse the user's complaint/correction. Extract:
Use the QE interaction adapter to confirm before recording:
Mistake identified:
What went wrong: {description}
Correct behavior: {what should happen instead}
Context: {skill/file/situation}
Record this mistake?
(a) Yes, record it
(b) Edit description first
(c) Cancel
If user picks (b), ask for the corrected description, then confirm again.
Append the entry to .qe/MISTAKE.md. Create the file if it doesn't exist.
File format:
# Mistake Registry
> These mistakes were identified by the user. Do NOT repeat them.
> This file is loaded at every session start.
---
### M001: {short title}
- **Date**: {YYYY-MM-DD}
- **Wrong**: {what Claude did wrong}
- **Correct**: {what should happen instead}
- **Context**: {skill/agent/file involved}
- **Severity**: {critical / important / minor}
---
Entry numbering: M001, M002, M003... Auto-increment by reading the last entry number.
Severity levels:
critical — Causes data loss, breaks builds, sends wrong output to userimportant — Wrong approach, wasted time, incorrect assumptionminor — Style issue, suboptimal choice, cosmeticReport: "Recorded as M{NNN}. This will be loaded at every session start."
/Qmistake (no args)Show current mistake count and last 5 entries.
/Qmistake addInteractive: ask what went wrong, confirm, save.
/Qmistake listShow all entries from .qe/MISTAKE.md.
/Qmistake resolve M{NNN}Mark a mistake as resolved (add [RESOLVED] prefix). Resolved mistakes stay in the file for reference but are de-prioritized in session injection.
/Qmistake learnPromote auto-extracted recurring failure patterns into the registry (Phase 4, D021).
npm run learn:failures # → node scripts/learn-from-failures.mjs
It scans .qe/learning/failures/** (auto-captured on Stop by failure-capture.mjs),
counts each pattern by distinct task_uuid, and writes recurring ones
(≥ 2 distinct tasks) to .qe/learning/mistake-candidates.md..qe/learning/mistake-candidates.md. For each candidate, present it via
the interaction adapter exactly as in Step 2 above — the user decides whether it is a
genuine systemic mistake worth recording..qe/MISTAKE.md). Skip candidates the user rejects.This is candidate-suggestion only: the extractor never writes to .qe/MISTAKE.md, and
promotion always passes through user confirmation (D011 user-in-the-loop).
The session-start.mjs hook reads .qe/MISTAKE.md and injects its content into the session context. This ensures every new conversation starts with awareness of past mistakes.
Injection format (in hook output):
[MISTAKES] {N} recorded mistakes. Critical: {X}, Important: {Y}.
Top entries:
- M001: {title} — {wrong behavior}
- M002: {title} — {wrong behavior}
Full list: .qe/MISTAKE.md
Only unresolved entries are injected. If there are more than 10, show only critical + important.
/Qmistake learn) for user-confirmed promotionQmistake records mistakes to .qe/MISTAKE.md. /Qlearn is the broader
cross-session learning memory (mistakes + conventions + gotchas + decisions) in
.qe/learnings.md, ranked by time-decayed relevance and injected top-N at session
start. Prefer Qlearn add --type mistake for new lessons that benefit from decay
ranking; Qmistake stays valid and the two registries coexist.