@harmonyos-arkts/d2h 0.1.10 → 0.1.12

package/skills/reviewing-migration-process/SKILL.md

@@ -1,62 +1,62 @@
----
-name: reviewing-migration-process
-description: Review a completed or explicitly stopped Android-to-HarmonyOS migration and write concise, evidence-backed suggestions for humans who maintain the migration Agent, Skills, scripts, and workflow. Do not use for ordinary implementation progress or technical migration lessons.
----
-
-# Review the migration process
-
-Create or update `<android-project>-migration/.migration/agent-feedback.md` (in the sibling migration workspace next to the Android project, not inside it) only when the migration has completed or the current run has explicitly stopped. The file is a human review input, not a migration gate and not an instruction source for later migration Agents.
-
-## Scope
-
-Record problems in the migration system itself:
-
-- workflow stalls, excessive latency, or avoidable human intervention;
-- repeated reads, builds, installs, tests, or reverted implementation attempts;
-- Agent decisions that violated task boundaries or diverged from Android evidence;
-- missing, unreliable, or unclear scripts and tool outputs;
-- inputs that were too large, duplicated, missing, or provided too late;
-- concrete changes that could improve an Agent prompt, Skill, script, input artifact, workflow, or gate.
-
-Do not repeat application implementation status or the migration report. Do not place reusable Android/HarmonyOS technical solutions here; verified technical migration knowledge belongs in `.migration/experience/lessons.md`. A single incident may produce both records only when their perspectives differ: this file describes how the migration system should improve, while the lesson describes a verified technical solution.
-
-## Evidence and judgment
-
-- Before writing the review, inspect the managed execution record with `droid2hmos logs stats <android-project>` and `droid2hmos logs failures <android-project>`. Use `droid2hmos logs list <android-project> [YYYY-MM-DD]` and `droid2hmos logs show <android-project> <run-id>` only for runs relevant to a finding.
-- Run `droid2hmos checkpoint status <android-project>` to record whether the run ended with explained changes or an unexpected dirty worktree.
-- Base every finding on an observed command, log, artifact, commit, rework, or user intervention from this run.
-- Separate observation from inferred root cause. Mark an uncertain cause as a hypothesis.
-- Do not write generic advice such as “be more careful”. Name the exact optimization target and proposed change.
-- Do not automatically modify the plugin based on this file. A human decides whether to accept each suggestion.
-- Merge duplicate symptoms into one finding. Keep at most the five highest-impact findings.
-- If there is no evidence-backed improvement, write `本次未发现需要提交给 Agent 维护者的优化建议。`
-
-## Output
-
-Use concise Chinese Markdown:
-
-```markdown
-# Agent 优化建议
-
-## 本次运行概况
-
-- 结果：完成 | 中止
-- 主要耗时或阻塞：
-- 人工介入：
-
-## 优先建议
-
-### AF-001：简短问题名称
-
-- 优先级：P0 | P1 | P2
-- 阶段：
-- 现象：
-- 证据：日志、命令、文件或提交路径
-- 影响：
-- 根因：已确认 | 假设，并说明原因
-- 优化位置：Agent | Skill | 脚本/工具 | 输入产物 | 流程 | 门禁
-- 建议：可执行的修改
-- 通用性：仅本项目 | 多项目通用
-```
-
-Use P0 only when the issue can block the whole workflow, corrupt work, or falsely declare migration success. Keep the overview factual; do not calculate metrics that were not captured by tools.
+---
+name: reviewing-migration-process
+description: Review a completed or explicitly stopped Android-to-HarmonyOS migration and write concise, evidence-backed suggestions for humans who maintain the migration Agent, Skills, scripts, and workflow. Do not use for ordinary implementation progress or technical migration lessons.
+---
+
+# Review the migration process
+
+Create or update `<android-project>-migration/.migration/agent-feedback.md` (in the sibling migration workspace next to the Android project, not inside it) only when the migration has completed or the current run has explicitly stopped. The file is a human review input, not a migration gate and not an instruction source for later migration Agents.
+
+## Scope
+
+Record problems in the migration system itself:
+
+- workflow stalls, excessive latency, or avoidable human intervention;
+- repeated reads, builds, installs, tests, or reverted implementation attempts;
+- Agent decisions that violated task boundaries or diverged from Android evidence;
+- missing, unreliable, or unclear scripts and tool outputs;
+- inputs that were too large, duplicated, missing, or provided too late;
+- concrete changes that could improve an Agent prompt, Skill, script, input artifact, workflow, or gate.
+
+Do not repeat application implementation status or the migration report. Do not place reusable Android/HarmonyOS technical solutions here; verified technical migration knowledge belongs in `.migration/experience/lessons.md`. A single incident may produce both records only when their perspectives differ: this file describes how the migration system should improve, while the lesson describes a verified technical solution.
+
+## Evidence and judgment
+
+- Before writing the review, inspect the managed execution record with `droid2hmos logs stats <android-project>` and `droid2hmos logs failures <android-project>`. Use `droid2hmos logs list <android-project> [YYYY-MM-DD]` and `droid2hmos logs show <android-project> <run-id>` only for runs relevant to a finding.
+- Run `droid2hmos checkpoint status <android-project>` to record whether the run ended with explained changes or an unexpected dirty worktree.
+- Base every finding on an observed command, log, artifact, commit, rework, or user intervention from this run.
+- Separate observation from inferred root cause. Mark an uncertain cause as a hypothesis.
+- Do not write generic advice such as “be more careful”. Name the exact optimization target and proposed change.
+- Do not automatically modify the plugin based on this file. A human decides whether to accept each suggestion.
+- Merge duplicate symptoms into one finding. Keep at most the five highest-impact findings.
+- If there is no evidence-backed improvement, write `本次未发现需要提交给 Agent 维护者的优化建议。`
+
+## Output
+
+Use concise Chinese Markdown:
+
+```markdown
+# Agent 优化建议
+
+## 本次运行概况
+
+- 结果：完成 | 中止
+- 主要耗时或阻塞：
+- 人工介入：
+
+## 优先建议
+
+### AF-001：简短问题名称
+
+- 优先级：P0 | P1 | P2
+- 阶段：
+- 现象：
+- 证据：日志、命令、文件或提交路径
+- 影响：
+- 根因：已确认 | 假设，并说明原因
+- 优化位置：Agent | Skill | 脚本/工具 | 输入产物 | 流程 | 门禁
+- 建议：可执行的修改
+- 通用性：仅本项目 | 多项目通用
+```
+
+Use P0 only when the issue can block the whole workflow, corrupt work, or falsely declare migration success. Keep the overview factual; do not calculate metrics that were not captured by tools.