observability-publish

Aggregate omni-execution-log.json into omni-observability-result.json by latest execution per step.

52|3|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/ZTE-AICloud/Co-OmniSpec --skill observability-publish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability-publish
Source: https://github.com/ZTE-AICloud/Co-OmniSpec/tree/main/skills/observability-publish
Command: npx skills add https://github.com/ZTE-AICloud/Co-OmniSpec --skill observability-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pymysql, and includes scripts (resource) components.

What problem does it solve?

该技能用于将 omni-execution-log.json 的步骤数据聚合为 omni-observability-result.json(按 sdd_step/step_name 取最近一次执行),并调用 ssd_step_insert 将结果写入 ssd_step_info。

Core Features & Use Cases

  • 聚合 omni-execution-log.json 获取最新执行并输出 omni-observability-result.json。
  • 调用 ssd_step_insert 将结果写入数据库,必要时支持 dry-run 以仅校验。
  • 提供多种触发方式与参数(如 --default-branch)。

Quick Start

在一个特性目录中执行 observability-publish,或对 omni-execution-log.json 直接运行,以生成 omni-observability-result.json 并将数据写入 ssd_step_info。

Frequently Asked Questions about observability-publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert execution logs into observability data for database insertion?

You can generate observability data by running observability-publish in a feature directory containing omni-execution-log.json. It aggregates the latest execution per step and writes the results to ssd_step_info, with optional branch handling via --default-branch.

Can I validate observability data generation without writing to the database?

You can validate observability data without database insertion by using the --dry-run flag. This processes the omni-execution-log.json file and validates the output without actually writing records into the ssd_step_info database table.

What is the process for extracting the latest step execution from JSON logs?

The process parses omni-execution-log.json and groups records by sdd_step or step_name. It selects the most recent execution per step, producing a filtered omni-observability-result.json file for analysis and database insertion.

Does observability data ingestion require a specific Python database driver?

Observability data ingestion requires the pymysql Python dependency to handle database connectivity. This driver enables the ssd_step_insert process to write the aggregated observability results into the ssd_step_info table with proper branch handling.

How do I handle branch information when publishing observability data to the database?

You can handle branch information during observability data publication by using the --default-branch parameter. This ensures the aggregated execution records are correctly contextualized with the appropriate branch when inserted into the ssd_step_info database table.