Xpersona

Crawler Summary

bug-investigation answer-first brief

Systematic 5-phase bug investigation workflow for unexpected behavior, test failures, performance regressions, data inconsistencies, and root cause tracing. Use when users ask to investigate/trace bugs or data flow (e.g., bug investigation, 測試失敗, 效能異常, 調查 Bug, 追蹤資料流, root cause analysis). --- name: bug-investigation description: "Systematic 5-phase bug investigation workflow for unexpected behavior, test failures, performance regressions, data inconsistencies, and root cause tracing. Use when users ask to investigate/trace bugs or data flow (e.g., bug investigation, 測試失敗, 效能異常, 調查 Bug, 追蹤資料流, root cause analysis)." --- Bug Investigation Skill 概述 一套系統化方法，用於調查複雜程式碼中的錯誤與異常行為。此技能包含五個階段： 1. **問題釐清** - 理解回報 Capability contract not published. No trust telemetry is available yet. 1 GitHub stars reported by the source. Last updated 4/15/2026.

Freshness

Last checked 4/15/2026

Best For

bug-investigation is best for general automation workflows where OpenClaw compatibility matters.

Not Ideal For

Contract metadata is missing or unavailable for deterministic execution.

Evidence Sources Checked

editorial-content, GITHUB OPENCLEW, runtime-metrics, public facts pack

CardFactsSnapshotContractTrust
Claim this agent
Agent DossierGitHubSafety: 94/100

bug-investigation

Systematic 5-phase bug investigation workflow for unexpected behavior, test failures, performance regressions, data inconsistencies, and root cause tracing. Use when users ask to investigate/trace bugs or data flow (e.g., bug investigation, 測試失敗, 效能異常, 調查 Bug, 追蹤資料流, root cause analysis). --- name: bug-investigation description: "Systematic 5-phase bug investigation workflow for unexpected behavior, test failures, performance regressions, data inconsistencies, and root cause tracing. Use when users ask to investigate/trace bugs or data flow (e.g., bug investigation, 測試失敗, 效能異常, 調查 Bug, 追蹤資料流, root cause analysis)." --- Bug Investigation Skill 概述 一套系統化方法，用於調查複雜程式碼中的錯誤與異常行為。此技能包含五個階段： 1. **問題釐清** - 理解回報

OpenClawself-declared

Public facts

5

Change events

1

Artifacts

0

Freshness

Apr 15, 2026

Verifiededitorial-contentNo verified compatibility signals1 GitHub stars

Capability contract not published. No trust telemetry is available yet. 1 GitHub stars reported by the source. Last updated 4/15/2026.

1 GitHub starsTrust evidence available

Trust score

Unknown

Compatibility

OpenClaw

Freshness

Apr 15, 2026

Vendor

Hmj1026

Artifacts

0

Benchmarks

0

Last release

Unpublished

Executive Summary

Key links, install path, and a quick operational read before the deeper crawl record.

Verifiededitorial-content

Summary

Capability contract not published. No trust telemetry is available yet. 1 GitHub stars reported by the source. Last updated 4/15/2026.

View Source

Setup snapshot

git clone https://github.com/hmj1026/bug-investigation.git
  1. 1

    Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.

  2. 2

    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.

Evidence Ledger

Everything public we have scraped or crawled about this agent, grouped by evidence type with provenance.

Verifiededitorial-content
Vendor (1)

Vendor

Hmj1026

profilemedium
Observed Apr 15, 2026Source linkProvenance
Compatibility (1)

Protocol compatibility

OpenClaw

contractmedium
Observed Apr 15, 2026Source linkProvenance
Adoption (1)

Adoption signal

1 GitHub stars

profilemedium
Observed Apr 15, 2026Source linkProvenance
Security (1)

Handshake status

UNKNOWN

trustmedium
Observed unknownSource linkProvenance
Integration (1)

Crawlable docs

6 indexed pages on the official domain

search_documentmedium
Observed Apr 15, 2026Source linkProvenance

Release & Crawl Timeline

Merged public release, docs, artifact, benchmark, pricing, and trust refresh events.

Self-declaredagent-index

Docs Update

Docs refreshed: Sign in to GitHub · GitHub

search_documentmedium

Fresh crawlable documentation was indexed for the official domain.

Observed Apr 15, 2026

Artifacts Archive

Extracted files, examples, snippets, parameters, dependencies, permissions, and artifact metadata.

Self-declaredGITHUB OPENCLEW

Extracted files

0

Examples

6

Snippets

0

Languages

typescript

Parameters

Executable Examples

text

未完成 Phase 1-3（尤其 Phase 3），不得提出修正方案或修改程式碼。

text

docs/knowledge/
├── [feature-name]/
│   ├── investigation.md      # 調查總表與進度
│   ├── data-flow.md           # 資料流圖解
│   ├── key-functions.md       # 關鍵函數說明
│   ├── related-tables.md      # 相關資料表結構
│   └── solution-proposal.md   # 修正方案與決策依據

text

1. 使用者動作 → [函式/API]
           ↓
2. 前端處理 → [JS 函式]
           ↓
3. 後端 API → [Controller/Action]
           ↓
4. 資料庫寫入 → [資料表]

bash

# 使用 ripgrep (推薦)
   rg "<variable_name>" --type php --type js
   
   # 或使用技能提供的腳本
   ./scripts/trace-data-flow.sh <variable_name>
   
   # 搜尋資料表操作
   ./scripts/search-database-queries.sh <table_name>

bash

/opsx:new   # 依推薦方案命名 change（kebab-case）

bash

# 搜尋知識庫是否已有相關文件
ls docs/knowledge/

Docs & README

Full documentation captured from public sources, including the complete README when available.

Self-declaredGITHUB OPENCLEW

Docs source

GITHUB OPENCLEW

Editorial quality

ready

Systematic 5-phase bug investigation workflow for unexpected behavior, test failures, performance regressions, data inconsistencies, and root cause tracing. Use when users ask to investigate/trace bugs or data flow (e.g., bug investigation, 測試失敗, 效能異常, 調查 Bug, 追蹤資料流, root cause analysis). --- name: bug-investigation description: "Systematic 5-phase bug investigation workflow for unexpected behavior, test failures, performance regressions, data inconsistencies, and root cause tracing. Use when users ask to investigate/trace bugs or data flow (e.g., bug investigation, 測試失敗, 效能異常, 調查 Bug, 追蹤資料流, root cause analysis)." --- Bug Investigation Skill 概述 一套系統化方法，用於調查複雜程式碼中的錯誤與異常行為。此技能包含五個階段： 1. **問題釐清** - 理解回報

Full README

name: bug-investigation description: "Systematic 5-phase bug investigation workflow for unexpected behavior, test failures, performance regressions, data inconsistencies, and root cause tracing. Use when users ask to investigate/trace bugs or data flow (e.g., bug investigation, 測試失敗, 效能異常, 調查 Bug, 追蹤資料流, root cause analysis)."

Bug Investigation Skill

概述

一套系統化方法，用於調查複雜程式碼中的錯誤與異常行為。此技能包含五個階段：

  1. 問題釐清 - 理解回報的問題與影響範圍
  2. 證據蒐集 - 從資料庫與日誌收集可驗證的證據
  3. 根因分析 - 追蹤資料流找出來源與分歧點
  4. 修正方案設計 - 提出與評估解決方案並形成決策依據
  5. 知識文件化 - 留存可重用的知識與調查結果

核心鐵律

未完成 Phase 1-3（尤其 Phase 3），不得提出修正方案或修改程式碼。

強制要求：

  • 所有五個階段必須完成，不可跳過。若受阻，必須記錄原因、缺口與下一步，並在調查文件中標示未完成狀態。
  • 未完成 Phase 1-3 前禁止提出修正方案或改動程式碼。
  • 所有輸出文件與報告以正體中文為主；保留原始 log、程式碼與欄位名稱。

紅旗（出現即停止，回到 Phase 1）

  • 「先快修再說，之後再查」
  • 「先改幾個地方試試看」
  • 「我不確定但先試」
  • 「先跳過測試，手動驗證就好」
  • 連續修復 2 次仍失敗，準備嘗試第 3 次

使用者提示你方向錯了

  • 「這樣真的有證據嗎？」
  • 「會不會根本不是那一層？」
  • 「先停一下，不要猜」

知識庫

調查過程中獲得的程式功能邏輯文件應同步存放在專案內部的知識庫資料夾：

docs/knowledge/
├── [feature-name]/
│   ├── investigation.md      # 調查總表與進度
│   ├── data-flow.md           # 資料流圖解
│   ├── key-functions.md       # 關鍵函數說明
│   ├── related-tables.md      # 相關資料表結構
│   └── solution-proposal.md   # 修正方案與決策依據

好處：

  • 知識庫與專案程式碼一同版本控制
  • 團隊成員可共享調查結果
  • 日後調查類似問題時可先查閱
  • 減少重複的 code tracing

範例參考：references/examples.md 與 examples/state-inconsistency-example/。

參考

  • references/scripts.md：工具安裝與腳本使用說明
  • references/examples.md：調查案例與寫作模板
  • references/root-cause-tracing.md：根因回溯追蹤技巧
  • references/defense-in-depth.md：多層防護驗證模式
  • references/condition-based-waiting.md：以條件為基準的等待（解決 flaky 測試）
  • references/wait-for-helper.ts：條件等待 helper 範本（可直接複製）
  • references/phase-templates.md：各 Phase 文件與 SQL/表格模板
  • references/checklists.md：完整檢查清單

Phase 1: 問題釐清

提示：首次使用先執行 ./scripts/check-tools.sh（詳見 references/scripts.md）。

1.1 收集初始資訊

向使用者詢問以下資訊：

  • [ ] 問題描述：預期行為與實際行為的差異為何？
  • [ ] 樣本資料：具體的 ID、時間戳記或交易編號
  • [ ] 可重現性：問題是否能穩定重現？
  • [ ] 環境資訊：受影響的環境、系統或資料庫

1.2 建立調查文件

在 docs/knowledge/[feature-name]/investigation.md 建立調查文件，模板見 references/phase-templates.md。

Phase 2: 證據蒐集

2.1 資料庫驗證

產生 SQL 查詢以驗證問題，模板見 references/phase-templates.md。

2.2 記錄發現

在 docs/knowledge/[feature-name]/investigation.md 中記錄資料庫證據，表格模板見 references/phase-templates.md。

2.3 識別矛盾點

尋找資料不一致的地方：

  • [ ] 相關資料表的資料是否匹配？
  • [ ] Log 記錄是否與交易資料一致？
  • [ ] 資料中是否有時序問題？

2.4 跨層蒐證（多元件系統）

當流程跨越多層（前端 → API → 背景作業 → DB）時：

  • [ ] 在每一層記錄「輸入」與「輸出」的資料
  • [ ] 檢查設定/環境變數是否正確傳遞
  • [ ] 一次收集證據以定位斷裂的層級

Phase 3: 根因分析

3.1 追蹤資料流向

描繪資料從輸入到資料庫的完整路徑：

1. 使用者動作 → [函式/API]
           ↓
2. 前端處理 → [JS 函式]
           ↓
3. 後端 API → [Controller/Action]
           ↓
4. 資料庫寫入 → [資料表]

需要完整回溯技巧時，參考 references/root-cause-tracing.md。

3.2 對照可運作範例

  • [ ] 找出同專案中相似且正常的流程/程式碼
  • [ ] 完整閱讀，不要略過細節
  • [ ] 列出所有差異（哪怕很小）

3.3 程式碼調查

對資料流中的每個步驟：

  1. 搜尋關鍵變數 (使用專業工具):

    # 使用 ripgrep (推薦)
rg "<variable_name>" --type php --type js

# 或使用技能提供的腳本
./scripts/trace-data-flow.sh <variable_name>

# 搜尋資料表操作
./scripts/search-database-queries.sh <table_name>

  2. 追蹤資料來源：

    • 哪個函式計算或提供此值？
    • 資料如何從前端傳遞到後端？
    • 使用 analyze-function-calls.sh 分析函式呼叫關係

  3. 識別分歧點：

    • 預期與實際行為在哪裡分歧？
    • 什麼條件導致進入錯誤的路徑？
    • 使用 generate-flow-diagram.sh 生成流程圖輔助分析

3.4 單一假設與最小驗證

  • [ ] 明確寫下單一假設：「我認為 X 是根因，因為 Y」
  • [ ] 設計最小修改或最小檢查來驗證
  • [ ] 驗證失敗就回到 3.1-3.3 重新建立假設

3.5 記錄根本原因

更新 docs/knowledge/[feature-name]/investigation.md，模板見 references/phase-templates.md。

Phase 4: 修正方案設計

4.1 建立修正方案文件（必做）

在 docs/knowledge/[feature-name]/solution-proposal.md 記錄修正方案與判斷依據，模板見 references/phase-templates.md。

4.2 設計解決方案選項

提出 2-3 個解決方案，並回填到 solution-proposal.md。

4.3 推薦解決方案

向使用者呈現建議：

  • 推薦哪個選項？為什麼？
  • 有什麼風險？
  • 需要什麼測試？

4.4 建立失敗測試/最小重現（必做）

  • [ ] 建立最小可重現案例或自動化測試
  • [ ] 有測試框架時先寫 failing test
  • [ ] 需要完整測試流程時使用 test-driven-development 技能
  • [ ] 若是 flaky/timeout，改用 references/condition-based-waiting.md 的條件等待

4.5 建立 OpenSpec（強制，無例外）

Phase 4 完成後必須進入 OpenSpec 流程，不得跳過：

/opsx:new   # 依推薦方案命名 change（kebab-case）

依序建立所有 artifacts：

  • proposal.md - 根因摘要 + 推薦方案
  • design.md - 技術決策與架構
  • specs/[capability]/spec.md - 行為規格
  • tasks.md - 實作檢查清單

建立完成後執行 /opsx:apply 按 TDD 實作。

鐵律： bug-investigation 觸發 → 調查完成 → 必接 OpenSpec → 再實作。 不允許從 Phase 4 直接跳到程式碼修改。

4.6 修復連續失敗時的停損

  • [ ] 已嘗試修復 2 次仍失敗：回到 Phase 1-3 重新調查
  • [ ] 已嘗試 3 次仍失敗：停止再修，先討論架構/設計問題

修復涉及資料驗證時，採用 references/defense-in-depth.md 的多層防護。

Phase 5: 知識文件化

5.1 檢查現有知識庫

在深入研究程式碼之前，檢查是否已有相關文件：

# 搜尋知識庫是否已有相關文件
ls docs/knowledge/

5.2 建立功能知識文件

調查完成後，記錄功能邏輯供未來參考： 建立以下文件，模板見 references/phase-templates.md：

  • data-flow.md
  • key-functions.md
  • related-tables.md

5.3 更新檢查清單

檢查清單模板見 references/checklists.md。

關鍵原則

調查方法論

  • 追隨資料 - 從來源追蹤數值到目的地
  • 信任證據 - 資料庫記錄不會說謊
  • 一次一個假設 - 先測試和驗證再前進
  • 記錄一切 - 保留調查軌跡

溝通方式

  • 全程正體中文 - 所有輸出與文件維持正體中文
  • 游進式報告 - 不要等到最後才報告
  • 提出澄清問題 - 與使用者驗證假設
  • 解釋推理 - 幫助使用者理解分析

解決方案設計

  • 最小變更原則 - 只修復損壞的部分
  • 預防未來問題 - 考慮如何避免類似的 bug
  • 完整測試 - 驗證修復不會引入新問題

例外處理（仍須完成 Phase 1-5）

若調查確認問題源於外部系統/環境/時序：

  • 清楚記錄證據與限制
  • 在 Phase 4 設計防護（重試、timeout、錯誤訊息、監控）
  • 在 Phase 5 留下觀測點

檢查清單總結

完整版本請見 references/checklists.md。

Contract & API

Machine endpoints, protocol fit, contract coverage, invocation examples, and guardrails for agent-to-agent use.

MissingGITHUB OPENCLEW

Endpoints

Dossier APISnapshot APIContract APITrust API

Contract coverage

Status

missing

Auth

None

Streaming

No

Data region

Unspecified

Protocol support

OpenClaw: self-declared

Requires: none

Forbidden: none

Guardrails

Operational confidence: low

No positive guardrails captured.
Invocation examples
curl -s "https://xpersona.co/api/v1/agents/hmj1026-bug-investigation/snapshot"
curl -s "https://xpersona.co/api/v1/agents/hmj1026-bug-investigation/contract"
curl -s "https://xpersona.co/api/v1/agents/hmj1026-bug-investigation/trust"

Reliability & Benchmarks

Trust and runtime signals, benchmark suites, failure patterns, and practical risk constraints.

Missingruntime-metrics

Trust signals

Handshake

UNKNOWN

Confidence

unknown

Attempts 30d

unknown

Fallback rate

unknown

Runtime metrics

Observed P50

unknown

Observed P95

unknown

Rate limit

unknown

Estimated cost

unknown

Do not use if

Contract metadata is missing or unavailable for deterministic execution.
No benchmark suites or observed failure patterns are available.

Media & Demo

Every public screenshot, visual asset, demo link, and owner-provided destination tied to this agent.

Missingno-media
No screenshots, media assets, or demo links are available.

Related Agents

Neighboring agents from the same protocol and source ecosystem for comparison and shortlist building.

Self-declaredprotocol-neighbors
GITHUB_REPOSactivepieces

Rank

70

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

Traction

No public download signal

Freshness

Updated 2d ago

OPENCLAW
GITHUB_REPOScherry-studio

Rank

70

AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs

Traction

No public download signal

Freshness

Updated 5d ago

MCPOPENCLAW
GITHUB_REPOSAionUi

Rank

70

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!

Traction

No public download signal

Freshness

Updated 6d ago

MCPOPENCLAW
GITHUB_REPOSCopilotKit

Rank

70

The Frontend for Agents & Generative UI. React + Angular

Traction

No public download signal

Freshness

Updated 23d ago

OPENCLAW
Agent hubMore from this sourceOpenClaw agents
Machine Appendix

Contract JSON

{
  "contractStatus": "missing",
  "authModes": [],
  "requires": [],
  "forbidden": [],
  "supportsMcp": false,
  "supportsA2a": false,
  "supportsStreaming": false,
  "inputSchemaRef": null,
  "outputSchemaRef": null,
  "dataRegion": null,
  "contractUpdatedAt": null,
  "sourceUpdatedAt": null,
  "freshnessSeconds": null
}

Invocation Guide

{
  "preferredApi": {
    "snapshotUrl": "https://xpersona.co/api/v1/agents/hmj1026-bug-investigation/snapshot",
    "contractUrl": "https://xpersona.co/api/v1/agents/hmj1026-bug-investigation/contract",
    "trustUrl": "https://xpersona.co/api/v1/agents/hmj1026-bug-investigation/trust"
  },
  "curlExamples": [
    "curl -s \"https://xpersona.co/api/v1/agents/hmj1026-bug-investigation/snapshot\"",
    "curl -s \"https://xpersona.co/api/v1/agents/hmj1026-bug-investigation/contract\"",
    "curl -s \"https://xpersona.co/api/v1/agents/hmj1026-bug-investigation/trust\""
  ],
  "jsonRequestTemplate": {
    "query": "summarize this repo",
    "constraints": {
      "maxLatencyMs": 2000,
      "protocolPreference": [
        "OPENCLEW"
      ]
    }
  },
  "jsonResponseTemplate": {
    "ok": true,
    "result": {
      "summary": "...",
      "confidence": 0.9
    },
    "meta": {
      "source": "GITHUB_OPENCLEW",
      "generatedAt": "2026-04-16T23:41:18.267Z"
    }
  },
  "retryPolicy": {
    "maxAttempts": 3,
    "backoffMs": [
      500,
      1500,
      3500
    ],
    "retryableConditions": [
      "HTTP_429",
      "HTTP_503",
      "NETWORK_TIMEOUT"
    ]
  }
}

Trust JSON

{
  "status": "unavailable",
  "handshakeStatus": "UNKNOWN",
  "verificationFreshnessHours": null,
  "reputationScore": null,
  "p95LatencyMs": null,
  "successRate30d": null,
  "fallbackRate": null,
  "attempts30d": null,
  "trustUpdatedAt": null,
  "trustConfidence": "unknown",
  "sourceUpdatedAt": null,
  "freshnessSeconds": null
}

Capability Matrix

{
  "rows": [
    {
      "key": "OPENCLEW",
      "type": "protocol",
      "support": "unknown",
      "confidenceSource": "profile",
      "notes": "Listed on profile"
    }
  ],
  "flattenedTokens": "protocol:OPENCLEW|unknown|profile"
}

Facts JSON

[
  {
    "factKey": "docs_crawl",
    "category": "integration",
    "label": "Crawlable docs",
    "value": "6 indexed pages on the official domain",
    "href": "https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fopenclaw%2Fskills%2Ftree%2Fmain%2Fskills%2Fasleep123%2Fcaldav-calendar",
    "sourceUrl": "https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fopenclaw%2Fskills%2Ftree%2Fmain%2Fskills%2Fasleep123%2Fcaldav-calendar",
    "sourceType": "search_document",
    "confidence": "medium",
    "observedAt": "2026-04-15T05:03:46.393Z",
    "isPublic": true
  },
  {
    "factKey": "vendor",
    "category": "vendor",
    "label": "Vendor",
    "value": "Hmj1026",
    "href": "https://github.com/hmj1026/bug-investigation",
    "sourceUrl": "https://github.com/hmj1026/bug-investigation",
    "sourceType": "profile",
    "confidence": "medium",
    "observedAt": "2026-04-15T00:19:07.472Z",
    "isPublic": true
  },
  {
    "factKey": "protocols",
    "category": "compatibility",
    "label": "Protocol compatibility",
    "value": "OpenClaw",
    "href": "https://xpersona.co/api/v1/agents/hmj1026-bug-investigation/contract",
    "sourceUrl": "https://xpersona.co/api/v1/agents/hmj1026-bug-investigation/contract",
    "sourceType": "contract",
    "confidence": "medium",
    "observedAt": "2026-04-15T00:19:07.472Z",
    "isPublic": true
  },
  {
    "factKey": "traction",
    "category": "adoption",
    "label": "Adoption signal",
    "value": "1 GitHub stars",
    "href": "https://github.com/hmj1026/bug-investigation",
    "sourceUrl": "https://github.com/hmj1026/bug-investigation",
    "sourceType": "profile",
    "confidence": "medium",
    "observedAt": "2026-04-15T00:19:07.472Z",
    "isPublic": true
  },
  {
    "factKey": "handshake_status",
    "category": "security",
    "label": "Handshake status",
    "value": "UNKNOWN",
    "href": "https://xpersona.co/api/v1/agents/hmj1026-bug-investigation/trust",
    "sourceUrl": "https://xpersona.co/api/v1/agents/hmj1026-bug-investigation/trust",
    "sourceType": "trust",
    "confidence": "medium",
    "observedAt": null,
    "isPublic": true
  }
]

Change Events JSON

[
  {
    "eventType": "docs_update",
    "title": "Docs refreshed: Sign in to GitHub · GitHub",
    "description": "Fresh crawlable documentation was indexed for the official domain.",
    "href": "https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fopenclaw%2Fskills%2Ftree%2Fmain%2Fskills%2Fasleep123%2Fcaldav-calendar",
    "sourceUrl": "https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fopenclaw%2Fskills%2Ftree%2Fmain%2Fskills%2Fasleep123%2Fcaldav-calendar",
    "sourceType": "search_document",
    "confidence": "medium",
    "observedAt": "2026-04-15T05:03:46.393Z",
    "isPublic": true
  }
]

Sponsored

Ads related to bug-investigation and adjacent AI workflows.