Crawler Summary

postmortem answer-first brief

Use when analyzing fix commits to create postmortems, checking code changes against known issues before release, or updating postmortem knowledge base after release. Triggers on /postmortem command with onboard, check, or update arguments. --- name: postmortem description: Use when analyzing fix commits to create postmortems, checking code changes against known issues before release, or updating postmortem knowledge base after release. Triggers on /postmortem command with onboard, check, or update arguments. argument-hint: "[onboard | check [base] | update [range]]" metadata: author: jerikchan version: "1.0.0" --- Postmortem 驱动开发 Overview 通过 postmortem Capability contract not published. No trust telemetry is available yet. Last updated 4/15/2026.

Freshness

Last checked 4/15/2026

Best For

postmortem 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

Claim this agent
Agent DossierGitHubSafety: 94/100

postmortem

Use when analyzing fix commits to create postmortems, checking code changes against known issues before release, or updating postmortem knowledge base after release. Triggers on /postmortem command with onboard, check, or update arguments. --- name: postmortem description: Use when analyzing fix commits to create postmortems, checking code changes against known issues before release, or updating postmortem knowledge base after release. Triggers on /postmortem command with onboard, check, or update arguments. argument-hint: "[onboard | check [base] | update [range]]" metadata: author: jerikchan version: "1.0.0" --- Postmortem 驱动开发 Overview 通过 postmortem

OpenClawself-declared

Public facts

4

Change events

1

Artifacts

0

Freshness

Apr 15, 2026

Verifiededitorial-contentNo verified compatibility signals

Capability contract not published. No trust telemetry is available yet. Last updated 4/15/2026.

Trust evidence available

Trust score

Unknown

Compatibility

OpenClaw

Freshness

Apr 15, 2026

Vendor

Jerikchan

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. Last updated 4/15/2026.

Setup snapshot

git clone https://github.com/jerikchan/postmortem.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

Jerikchan

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

Protocol compatibility

OpenClaw

contractmedium
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

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

/postmortem onboard          # 初始化:分析历史 fix commits,创建知识库
/postmortem check [base]     # 检查:对比 base 分支,检测风险
/postmortem update [range]   # 更新:分析指定范围的 fix commits,更新知识库

markdown

---
id: PM-001
title: 简短描述问题
severity: critical | high | medium | low
created: 2024-01-15
updated: 2024-01-20
related_commits: [abc1234, def5678]
tags: [authentication, race-condition, async]
---

# PM-001: 简短描述问题

## 问题概述
一句话描述发生了什么问题。

## 影响范围
- 受影响的功能/模块
- 影响的用户范围

## 根本原因
详细分析为什么会发生这个问题。

## 触发条件
**关键!** 描述什么样的代码变更会触发类似问题:
- 特定的代码模式
- 特定的文件或模块
- 特定的操作序列

## 修复方案
实际采用的修复方法,包括代码示例。

## 预防措施
- [ ] 代码审查检查点
- [ ] 测试用例补充

## 经验教训
从这次事件中学到的可推广的经验。

bash

mkdir -p postmortem

bash

# 通过 commit message 关键词识别
   git log --oneline --all | grep -iE "(fix|bugfix|hotfix|patch|resolve|修复|修正|解决)"

   # Conventional Commits 格式
   git log --oneline --all | grep -E "^[a-f0-9]+ fix(\(.+\))?:"

text

./postmortem/
├── INDEX.md
├── PM-001-auth-race-condition.md
├── PM-002-null-pointer-in-parser.md
└── PM-003-timezone-calculation.md

bash

# 对比 base 分支
   git diff --name-only $(git merge-base HEAD origin/main) HEAD

   # 查看具体变更
   git diff $(git merge-base HEAD origin/main) HEAD

Docs & README

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

Self-declaredGITHUB OPENCLEW

Docs source

GITHUB OPENCLEW

Editorial quality

ready

Use when analyzing fix commits to create postmortems, checking code changes against known issues before release, or updating postmortem knowledge base after release. Triggers on /postmortem command with onboard, check, or update arguments. --- name: postmortem description: Use when analyzing fix commits to create postmortems, checking code changes against known issues before release, or updating postmortem knowledge base after release. Triggers on /postmortem command with onboard, check, or update arguments. argument-hint: "[onboard | check [base] | update [range]]" metadata: author: jerikchan version: "1.0.0" --- Postmortem 驱动开发 Overview 通过 postmortem

Full README

name: postmortem description: Use when analyzing fix commits to create postmortems, checking code changes against known issues before release, or updating postmortem knowledge base after release. Triggers on /postmortem command with onboard, check, or update arguments. argument-hint: "[onboard | check [base] | update [range]]" metadata: author: jerikchan version: "1.0.0"

Postmortem 驱动开发

Overview

通过 postmortem(尸检报告)将 bug fix 的教训转化为可查询的知识库,在 Release 前检测可能触发已知问题的代码,形成持续学习的闭环。

核心原则: 每个 bug fix 都是一次学习机会,必须被记录、索引、并用于预防未来的回归。

命令用法

/postmortem onboard          # 初始化:分析历史 fix commits,创建知识库
/postmortem check [base]     # 检查:对比 base 分支,检测风险
/postmortem update [range]   # 更新:分析指定范围的 fix commits,更新知识库

When to Use

| 场景 | 命令 | |------|------| | 新项目接入,需要初始化 postmortem 知识库 | /postmortem onboard | | Release 前,检查代码变更是否触发已知问题 | /postmortem check main | | Release 后,将新的 fix commits 沉淀为 postmortem | /postmortem update v1.0.0..v1.1.0 |

Postmortem 文档结构

每个 postmortem 存放在 ./postmortem/ 目录,使用 Markdown 格式:

---
id: PM-001
title: 简短描述问题
severity: critical | high | medium | low
created: 2024-01-15
updated: 2024-01-20
related_commits: [abc1234, def5678]
tags: [authentication, race-condition, async]
---

# PM-001: 简短描述问题

## 问题概述
一句话描述发生了什么问题。

## 影响范围
- 受影响的功能/模块
- 影响的用户范围

## 根本原因
详细分析为什么会发生这个问题。

## 触发条件
**关键!** 描述什么样的代码变更会触发类似问题:
- 特定的代码模式
- 特定的文件或模块
- 特定的操作序列

## 修复方案
实际采用的修复方法,包括代码示例。

## 预防措施
- [ ] 代码审查检查点
- [ ] 测试用例补充

## 经验教训
从这次事件中学到的可推广的经验。

模式 1: Onboard(初始化)

命令: /postmortem onboard

执行步骤

  1. 创建目录结构

    mkdir -p postmortem
    
  2. 扫描 fix commits

    # 通过 commit message 关键词识别
    git log --oneline --all | grep -iE "(fix|bugfix|hotfix|patch|resolve|修复|修正|解决)"
    
    # Conventional Commits 格式
    git log --oneline --all | grep -E "^[a-f0-9]+ fix(\(.+\))?:"
    
  3. 分析每个 fix commit

    • git show --stat <commit> - 查看变更的文件
    • git show <commit> - 查看具体变更内容
    • 从代码变更反推问题的根本原因
  4. 将相似问题分组,避免重复创建 postmortem

  5. 生成 postmortem 文档,使用上述文档结构

  6. 创建 INDEX.md 索引文件

输出示例

./postmortem/
├── INDEX.md
├── PM-001-auth-race-condition.md
├── PM-002-null-pointer-in-parser.md
└── PM-003-timezone-calculation.md

模式 2: Check(Release 前检查)

命令: /postmortem check [base_branch]

执行步骤

  1. 加载所有 postmortem 文档

    • 读取 ./postmortem/*.md(排除 INDEX.md)
  2. 提取每个 postmortem 的触发条件

    • 文件路径模式
    • 代码模式
    • 操作序列
  3. 获取代码变更

    # 对比 base 分支
    git diff --name-only $(git merge-base HEAD origin/main) HEAD
    
    # 查看具体变更
    git diff $(git merge-base HEAD origin/main) HEAD
    
  4. 匹配触发条件

    • 文件路径匹配
    • 代码模式匹配
    • 语义分析
  5. 生成检查报告

输出格式

# Postmortem Check Report

## 检查范围
- 基准分支: main
- 文件变更数: 15
- 检查的 postmortems: 5

## ⚠️ 风险警告

### PM-001: Auth Race Condition
**匹配原因:** `src/auth/session.ts` 被修改,且包含异步操作
**建议操作:**
- [ ] 确认新代码中的异步操作有正确的锁机制
- [ ] 运行相关测试用例

## ✅ 检查通过
- PM-002, PM-003, PM-004, PM-005: 无匹配的代码变更

模式 3: Update(Release 后更新)

命令: /postmortem update [commit_range]

执行步骤

  1. 扫描指定范围的 fix commits

    # 指定 tag 范围
    git log v1.0.0..v1.1.0 --oneline | grep -iE "(fix|bugfix|hotfix|修复)"
    
    # 最近 N 个提交
    git log -20 --oneline | grep -iE "(fix|bugfix|hotfix|修复)"
    
  2. 加载现有 postmortems

  3. 分析每个 fix commit

    • 判断是否属于已有 postmortem(相似问题)
    • 决定更新现有文档还是创建新文档
  4. 更新策略

    • 相似问题 → 合并到现有 postmortem,增加 related_commits
    • 新问题 → 创建新的 postmortem 文档
    • 问题再次出现 → 更新 postmortem,标记为需要关注
  5. 更新 INDEX.md


Quick Reference

| 命令 | 用途 | 示例 | |------|------|------| | /postmortem onboard | 初始化知识库 | 新项目接入时 | | /postmortem check | 风险检查 | /postmortem check main | | /postmortem update | 更新知识库 | /postmortem update v1.0..v1.1 |

Common Mistakes

| 错误 | 正确做法 | |------|----------| | 触发条件写得太模糊 | 具体到文件路径、代码模式、操作序列 | | 只记录"怎么修的" | 重点记录"为什么会出问题"和"如何预防" | | 每个 commit 都建 postmortem | 相似问题应该合并,保持知识库精简 | | 忽略低 severity 的问题 | 小问题积累会成大问题,全部记录 |

典型工作流

项目初始化
    └─→ /postmortem onboard
           └─→ 生成初始知识库

日常开发
    └─→ 准备 Release
           └─→ /postmortem check main
                  └─→ 检查风险,修复问题
                         └─→ Release
                                └─→ /postmortem update
                                       └─→ 沉淀新的教训

Contract & API

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

MissingGITHUB OPENCLEW

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/jerikchan-postmortem/snapshot"
curl -s "https://xpersona.co/api/v1/agents/jerikchan-postmortem/contract"
curl -s "https://xpersona.co/api/v1/agents/jerikchan-postmortem/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
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/jerikchan-postmortem/snapshot",
    "contractUrl": "https://xpersona.co/api/v1/agents/jerikchan-postmortem/contract",
    "trustUrl": "https://xpersona.co/api/v1/agents/jerikchan-postmortem/trust"
  },
  "curlExamples": [
    "curl -s \"https://xpersona.co/api/v1/agents/jerikchan-postmortem/snapshot\"",
    "curl -s \"https://xpersona.co/api/v1/agents/jerikchan-postmortem/contract\"",
    "curl -s \"https://xpersona.co/api/v1/agents/jerikchan-postmortem/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-17T01:40:36.463Z"
    }
  },
  "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": "Jerikchan",
    "href": "https://github.com/jerikchan/postmortem",
    "sourceUrl": "https://github.com/jerikchan/postmortem",
    "sourceType": "profile",
    "confidence": "medium",
    "observedAt": "2026-04-15T03:13:27.707Z",
    "isPublic": true
  },
  {
    "factKey": "protocols",
    "category": "compatibility",
    "label": "Protocol compatibility",
    "value": "OpenClaw",
    "href": "https://xpersona.co/api/v1/agents/jerikchan-postmortem/contract",
    "sourceUrl": "https://xpersona.co/api/v1/agents/jerikchan-postmortem/contract",
    "sourceType": "contract",
    "confidence": "medium",
    "observedAt": "2026-04-15T03:13:27.707Z",
    "isPublic": true
  },
  {
    "factKey": "handshake_status",
    "category": "security",
    "label": "Handshake status",
    "value": "UNKNOWN",
    "href": "https://xpersona.co/api/v1/agents/jerikchan-postmortem/trust",
    "sourceUrl": "https://xpersona.co/api/v1/agents/jerikchan-postmortem/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 postmortem and adjacent AI workflows.