Archive Change Skill

Archive completed changes and maintain project history.

Features

📦 Change Archiving

• Move completed changes to archive
• Generate completion reports
• Update project history
• Clean up working directories

📝 Documentation

• Auto-generate change summary
• Link related artifacts
• Update changelog
• Create knowledge base entries

🔗 Cross-Reference

• Link to related issues
• Reference PRs and commits
• Connect to requirements
• Trace to deployments

Trigger Patterns

"归档", "archive", "完成"
"变更完成", "change complete"
"结束变更", "finish change"
"交付", "deliver"

Output Format

┌─────────────────────────────────────────────────────┐
│ Change Archived                                     │
├─────────────────────────────────────────────────────┤
│ Change: {change_name}                               │
│ Status: ✓ Completed                                 │
│ Duration: {days} days                               │
├─────────────────────────────────────────────────────┤
│ Artifacts:                                          │
│ • Proposal: ✓                                       │
│ • Specs: ✓                                          │
│ • Design: ✓                                         │
│ • Tasks: ✓ (15/15 completed)                        │
│ • Tests: ✓ (42 passed)                              │
├─────────────────────────────────────────────────────┤
│ Archive Location:                                   │
│ archive/changes/{change_name}/                      │
└─────────────────────────────────────────────────────┘

Archive Structure

archive/
└── changes/
    └── {change_name}/
        ├── SUMMARY.md           # Change summary
        ├── CODE-DELIVERY.md     # 代码归档（必填，见下节）
        ├── PROPOSAL.md          # Original proposal
        ├── SPECS.md             # Specifications
        ├── DESIGN.md            # Design document
        ├── TASKS.md             # Task list
        ├── CHANGELOG.md         # Detailed changes
        ├── TESTS.md             # Test results
        └── artifacts/           # Related files

代码归档（CODE-DELIVERY.md，强制）

归档是双归档：设计文档归档 + 开发代码归档。任何项目经 flowmind 设计后开发的 代码，归档时必须在归档目录生成 CODE-DELIVERY.md，让代码去向可追溯。 TASKS 全部完成但代码未合入/无去向的变更不得归档为 completed。

模板：

# 代码归档 - {change_name}

- 归档时间: {YYYY-MM-DD HH:mm}
- 变更类型: 代码变更 ｜ 纯文档变更（二选一）

## 代码变更记录（纯文档变更则本节写「无代码变更」并说明）
- 仓库: {repo name / namespace / gitId}
- 分支: {feature branch} → 合入 {target branch}
- 提交:
  - {short_id} {title}（{date}）
  - ...
- MR/PR: {!id 或 URL}
- 合入状态: 已合入 {branch} ｜ 待合入（注明原因与计划）｜ 已部署 {env}
- 构建/流水线: {pipeline/build id}（如有）

Rules:

• 提交与 MR 信息经 git 平台核实后填写，不得凭记忆编造 commit id。
• 多仓库变更每个仓库单独一节记录。
• 代码仍在 feature 分支未合入时，只能归档为 status: delivered-pending-merge， 并注明计划合入时间；合入后补记并改为 completed。

Learning Integration

This skill supports FlowMind learning:

• Archive Format: Learns preferred archive structure
• Summary Style: Learns how to summarize changes
• Cleanup Rules: Learns what to keep/delete

User: "归档时保留测试报告"
FlowMind: ✓ Learned: Keep test reports in archive

User: [Next archive]
FlowMind: [Includes test reports automatically]

Examples

Example 1: Archive Feature

User: 归档用户登录功能

FlowMind:
┌─────────────────────────────────────────────────────┐
│ Change Archived                                     │
├─────────────────────────────────────────────────────┤
│ Change: user-login-feature                          │
│ Status: ✓ Completed                                 │
│ Duration: 14 days                                   │
├─────────────────────────────────────────────────────┤
│ Summary:                                            │
│ • Implemented OAuth2 login                          │
│ • Added social login (Google, GitHub)               │
│ • Created user session management                   │
│ • Added login rate limiting                         │
├─────────────────────────────────────────────────────┤
│ Metrics:                                            │
│ • 23 files changed                                  │
│ • 1,847 lines added                                 │
│ • 42 test cases                                     │
│ • 100% test coverage                                │
├─────────────────────────────────────────────────────┤
│ Archive: archive/changes/user-login-feature/        │
└─────────────────────────────────────────────────────┘

Example 2: Bulk Archive

User: 归档所有已完成的变更

FlowMind:
┌─────────────────────────────────────────────────────┐
│ Bulk Archive Complete                               │
├─────────────────────────────────────────────────────┤
│ Archived: 3 changes                                 │
│ • user-login-feature (14 days)                      │
│ • order-optimization (7 days)                       │
│ • api-refactor (21 days)                            │
├─────────────────────────────────────────────────────┤
│ Total:                                              │
│ • 67 files archived                                 │
│ • 12,456 lines documented                           │
│ • 156 test cases                                    │
└─────────────────────────────────────────────────────┘

Configuration

{
  "archive-change": {
    "location": "archive/changes",
    "keepTests": true,
    "keepArtifacts": true,
    "generateSummary": true,
    "updateChangelog": true
  }
}

Archive Checklist

Before archiving, FlowMind checks:

• All tasks completed
• Code delivery recorded (CODE-DELIVERY.md: repo/branch/commits/MR/合入状态)
• All tests passing
• Documentation updated
• Code reviewed
• No open issues
• Deployment verified