@elvis1513/auto-coding-skill 2.0.3 → 2.0.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -8,10 +8,16 @@
8
8
  ## 2. 范围与非目标
9
9
  ## 3. 现状与问题
10
10
  ## 4. 方案与取舍
11
- ## 5. 接口设计(与 docs/interfaces/api.md 对齐)
12
- ## 6. 数据设计(迁移/回滚)
11
+ ## 5. 架构落位与复用检查
12
+ - 目标层级:Domain / Application / Infrastructure / Interface / Shared / Tooling
13
+ - 既有复用点:
14
+ - 是否需要 ADR:Yes / No;如 Yes,记录到 `docs/architecture/adr/`
15
+ - 是否触及大文件 / 大组件:
13
16
 
14
- ## 7. 时序图(强制)
17
+ ## 6. 接口设计(与 docs/interfaces/api.md 对齐)
18
+ ## 7. 数据设计(迁移/回滚)
19
+
20
+ ## 8. 时序图(强制)
15
21
  ```mermaid
16
22
  sequenceDiagram
17
23
  participant C as Client
@@ -26,7 +32,7 @@ sequenceDiagram
26
32
  A-->>C: response
27
33
  ```
28
34
 
29
- ## 8. ER 图(强制)
35
+ ## 9. ER 图(强制)
30
36
  ```mermaid
31
37
  erDiagram
32
38
  ENTITY_A ||--o{ ENTITY_B : relates
@@ -34,10 +40,10 @@ erDiagram
34
40
  ENTITY_B { string id string a_id }
35
41
  ```
36
42
 
37
- ## 9. 接口时序/调用编排(强制)
38
- ## 10. 测试方案(必须自动化 + 覆盖历史 bug)
39
- ## 11. 安全与合规
40
- ## 12. 性能与容量
41
- ## 13. 风险清单
42
- ## 14. 回滚方案
43
- ## 15. 影响面与发布计划
43
+ ## 10. 接口时序/调用编排(强制)
44
+ ## 11. 测试方案(必须自动化 + 覆盖历史 bug)
45
+ ## 12. 安全与合规
46
+ ## 13. 性能与容量
47
+ ## 14. 风险清单
48
+ ## 15. 回滚方案
49
+ ## 16. 影响面与发布计划
@@ -3,22 +3,32 @@
3
3
  > 仅在任务需要独立 review 记录时使用;不是每个小改动的默认强制文档。
4
4
 
5
5
  ## 1. 静态分析结果
6
- - Command:light_gate / diff_check / verify_api_docs / verify_jenkins
6
+ - Command:structure-check / light_gate / diff_check / verify_api_docs / verify_jenkins
7
7
  - Summary:
8
8
  - Issues:
9
9
 
10
- ## 2. 本地轻量校验
10
+ ## 2. 结构与优化基线
11
+ - Structure standard:`docs/architecture/structure-standard.md`
12
+ - Health baseline read:Yes / No / N/A
13
+ - Optimization backlog read:Yes / No / N/A
14
+ - New / worsened issues:
15
+ - Accepted debt not repeated:
16
+ - Completion standard:Met / Not met / N/A
17
+
18
+ ## 3. 本地轻量校验
11
19
  - light_gate or quick_test/test/build:
20
+ - structure-check:
12
21
  - api docs:
13
22
  - jenkins:
14
23
 
15
- ## 3. 按需本地运行验证(如果有)
24
+ ## 4. 按需本地运行验证(如果有)
16
25
  - runtime-up / health:
17
26
 
18
- ## 4. Jenkins 与目标环境
27
+ ## 5. Jenkins 与目标环境
19
28
  - Jenkins readiness:
20
29
  - Target env verification:
21
30
 
22
- ## 5. 风险与结论
31
+ ## 6. 风险与结论
23
32
  - Risk:
24
- - Conclusion:Pass / Blocked
33
+ - Priority:P0 / P1 / P2 / P3 / N/A
34
+ - Conclusion:Pass / Blocked / Accepted debt
@@ -0,0 +1,24 @@
1
+ # Optimization Backlog
2
+
3
+ > 这里记录持续优化项。被记录为 `accepted-debt` 的项目不等于当前任务未完成;只有新增、恶化或升级优先级时才需要重新报告。
4
+
5
+ ## Status Values
6
+
7
+ - `open`: 已确认,等待排期。
8
+ - `accepted-debt`: 当前接受的债务,按触发条件再处理。
9
+ - `in-progress`: 正在处理。
10
+ - `closed`: 已闭环,证据写在表格中。
11
+ - `superseded`: 被其他方案或任务替代。
12
+
13
+ ## Backlog
14
+
15
+ | ID | Priority | Status | Scope | Item | Reason | Acceptance | Last reviewed |
16
+ | --- | --- | --- | --- | --- | --- | --- | --- |
17
+ | OPT-000 | P2 | open | `<path/module>` | | | | YYYY-MM-DD |
18
+
19
+ ## Review Rules
20
+
21
+ - P0/P1 不能长期停留在 backlog;应进入当前迭代或明确升级。
22
+ - P2 可以排队,但必须有范围、原因和验收标准。
23
+ - P3 只在低成本或同域修改时顺手处理,不影响“优化完成”结论。
24
+ - 新会话整体分析只允许新增、升级或关闭条目,不要重复制造同义优化项。
@@ -0,0 +1,63 @@
1
+ # Project Health Baseline
2
+
3
+ > 用于固定“当前项目结构是否达标”的判断口径。整体分析、结构优化和新会话复盘必须先读本文件,再读 `docs/reviews/optimization-backlog.md`。
4
+
5
+ - Baseline date: YYYY-MM-DD
6
+ - Baseline commit: `<git-sha>`
7
+ - Owner: <name / team>
8
+ - Review scope: <repo / module / subsystem>
9
+ - Standard: `docs/architecture/structure-standard.md`
10
+
11
+ ## 1. Current Accepted Structure
12
+
13
+ 记录当前被接受的目录结构、主要模块边界、已知历史原因和不再重复争论的事实。
14
+
15
+ | Area | Current state | Accepted because | Review date |
16
+ | --- | --- | --- | --- |
17
+ | <module/path> | | | |
18
+
19
+ ## 2. Closed Optimization Scope
20
+
21
+ 记录已经闭环的优化项。新会话不能把这些项重复判定为“当前未完成”。
22
+
23
+ | ID | Closed date | Scope | Acceptance evidence |
24
+ | --- | --- | --- | --- |
25
+ | OPT-000 | YYYY-MM-DD | | |
26
+
27
+ ## 3. Accepted Debt
28
+
29
+ 这些是已知但暂不处理的问题。除非新增风险、影响扩大或优先级升级,否则只保留在 backlog,不作为当前任务失败原因。
30
+
31
+ | ID | Priority | Scope | Debt | Why accepted | Revisit trigger |
32
+ | --- | --- | --- | --- | --- | --- |
33
+ | DEBT-000 | P2 | | | | |
34
+
35
+ ## 4. Priority Rules
36
+
37
+ - P0: blocks build, release, deploy, core user flow, data integrity, security, or compliance.
38
+ - P1: clear architectural violation, contract drift, missing test around high-risk change, or recently introduced maintainability risk.
39
+ - P2: planned debt such as large files, hot directories, module extraction, stronger tests, or tool consolidation.
40
+ - P3: optional naming, style, polish, or further abstraction.
41
+
42
+ ## 5. Completion Standard
43
+
44
+ An optimization task is complete when all are true:
45
+
46
+ - The scoped P0/P1/P2 items listed for this task are closed.
47
+ - Local gate passed, including structure check when enabled.
48
+ - No new unclassified P0/P1 was introduced.
49
+ - Remaining P2/P3 items are either in `docs/reviews/optimization-backlog.md` or accepted debt above.
50
+ - Review output says explicitly whether the project meets this baseline.
51
+
52
+ ## 6. New Review Instructions
53
+
54
+ When asked to analyze structure or optimization:
55
+
56
+ - Read this baseline first.
57
+ - Read `docs/reviews/optimization-backlog.md` second.
58
+ - Report only:
59
+ - new or worsened issues;
60
+ - unrecorded P0/P1;
61
+ - backlog items whose priority should now be upgraded;
62
+ - baseline drift.
63
+ - Do not repeat accepted debt as fresh findings.
@@ -15,6 +15,7 @@
15
15
  - Jenkins Build: <build url>
16
16
  - Target Env: <env name / health url / page path>
17
17
  - Verification: <health / key api / key page / business path>
18
+ - Structure Check: <passed / blocked / skipped with reason>
18
19
  - Result: DEV-CLOSED / PASS / FAIL / PARTIAL
19
20
  - Follow-up: <none or todo>
20
21
  - Jenkins Failure: <optional>
@@ -20,6 +20,7 @@
20
20
 
21
21
  ## 3. 质量证据
22
22
  - 本地轻量校验:light_gate or quick_test/test/build / api docs / jenkins / diff-check
23
+ - 结构检查:structure-check
23
24
  - Jenkins Build:
24
25
  - 目标环境验证:
25
26
  - 闭环记录:`docs/tasks/closure-log.md`
@@ -15,6 +15,9 @@
15
15
  - 是否高风险(Yes/No):
16
16
  - 高风险分类(如有):DB / Auth / Payment / Jenkins / Gateway / Upload / Prod Config
17
17
  - 影响面(API / DB / Jenkins / Page / Config / Deploy):
18
+ - 结构落位(Domain / Application / Infrastructure / Interface / Shared / Tooling / N/A):
19
+ - 复用检查(已有 helper / 组件 / 脚本 / 库):
20
+ - 是否需要 ADR(Yes/No):
18
21
  - 最小设计记录:
19
22
  - 验收标准:
20
23
  - 子任务(如有):