skills.rest
oceanbase
oceanbaseOFFICIAL
Explore all skills by this author →
Website𝕏@OceanBaseDBGitHub

oceanbase-source-analysis

Extract evidence from OceanBase community source code to validate error codes and runtime behavior.

161|40|Updated Nov 22, 2022
Search Tags:#git#analysis#debug#static-analysis#version-control#source-code#oceanbase
One-click install
npx skills add https://github.com/oceanbase/obdiag --skill oceanbase-source-analysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oceanbase-source-analysis
Source: https://github.com/oceanbase/obdiag/tree/main/plugins/agent/skills/oceanbase-source-analysis
Command: npx skills add https://github.com/oceanbase/obdiag --skill oceanbase-source-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This SOP helps engineers validate OceanBase behavior by reading local OceanBase community edition source code when logs or RCA analyses do not yield a definitive conclusion. It covers error code traceability, function/parameter behavior verification, call-chain tracing, and cross-version behavior comparisons.

Core Features & Use Cases

  • Source-path validation and version control checks to ensure analysis against the correct codebase.
  • Module-focused code search and targeted file retrieval to locate implementation details (e.g., error definitions, transaction management, storage, SQL engine).
  • Use Case: When RCA or logs are inconclusive, verify the exact source implementation and compare behavior across versions to isolate root causes.

Quick Start

Provide the local OceanBase source path and the target version to begin analysis.

Frequently Asked Questions about oceanbase-source-analysis

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

FAQPage Schema
How do I trace OceanBase error codes in source code when logs are inconclusive?▼

Pinpoint and extract evidence from OceanBase community source code to validate error codes and parameter handling. This source-level verification isolates exact root causes when RCA or runtime logs fail to yield definitive conclusions.

How do I compare OceanBase runtime behavior across different versions?▼

Apply version control checks against the local OceanBase repository to extract and compare source-level evidence across versions. This cross-version comparison isolates behavioral differences in modules like storage and SQL engine.

Do I need a local OceanBase repository to verify function call chains and parameter behavior?▼

Yes, you need a local OceanBase source path and target version to verify function call chains. The analysis enforces repository location and module-specific searches under directories like src/storage and src/sql to retrieve implementation details.

What is the best way to locate OceanBase transaction management implementation details?▼

Perform module-focused code searches within the local source repository to locate transaction management details. This targeted file retrieval validates function behavior and error definitions without relying solely on runtime logs.

Why does source-level validation fail to find specific OceanBase storage module behaviors?▼

Source-level validation fails if repository location or version control checks do not match the target OceanBase codebase. Ensure the local source path points to the correct community edition version before executing module-specific searches.

Related Skills

Explore More Software Engineering Skills→
Kgan01Kgan01
6

reload-ghengis

Force-sync the ghengis-skills plugin from GitHub and update local cache.

Community
Advanced
incidentfoxincidentfox
654

observability

Correlate logs, metrics, and traces across multiple backends to identify root causes.

Official
Intermediate
nicograefnicograef
2

understand

Trace call chains and data flows to construct codebase mental models.

Community
Advanced
OiAnthonyOiAnthony
8

hunt

Diagnose root causes of errors, crashes, and regressions using repro steps and source traces.

Community
Advanced