What makes zentao-bug-analyzer notable?

1.4K downloads. Trust evidence available

How should zentao-bug-analyzer be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

zentao-bug-analyzer

禅道缺陷自动分析：从飞书消息解析Bug链接，自动模块分类+分支定位+代码分析，Playwright评论+飞书通知双通道输出。 Skill: zentao-bug-analyzer Owner: yeah526 Summary: 禅道缺陷自动分析：从飞书消息解析Bug链接，自动模块分类+分支定位+代码分析，Playwright评论+飞书通知双通道输出。 Tags: latest:1.1.0 Version history: v1.1.0 | 2026-07-31T03:34:14.485Z | user **zentao-bug-analyzer v1.1.0** - 增加对 ffmpeg 环境依赖的自动检查，首次运行前强制校验，缺失时提示安装 npm 版本依赖。 - 新增用于视频附件抽帧与图片视觉分析的脚本和工具模块（scripts/zentao-extract-frames.js, scripts/zentao-utils.js）。 - 明确规定所有日志/文件操作必须用 Node.js（解决 Windows PowerShell 输出中文乱码问题）。

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.4k

Updated

Oct 10, 2026

Version

1.1.0

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.4K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.4K downloadsadoption · observed Oct 10, 2026
Latest release: 1.1.0release · observed Jul 31, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s171jrne9aa0bf40kzgc82gb318a7gba:zentao-bug-analyzer

Node.js workspace detected. Install dependencies securely: run `npm ci --ignore-scripts` to prevent post-install lifecycle triggers from running arbitrary code, then selectively audit the dependency tree.
Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-yeah526-zentao-bug-analyzer/snapshot"

Documentation

CLAWHUB

147,511 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: zentao-bug-analyzer
description: "禅道缺陷自动分析：从飞书消息解析Bug链接，自动模块分类+分支定位+代码分析，Playwright评论+飞书通知双通道输出。"
---

# 禅道缺陷自动分析 (zentao-bug-analyzer)

禅道实例：`http://zentao.gxatek.com:20080/`（企业版 12.1）

## 环境依赖

本 Skill 依赖以下工具，**环境不具备时立即停止流程并飞书通知用户**，禁止用替代品硬撑：

| 工具 | 用途 | 安装方式 | 验证命令 |
|------|------|----------|----------|
| **ffmpeg** | 视频附件抽帧（步骤 4b） | `npm install @ffmpeg-installer/ffmpeg ffprobe-static --no-save` | `node -e "console.log(require('@ffmpeg-installer/ffmpeg').path)"` |
| **Node.js zlib** | 解压 Android logcat `.gz` 日志（步骤 4c） | Node.js 内置，无需安装 | `node -e "require('zlib')"` |
| **Playwright** | 禅道交互（5 个 scripts） | 已有 | — |
| **视觉模型** | 读取截图/视频帧中的系统时间 + 判断画面中 BUG 现象是否可见（步骤 4b 子步骤 3、4） | 由 AI 代理运行环境提供 | — |

**禁止的替代方案**：
- ❌ 用 winget 装系统级 ffmpeg（实测 `winget install Gyan.FFmpeg` 超时不可靠）
- ❌ 用 PowerShell `tar`、`System.IO.Compression.GZipStream` 或 .NET 工具解压 logcat `.gz`（兼容性 bug，会丢失大量日志）
- ❌ 用 PowerShell/.NET 替代品处理视频（参考 4c 关于 .NET 解压 bug 的教训）

> ⚠️ **视觉模型不可用时**：步骤 4b 子步骤 3、4 无法读取截图/视频帧中的系统时间，降级为跳过图片/视频时间提取，直接进入子步骤 5 飞书询问用户。

**首次运行检查**：执行任何分析前先验证 ffmpeg 可用：
```bash
node -e "const ff=require('@ffmpeg-installer/ffmpeg');const{execSync}=require('child_process');execSync(`\"${ff.path}\" -version`);console.log('ffmpeg OK')"
```
失败 → 飞书私聊通知「ffmpeg 环境依赖缺失，请运行 `cd {workspace} && npm install @ffmpeg-installer/ffmpeg ffprobe-static --no-save` 后重试」，流程终止。

## ⚠️ 执行守则（最高优先级）

> 🔴 分析前必须先读完 `SKILL.checklist.md` 的全部检查项，每条逐项完成。

1. **只用 scripts/ 下的 5 个可执行脚本操作禅道**（不含 `zentao-utils.js` 工具模块），禁止手写临时 Playwright 文件
2. **一个 Bug 只启动一次浏览器**，所有操作复用同一 WS endpoint
3. **脚本报错 = 诊断脚本的输入条件**（WS 是否有效？参数是否正确？），不是另起炉灶的理由
4. **分析完成后保持仓库不动**：`git checkout <commit-id>` 分析完后不切回原分支（非 worktree 场景）。worktree 场景按步骤 6 清理。
5. **分析完输出报告**：步骤 4d 产出分析报告后，根据 `auto_comment` 配置决定是否评论禅道：
   - `auto_comment === true` 或未配置（默认视为 `true`）：运行 `zentao-post-comment.js` 评论 + 飞书摘要
   - `auto_comment === false`：仅飞书摘要，不评论禅道
6. **环境依赖缺失立即停止**：ffmpeg / Node.js zlib / Playwright 任一不可用 → 飞书通知用户安装，禁止用替代品硬撑（详见「环境依赖」章节）
7. **Windows 读取中文文件必须用 Node.js，禁止 PowerShell `Get-Content` / `Select-String`**：
   - Windows PowerShell 控制台默认 GBK（CP936）编码，读取 UTF-8 中文文件直接显示乱码
   - ❌ 禁止：`Get-Content xxx.txt -First 5`、`Select-String -Path xxx.txt -Pattern "中文"`、`Get-ChildItem | Where-Object Name -like '*.中文.txt'`
   - ✅ 必须：`node -e "console.log(require('fs').readFileSync('xxx.txt','utf8').slice(0,500))"`
   - 涉及场景：读取日志中的中文 TAG、中文注释、报告 review 时的中文文件名/路径、PowerShell 调用 `node script.js --video=中文.mp4` 时加 `--` 分隔符规避 argv 解析 bug
   - 例外：`Get-Content` 加上 `-Encoding UTF8` 参数可以读 UTF-8（输出仍可能乱码，但不会被识别为 ANSI）；推荐一律走 Node.js

## 触发方式

### 方式一：邮件转发触发
飞书 Bot 收到包含禅道 Bug 链接的消息时自动触发。

正则模式：`zentao\.gxatek\.com:20080/bug-view-(\d+)\.html`

### 方式二：自然语言触发
用户直接在飞书对话中：
- 发送禅道 Bug 链接
- 「帮我分析我名下所有未解决的缺陷」
- 「分析最近 3 天指派给我的严重缺陷」

**批量分析**：批量触发时，先通过 Playwright 会话查询 Bug 列表，每个 Bug 独立走完整流水线。不同 Bug 按第三章并发规则处理。

**无有效链接时**：飞书私聊回复「未识别到有效的禅道缺陷链接，请确认消息内容」。

---

## 配置文件

依赖 `{workspace}/bug-analyzer-config.json`。

```jsonc
{
  "zentao": {
    "url": "http://zentao.gxatek

_meta.json

{
  "ownerId": "kn7e1qtrtwmpapjt5hy2e9s4998a6wgq",
  "slug": "zentao-bug-analyzer",
  "version": "1.1.0",
  "publishedAt": 1785468854485
}

references/zentao-api-reference.md

# 禅道 API 参考

> 企业版 12.1 实例：`http://zentao.gxatek.com:20080/`
> 本文件为 API 字段/参数/错误码参考。实现示例见 `TOOLS.md`。

## 认证方式

企业版 12.1 不支持 Bearer Token（`POST /api.php/v1/tokens` 不可用）。所有操作统一通过 Playwright 登录获取 session cookie，后续请求在 `page.evaluate` 中用 `credentials: 'include'` 发起。

## Bug 详情

```
GET /api.php/v1/bugs/{bugId}
```

返回关键字段：

| 字段 | 类型 | 说明 |
|------|------|------|
| id | int | Bug ID |
| title | string | 标题（HTML） |
| description | string | 详细描述（HTML） |
| severity | int | 严重程度 1~4 |
| priority | int | 优先级 1~4 |
| product | object | `{ id, name }` |
| project | object | `{ id, name }` |
| module | object | `{ id, name }` |
| status | string | active / resolved / closed |
| openedBy | object | `{ id, account, name }` |
| assignedTo | object | `{ id, account, name }` |
| steps | string | 复现步骤（HTML） |
| files | array | 附件列表 `[{ id, title, extension, size }]` |
| comments | array | 评论列表 `[{ id, author, comment, date }]`，author 为 account 字符串 |

## Bug 列表

```
GET /api.php/v1/bugs?product={productId}&assignedTo={account}&limit=20&status=active
```

常用过滤参数：

| 参数 | 说明 |
|------|------|
| product | 产品 ID |
| assignedTo | 指派人账号 |
| status | active / resolved / closed |
| severity | 1~4 |
| limit | 分页条数 |
| offset | 分页偏移 |

## 产品列表

```
GET /api.php/v1/products
```

## 写评论

通过 `scripts/zentao-post-comment.js` 完成。POST `{zentao_url}/action-comment-bug-{bugId}.html`，Content-Type: `application/x-www-form-urlencoded`，body: `comment={URL-encoded HTML}`。传入原始 HTML 即可，脚本自动编码。

## 附件下载

附件 URL: `{zentao_url}/file-download-{fileId}.json`。下载通过 `scripts/zentao-download-files.js` 完成（内部使用 page.evaluate + exposeFunction 分块传输，支持 160MB+ 大文件）。

## 错误码

| 状态码 | 含义 | 处理 |
|--------|------|------|
| 200 | 成功 | — |
| 401 | Session 过期 | 重新 Playwright 登录 |
| 404 | 资源不存在 | 通知用户检查 ID |
| 500 | 服务端错误 | 通知用户检查禅道状态 |

scripts/package.json

{
  "name": "zentao-bug-analyzer-scripts",
  "private": true,
  "description": "禅道缺陷自动分析 - Playwright 脚本集",
  "engines": {
    "node": ">=18"
  },
  "dependencies": {
    "playwright": "^1.40.0"
  },
  "devDependencies": {
    "@ffmpeg-installer/ffmpeg": "^1.1.0",
    "ffprobe-static": "^3.1.0"
  }
}

skill-card.md

## Description:

Analyzes ZenTao bug reports from Feishu-triggered links by gathering bug details, attachments, logs, local code context, and producing a root-cause report with optional ZenTao and Feishu updates.

This skill is ready for commercial/non-commercial use.

## Publisher:

[yeah526](https://clawhub.ai/user/yeah526)

### License/Terms of Use:

MIT-0

## Use Case:

Developers and QA engineers use this skill to triage ZenTao defects, identify the affected module and branch, inspect logs and attachments, and prepare a concise root-cause analysis. It can also format the report for ZenTao comments and send a Feishu summary when configured.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The skill requires sensitive ZenTao credentials and broad local/browser authority.

Mitigation: Use a low-privilege ZenTao account, HTTPS, isolated disposable worktrees or containers, and pinned dependencies; do not store real passwords in workspace config until credential handling and CDP/browser exposure are fixed.

Risk: Automatic ZenTao comments could publish incomplete or incorrect analysis.

Mitigation: Review generated reports before posting, and set auto_comment to false when manual approval is required.

Risk: Bug analysis can modify local repository state through checkout or worktree operations.

Mitigation: Run analysis in disposable or isolated worktrees and verify cleanup of worktrees, browser sessions, and ZenTao helper processes after each run.

## Reference(s):

- [ZenTao API Reference](artifact/references/zentao-api-reference.md)
- [ClawHub Skill Page](https://clawhub.ai/yeah526/skills/zentao-bug-analyzer)

## Skill Output:

**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance]

**Output Format:** [Markdown reports with shell command guidance, JSON metadata, HTML comment output, and Feishu-ready text summaries]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [May write local bug artifacts such as downloaded attachments, extracted video frames, time metadata, reports, and comment HTML.]

## Skill Version(s):

1.1.0 (source: server release metadata; target metadata agrees)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 21h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.