‹ 首页

formax-rework-convergence-workflow

@yusifeng · 收录于 5 天前 · 上游提交 3 周前

Use when code has gone through repeated rework and may contain redundant logic, style drift, or tangled structure. Trigger when user asks for "返工收敛", "cleanup-pass", or requests a focused cleanup pass that reduces churn without changing behavior.

场景代码重构返工清理结构优化

适合你，如果代码经过多次返工，需要一次专注的清理而不改变行为

/ 下载安装
https://github.com/yusifeng/formax/tree/main/.codex/skills/formax-rework-convergence-workflow ↗
/ 通过 npx 安装 校验哈希
npx oh-my-skill add yusifeng/formax/formax-rework-convergence-workflow
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- yusifeng/formax/formax-rework-convergence-workflow
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify yusifeng/formax/formax-rework-convergence-workflow
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
192GitHub stars
~532上下文体积 · 单文件
索引托管

怎么用

商店整理自技能原文 · 版本 5a48573 · 表述以原文为准
它做什么

装上后，Claude 会在代码经过多次返工后，自动清理冗余逻辑、恢复结构清晰，且不改变原有行为。

什么时候触发

当用户提到“返工收敛”、“cleanup-pass”或请求清理代码时触发。

装好后可以这样说
Claude 会分析最近改动，清理冗余。
执行收敛清理流程。
触发代码整理。
技能原文 SKILL.md作者撰写 · MIT · 5a48573

Formax Rework Convergence Workflow

Purpose

Use this workflow to clean up code after multiple back-and-forth edits.

Primary goal:

  • Reduce redundancy
  • Restore structure clarity
  • Keep behavior unchanged unless user explicitly asks for behavior changes
Trigger Phrases

Run this skill when the user says:

  • 返工收敛 (recommended keyword)
  • cleanup-pass
  • "帮我收敛一下这波改动"
  • "把返工后冗余代码清掉"
Scope Rules
  1. No feature expansion during convergence.
  2. No broad redesign unless user explicitly asks.
  3. Prefer local cleanup in touched files first.
  4. Preserve existing runtime behavior and UI semantics.
Workflow
  1. Freeze Intent
  2. Restate the target in one sentence.
  3. Identify "must keep" behavior before editing.
  1. Build Cleanup Map
  2. Inspect current diff and touched files.
  3. Group issues into:
  4. duplicate logic
  5. dead code / unreachable branches
  6. conflicting style patterns
  7. state ownership confusion
  8. temporary patches that became permanent
  1. Rank by Risk and Value
  2. High priority:
  3. behavior-risky duplication
  4. conflicting state sources
  5. repeated conditional branches causing drift
  6. Medium priority:
  7. naming inconsistencies
  8. repeated style tokens/classes
  9. Low priority:
  10. cosmetic micro-cleanups
  1. Apply Minimal Convergence Edits
  2. Collapse duplicated branches into one shared path.
  3. Remove dead paths only when replacement path is verified.
  4. Keep interfaces stable.
  5. Keep patch size small and reviewable.
  1. Validate
  2. Run targeted type-check/tests for changed scope.
  3. If UI is touched, do a quick manual visual sanity check path.
  4. If validation is blocked, report the exact blocker and impact.
  1. Report Back in Convergence Format
  2. what was removed
  3. what was unified
  4. what behavior stayed the same
  5. residual risks
Guardrails
  • Do not hide uncertainty: explicitly call out assumptions.
  • Do not ship "temporary fixes" silently.
  • If a temporary mitigation is unavoidable, mark it and define removal conditions.
  • Never mix unrelated cleanup in the same pass.
Output Template

Use this structure in responses:

  1. Convergence summary (2-4 lines)
  2. Redundancy removed
  3. Structure unified
  4. Behavior parity check
  5. Risks and next small pass (optional)
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…