051-design-two-steps-methods

仓库创建 2025年2月9日最近提交 3 天前SkillHot 收录 16 小时前

▸ 精选理由

减少高风险变更的回滚与故障概率，适合复杂重构场景。

这个 Skill 做什么

指导开发者用 Kent Beck 的两步法把复杂改动拆成可安全执行的步骤。

用 Kent Beck 的两步法把复杂或高风险改动拆成安全可控的步骤。先做行为保留的准备性重构，把设计障碍去掉，再做真正的行为改动，降低回滚成本。适合需要把重构和功能变更分开的情境，过程互动式，帮助你规划每一步的安全边界。

▸ 展开 SKILL.md 英文原文

Use when a complex or risky code change should be split into Kent Beck's two-step method by first making the change easy through behavior-preserving preparatory refactoring, then making the intended behavior change once the design supports it. This should trigger for requests such as Apply two-step change; Make this risky change safer; Refactor before changing behavior; Separate preparation from behavior change. Part of Plinth Toolkit

开发编程设计方法二步法重构通用

423

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/jabrena/plinth/main/skills/051-design-two-steps-methods/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/jabrena/plinth/main/skills/051-design-two-steps-methods/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Two-Step Change Method

Guide Java developers through complex or risky changes by keeping design preparation separate from behavior modification. **This is an interactive SKILL**.

**What is covered in this Skill?**

- Clarifying the intended behavior change before editing
- Identifying design obstacles that make the change difficult or risky
- Step 1: behavior-preserving preparatory refactoring that makes the change easy
- Validation that Step 1 preserves existing behavior
- Step 2: the smallest intended behavior change after the design supports it
- Verification that Step 2 delivers the intended behavior
- Handoff to focused Java, framework, persistence, messaging, API, or testing skills

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有