分階段架構重構

來源狀態

可用來源

原始作者: petekp

這是第三方 Community Skill；2lus 收錄不代表已完整安全審計或保證安全。

資源類型

Skill

與類似 Skill 有什麼不同？

• 重構機會分析

  Refactor 著重局部程式改善且保留行為；Architectural Refactor 涵蓋模組依賴、架構邊界與分階段遷移。

來源描述的能力

這些是來源描述的可能操作，不代表 2lus 已授予權限或已測試。

• 讀取檔案
• 寫入檔案
• Shell 指令

這個 Skill 是什麼？

在已批准的目標架構下實作有邊界的重構；與尋找機會的 Refactor 不同，重點是持續追蹤進度和每階段的出口條件。

可以做什麼？何時適合使用？

• 執行已審核的模組拆分。
• 跨多次工作續接遷移。
• 防止長期重構偏離計畫。

如何使用

1. 提供評估、目標架構與批准範圍。
2. 拆出可獨立檢查的步驟，記錄相依與回復方式。
3. 完成一段即按專案允許方式驗證並記錄，未達門檻先停止。

使用前你需要準備

• 程式碼、diff 與目標行為
• 專案慣例與限制

你可以替換：

[framework]、[target branch]

環境與相依需求

• 明確的架構評估、版本控制與專案 build/type/test 工具；動態測試須另獲授權。

使用範例與 Prompt

以下是 2lus 撰寫的示範需求；請替換為你有權處理的檔案與專案，不代表已執行或保證結果。

入門

把這份 architecture assessment 拆成三個可獨立審查的階段，暫不改碼。

實務

依已批准計畫只實作第一段介面抽取，列出靜態檢查與待人工測試，不擴大範圍。

進階

為跨模組遷移建立持久化進度、入口／出口條件與回復策略；Build/Test 依專案政策執行，失敗後先分析不要無限重跑。

實用提醒

• 不要把未執行的驗證標為通過。

限制與注意事項

• 計畫檔無法自動保證相容；跨資料庫遷移需額外評估。

安全注意事項

• 不可清除未提交修改或自動 commit/push；資料變更需獨立批准。

使用與設定

此條目不提供已確認的通用安裝指令；請依官方文件與 Agent 版本操作。

支援平台

未確認特定 Agent 相容性

來源與授權

來源查核日期（非安全認證）: 2026-09-29

MIT

相關 Skills

• 重構機會分析
• 程式碼變更審查
• 單元測試設計 Agent

Source status

Active source

Original author: petekp

This is a third-party community skill. Inclusion by 2lus is not a complete security audit or safety guarantee.

Resource type

Skill

How is this different from similar skills?

• Refactor

  Refactor improves local code while preserving behavior; Architectural Refactor addresses dependencies, architecture boundaries and staged migration.

Documented capabilities

These are operations described upstream, not permissions granted or tested by 2lus.

• Read files
• Write files
• Shell commands

What is this skill?

Use an approved target architecture to guide incremental changes and verification gates; unlike Refactor, this workflow executes a plan rather than discovering opportunities.

Use cases and when to use it

• Split modules under an approved design.
• Resume migration across sessions.
• Keep long-running work aligned with its plan.

How to use it

1. Provide the assessment, target and approved scope.
2. Define independently reviewable steps, dependencies and recovery options.
3. Verify each stage as project policy permits; stop at unmet gates.

What you need

• Source, diff and expected behavior
• Project conventions and constraints

You can replace:

[framework], [target branch]

Environment and dependencies

• An explicit assessment, version control and project build/type/test tools; dynamic tests need authorization.

Usage and prompt examples

These example requests were written by 2lus. Substitute files and projects you may use; examples are not executed results or guarantees.

Beginner

Split this architecture assessment into three reviewable stages without editing code.

Practical

Implement only the approved interface-extraction stage. List static checks and pending manual tests.

Advanced

Design persistent progress, entry/exit gates and recovery for a cross-module migration. Follow project policy for Build/Test and analyze failures before retrying.

Tips

• Never record an unexecuted check as successful.

Limitations

• Progress files do not guarantee compatibility; database migrations need separate analysis.

Security notes

• Do not discard local changes or commit/push automatically; authorize data changes separately.

Usage and setup

No verified universal installation command is provided for this entry. Follow the official documentation for your agent version.

Supported agents

Specific agent compatibility unknown

Sources and license

Source check date (not a safety certification): 2026-09-29

MIT

Related skills

• Refactor
• Code Review
• Code Testing Agent