编码管理
- 作者仓库星标 0
- 作者仓库 skills-registry
- 领域
- 人工智能
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tomevault-io · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第 1 步:首次检测(分配编码任务之前)
当`~/coding-cli-config.json`不存在时运行:如果没有可用的CLI(`available`数组为空):继续正常任务分配(工作人员代码自己)。如果 CLI 可用,请通过主要渠道或 Matrix DM 询问管理员 - 使用管理员使用的语言:我发现以下可用的 AI 编码 CLI 工具:[列表]。您想启用 CLI 委派模式吗?工作人员将生成编码提示,我将使用 CLI 工具进行代码更改。回复工具名称 (claude/gemini/qodercli) 以启用,或回复“否”以让工作人员自行编写代码。
步骤 2:分配编码任务(启用 CLI 模式)
当`coding-cli-config.json`具有`enabled: true`时:确保工人具有`coding-cli`技能。检查`workers-registry.json`:如果`coding-cli`丢失,则分发它:将“编码CLI模式”部分添加到spec.md(请参阅下面的模板)。
步骤 3:处理编码请求:消息
当 Worker 发送包含 `coding-request:` 的消息时(在其 Worker Room 或 Project Room 中): 解析消息: 执行:成功时 — 发送给同一 Room 中的 Worker:失败时(退出 ≠ 0 或超时) — 参见步骤 4。
第四步:处理失败
通知任务室的工作人员:通过主通道通知管理员(参见通道管理技能“向主通道发送消息”): 在配置中记录(可选,用于心跳诊断):
# Coding CLI Management
This skill enables the Manager to execute AI coding CLI tools (claude/gemini/qodercli) on behalf of Workers. Workers generate precise prompts; the Manager runs the CLI in the Worker's workspace and returns the result.
## Config File
Path: `~/coding-cli-config.json`
```json
{
"enabled": true,
"cli": "claude",
"confirmed_at": "2026-02-23T10:00:00Z"
}
```
| `enabled` | `cli` | Meaning |
|-----------|-------|---------|
| `false` | any | Admin declined; use normal task flow |
| `true` | `"claude"` / `"gemini"` / `"qodercli"` | Active — use this CLI |
---
## Step 1: First-Time Detection (before assigning a coding task)
Run when `~/coding-cli-config.json` does not exist:
```bash
bash /opt/hiclaw/agent/skills/coding-cli-management/scripts/detect-available-cli.sh
```
**If no CLIs are available** (`available` array is empty):
```bash
echo '{"enabled":false,"cli":null,"confirmed_at":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}' \
> ~/coding-cli-config.json
```
Proceed with normal task assignment (Worker codes on their own).
**If CLIs are available**, ask the admin via the primary channel or Matrix DM — **in the language the admin used**:
> I found the following AI coding CLI tools available: [list]. Would you like to enable CLI delegation mode? Workers will generate coding prompts, and I'll use the CLI tool to make the code changes. Reply with the tool name (claude/gemini/qodercli) to enable, or 'no' to have workers code on their own.
On admin reply:
- Tool name (`claude` / `gemini` / `qodercli`):
```bash
echo '{"enabled":true,"cli":"<chosen-tool>","confirmed_at":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}' \
> ~/coding-cli-config.json
```
- `"no"` or decline:
```bash
echo '{"enabled":false,"cli":null,"confirmed_at":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}' \
> ~/coding-cli-config.json
```
---
## Step 2: Assigning a Coding Task (CLI mode enabled)
When `coding-cli-config.json` has `enabled: true`:
1. **Ensure the Worker has the `coding-cli` skill.** Check `workers-registry.json`:
```bash
cat ~/workers-registry.json | jq '.workers[] | select(.name=="<worker>") | .skills'
```
If `coding-cli` is missing, distribute it:
```bash
bash /opt/hiclaw/agent/skills/worker-management/scripts/push-worker-skills.sh \
--worker <worker-name> --skill coding-cli
```
2. **Add a "Coding CLI Mode" section to spec.md** (see template below).
---
## Step 3: Handling a `coding-request:` Message
When a Worker sends a message containing `coding-request:` (in their Worker Room or a Project Room):
**Parse the message:**
```
task-{task-id} coding-request:
workspace: /root/hiclaw-fs/shared/tasks/{task-id}/workspace
---PROMPT---
{prompt content}
---END---
```
**Execute:**
```bash
# 1. Sync workspace from MinIO
task_id="task-YYYYMMDD-HHMMSS"
workspace="/root/hiclaw-fs/shared/tasks/${task_id}/workspace"
mc mirror "${HICLAW_STORAGE_PREFIX}/shared/tasks/${task_id}/" "/root/hiclaw-fs/shared/tasks/${task_id}/"
# 2. Check for processing marker (task coordination)
bash /opt/hiclaw/agent/skills/task-coordination/scripts/check-processing-marker.sh "$task_id"
if [ $? -ne 0 ]; then
# Another process is working on this task
echo "Task ${task_id} is being processed by another operation. Retry later."
exit 1
fi
# 3. Create processing marker
bash /opt/hiclaw/agent/skills/task-coordination/scripts/create-processing-marker.sh "$task_id" "manager" 15
# 4. Save prompt to file
timestamp=$(date +%Y%m%d-%H%M%S)
prompt_dir="/root/hiclaw-fs/shared/tasks/${task_id}/coding-prompts"
mkdir -p "$prompt_dir"
prompt_file="$prompt_dir/${timestamp}.txt"
cat > "$prompt_file" << 'PROMPT_EOF'
{extracted prompt content}
PROMPT_EOF
# 5. Get configured CLI
cli=$(jq -r '.cli' ~/coding-cli-config.json)
# 6. Run CLI
bash /opt/hiclaw/agent/skills/coding-cli-management/scripts/run-coding-cli.sh \
--cli "$cli" \
--workspace "$workspace" \
--prompt-file "$prompt_file" \
--timeout 600
exit_code=$?
# 7. Remove processing marker
bash /opt/hiclaw/agent/skills/task-coordination/scripts/remove-processing-marker.sh "$task_id"
# 8. On success (exit 0): push changes to MinIO
if [ "$exit_code" -eq 0 ]; then
mc mirror "/root/hiclaw-fs/shared/tasks/${task_id}/workspace/" "${HICLAW_STORAGE_PREFIX}/shared/tasks/${task_id}/workspace/" --overwrite
fi
```
**On success** — send to Worker in the same Room:
```
@{worker}:DOMAIN task-{task-id} coding-result:
CLI 工具已完成编码。请同步工作目录并 review 变更:
hiclaw-sync
变更记录:/root/hiclaw-fs/shared/tasks/{task-id}/workspace/coding-cli-logs/
```
**On failure** (exit ≠ 0 or timeout) — see Step 4.
---
## Step 4: Handling Failure
**Notify Worker** in the task Room:
```
@{worker}:DOMAIN task-{task-id} coding-failed:
CLI 工具执行失败(exit code: {code})。请自行完成编码任务。
你生成的提示词已保存于:/root/hiclaw-fs/shared/tasks/{task-id}/coding-prompts/
```
**Notify Human Admin** via primary channel (see channel-management skill "Sending Messages to Primary Channel"):
```
Worker {worker-name} 的编码委托任务 {task-id} 中,{cli} 工具执行失败。
错误信息:{last lines from log file}
建议检查:
- ~/.{cli}/ 凭证是否有效(token 是否过期)
- /host-share/.{cli}/ 软链是否正常(ls -la /root/.{cli})
- {cli} binary 是否在容器内可用(which {cli})
```
**Record in config** (optional, for heartbeat diagnostics):
```bash
jq --arg ts "$(date -u +%Y-%m-%dT%H:%M:%SZ)" --arg tid "$task_id" \
'.last_failure = {task_id: $tid, failed_at: $ts}' \
~/coding-cli-config.json > /tmp/cfg.json && \
mv /tmp/cfg.json ~/coding-cli-config.json
```
---
## Spec.md Coding CLI Mode Template
Append to the end of spec.md when CLI mode is enabled:
```markdown
## Coding CLI Mode
本任务涉及代码修改。请使用 **Coding CLI 委托模式** 完成:
1. 克隆/准备代码到工作目录:`/root/hiclaw-fs/shared/tasks/{task-id}/workspace/`
2. 推送到 MinIO:`mc mirror /root/hiclaw-fs/shared/tasks/{task-id}/workspace/ ${HICLAW_STORAGE_PREFIX}/shared/tasks/{task-id}/workspace/`
3. 根据你的理解和 `coding-cli` skill 生成编码提示词,发送给我
4. 等待我执行 CLI 工具并返回结果
5. Sync 拉取变更:`hiclaw-sync`
6. Review 变更并报告完成
如收到 `coding-failed:`,请自行完成编码工作。
```
---
> Source: [agentscope-ai/HiClaw](https://github.com/agentscope-ai/HiClaw) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-23 -->
章节与文件索引
按说明文件中的顺序排列。
配置文件
第 1 步:首次检测(分配编码任务之前)
步骤 2:分配编码任务(启用 CLI 模式)
步骤 3:处理编码请求:消息
第四步:处理失败
文件/命令 -> ~/coding-cli-config.json · enabled · cli · false · true · "claude" · "gemini" · "qodercli"
内容校验值 -> 1a5ca3250b9b
当前原文的自动摘译,尚未人工审校。
配置文件
路径:
~/coding-cli-config.jsonenabled·cli· 含义false· 任何 · 管理员拒绝;使用正常任务流程true·"claude"/"gemini"/"qodercli"· 活动 — 使用此 CLI步骤 3:处理编码请求:消息
当 Worker 发送包含
coding-request:的消息时(在其 Worker Room 或 Project Room 中): 解析消息: 执行:成功时 — 发送给同一个 Room 中的 Worker:失败时(退出 ≠ 0 或超时) — 参见步骤 4。