菜单
This skill should be used when the user says "redo this", "start over", "scrap this approach", "rewrite from scratch", "try a simpler approach", or wants to discard the current implementation and reimplement with an elegant solution using everything learned so far.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when writing documentation, READMEs, explanations, blog posts, or any prose meant for humans to read
This skill should be used when the user asks to "rebase all open PRs", "update all PRs with latest main", "make sure every open PR is up to date with main", "sync all open PRs onto main", "rebase all my PRs", or wants to bring every open pull request current with its base branch by rebasing in parallel git worktrees, resolving conflicts with a team of agents, and force-pushing.
Groom and prioritize a project backlog — verify each candidate issue's claims against the current codebase, pick the most important N, rewrite them to a ready-to-work standard (Problem/Goals/Decisions/Outcomes/Verification), move them to Ready on the board, and close obsolete issues. Use when asked to "groom the backlog", "triage the backlog", "prioritize issues", "move issues to ready", or "what should we work on next".
This skill should be used when the user asks to "summarize a note", "summarize this article", "replace #summarize-later", "add a summary to a note", "generate takeaways", or mentions summarizing Obsidian notes. Replaces the #summarize-later tag with a high-level summary and actionable takeaways.
This skill should be used when the user asks to "update the changelog", "add changelog entries", "what changed since last release", or when updating CHANGELOG.md with user-facing changes. Follows Keep a Changelog format and filters out internal-only commits.
This skill should be used when the user asks to "improve a prompt", "make this prompt better", "optimize this prompt", "refine this system prompt", or wants to apply concept elevation to compress and clarify LLM instructions.
| name | redo |
| user-invokable | true |
| description | This skill should be used when the user says "redo this", "start over", "scrap this approach", "rewrite from scratch", "try a simpler approach", or wants to discard the current implementation and reimplement with an elegant solution using everything learned so far. |
After working through a problem and gaining deep context about the codebase, constraints, and edge cases, step back, discard the current approach, and reimplement from scratch with the simplest, most elegant solution.
Synthesize what was learned: Review the conversation history. Identify:
Identify the essential complexity: Separate what is truly necessary from accidental complexity. Ask: "What is the minimum viable design if explained to a senior engineer with full context?"
Design the elegant solution: Before writing any code, describe the new approach in 3-5 sentences. It should be:
Confirm with the user: Present the new design and get approval before proceeding. Explain what changes and why it is better.
Implement cleanly: Rewrite from scratch rather than patching. Do not carry forward unnecessary abstractions, workarounds, or dead code from the previous attempt.
Verify: Run tests, linters, and any relevant quality gates to confirm the new implementation is correct.
