@elvis1513/auto-coding-skill 2.1.2 → 2.1.3

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.
package/README.md CHANGED
@@ -300,6 +300,7 @@ python3 docs/tools/autopipeline/ap.py upgrade --dry-run
300
300
 
301
301
  `structure-check` is intentionally generic. Project-specific paths and stricter rules belong in `docs/ENGINEERING.md` under `structure.*`, `optimization.*`, and optional `commands.structure_check`.
302
302
  Historical large-file debt can be listed in `structure.accepted_debt_paths` after it is recorded in the health baseline or optimization backlog; continued large additions to those files still fail.
303
+ Do not split files only to reduce line count. Split only when a clear business or technical boundary improves cohesion and change safety; keep cohesive transaction, state-machine, workflow, or test-scenario code together and track it as accepted debt when appropriate.
303
304
 
304
305
  `docs-ledger-check` is intentionally separate from `structure-check`. It treats `docs/tasks/taskbook.md`, `docs/tasks/closure-log.md`, and top-level `docs/design/T*.md` as active working sets. When they exceed `docs.active_*` budgets, the fix is physical archiving under `docs.task_archive_dir` / `docs.design_archive_dir`; `docs.archive_index` is only a navigation index and does not count as archive slimming.
305
306
 
@@ -200,6 +200,7 @@ python3 docs/tools/autopipeline/ap.py gen-summary <TASK_ID>
200
200
  - Put new code in the correct layer: domain rules stay out of controllers/pages, orchestration belongs in application/service/usecase code, external systems belong behind infrastructure adapters, and UI components should not own deep business workflows.
201
201
  - Reuse before building: search existing utilities, components, clients, validation, permissions, caching, retry, formatting, and automation scripts before adding another helper.
202
202
  - Do not add new responsibilities to large files. If a file exceeds `structure.max_file_lines_warn`, prefer extracting a focused module or component; if it exceeds `structure.max_file_lines_block`, only small fixes are acceptable unless the path is explicitly allowed.
203
+ - Never split files just to reduce line count. Split only when the business or technical boundary is clear, cohesion improves, tests can cover the move, and the change does not break transaction, state-machine, workflow, or reading continuity. Otherwise record or keep accepted debt and avoid adding new responsibilities.
203
204
  - Historical large files can be listed in `structure.accepted_debt_paths` only after they are recorded in the health baseline or optimization backlog; this does not permit large new additions to those files.
204
205
  - `structure.layer_rules` enforces configurable import boundaries between domain, application, infrastructure, interface, and shared layers.
205
206
  - Self-built algorithms, concurrency controls, caches, protocol clients, or framework-like helpers require a concrete reason such as performance, concurrency, offline/deploy constraints, licensing, security, or compatibility, plus tests or benchmark/runtime evidence.
@@ -429,6 +429,7 @@ docs:
429
429
  3) 单文件容量控制
430
430
  - 超过 `structure.max_file_lines_warn` 的文件只允许小修和缺陷修复,新增职责应优先抽取模块。
431
431
  - 超过 `structure.max_file_lines_block` 的文件不得继续承载新职责,除非该文件在 `structure.allow_large_files` 中声明为生成物或外部产物。
432
+ - 禁止仅为了降低行数而拆文件。拆分必须服务于清晰的业务边界、技术边界、变更安全和阅读连续性;如果事务、状态机、用例流程或测试场景需要放在一起维护,应保留内聚结构并记录为接受债务。
432
433
  - 已记录为接受债务的历史大文件可放入 `structure.accepted_debt_paths`,但继续大幅新增仍会被阻塞。
433
434
  - 对已偏大的文件一次性增加超过 `structure.max_added_lines_to_large_file` 行时,`structure-check` 会阻塞,要求拆分或写明例外理由。
434
435
 
@@ -46,6 +46,7 @@
46
46
 
47
47
  - 文件超过 `structure.max_file_lines_warn`:只允许小修、缺陷修复、类型补充;新增职责应先抽取模块。
48
48
  - 文件超过 `structure.max_file_lines_block`:不得继续承载新职责,除非是生成物、外部产物或已在 `structure.allow_large_files` 中声明。
49
+ - 禁止仅为了降低行数而拆文件。拆分必须服务于清晰的业务边界、技术边界、变更安全和阅读连续性;如果事务、状态机、用例流程或测试场景需要放在一起维护,应保留内聚结构并记录为接受债务。
49
50
  - 历史大文件如果已进入健康基线 / backlog,可在 `structure.accepted_debt_paths` 中登记;登记只豁免历史体量,不豁免继续大幅新增。
50
51
  - 函数 / 方法 / 组件超过 `structure.max_function_lines_warn`:应拆分为命名清晰的子函数、hook、service、query、mapper 或 view component。
51
52
  - 对大文件新增超过 `structure.max_added_lines_to_large_file` 行:默认阻塞,必须拆分或记录例外理由。
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@elvis1513/auto-coding-skill",
3
- "version": "2.1.2",
3
+ "version": "2.1.3",
4
4
  "description": "CLI installer for a generic .agents engineering workflow with optional CI/Jenkins and target-environment verification.",
5
5
  "type": "module",
6
6
  "bin": {