菜单
Analyze and fix issues in the last completed task. Use when user reports errors after task was marked as done, when completion report had high confidence but result has issues, when AI missed obvious problems, or when post-task issues appear.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/dmitryprg-ai/cursor-develop-autorules --skill fix-last-task命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Test API endpoints with proper authorization including Basic Auth and session cookies. Use when testing curl requests, checking API responses, getting 401 Unauthorized, session expired errors, or verifying endpoint behavior after changes.
Implement accumulated improvements from improvements-backlog into AI rules and skills. Use when backlog has 5+ items, weekly rule update cycle, 2+ high priority improvements exist, before important releases, when same error repeated 3+ times, when user says implement improvements/process backlog/update rules from errors.
Fix bugs, errors, exceptions, and unexpected behavior. Use when debugging, fixing errors, handling crashes, or when user mentions bug, error, broken, not working, crash, exception, 500 error, Application error, white screen, TypeError, undefined is not a function, or unexpected behavior.
正在显示 SKILL.md
基于 SOC 职业分类
| name | fix-last-task |
| description | Analyze and fix issues in the last completed task. Use when user reports errors after task was marked as done, when completion report had high confidence but result has issues, when AI missed obvious problems, or when post-task issues appear. |
| allowed-tools | Read, Write, Bash, Grep, Glob |
| model | sonnet |
| user-invocable | true |
Analyze failure before fixing. Patching without understanding why you missed the problem guarantees you'll miss it again.
Apply 5 Whys — dig at least 5 levels deep to find why issues were missed. Surface-level answers like "I forgot" are not root causes — keep asking until you reach a systemic reason.
Create TODO list — one item per missed issue, critical ones first.
For each TODO:
[before]% -> [after]% — [reason]Open and read EVERY changed file. Run the Challenge (4 questions) again.
Record improvement to .cursor/data/improvements-backlog.md because patterns repeat without reflection — the same class of mistake will resurface unless codified.
Full DONE block: issues found, fixes applied, root cause, improvement recorded, final confidence.
For detailed analysis and review templates, see templates.md.