Skip to content

About

A Claude Code skill for analysing log files and console output from OCUDU — an open-source 5G CU/DU implementation.

Resources

Stars

3 stars

Watchers

0 watching

Forks

Latest commit

 

History

59 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

ocudu-tools

Claude Code skills for working with OCUDU — an open-source 5G CU/DU implementation. Covers instrumentation, observability, and diagnostics across the OCUDU stack.

Skills

analyze-ocudu-log

Analyses log files and console output from any OCUDU application. Activates automatically when you share a log file or unit test output containing OCUDU log lines.

It analyses the log in layers, starting with the cheap aggregate metrics and drilling into specific protocol layers only when anomalies are found.

Covered layers:

  • METRICS — scheduler, MAC, PHY and executor KPI windows
  • SCHED — slot decisions, PRACH/RACH events, HARQ chains
  • MAC — cell lifecycle, pipeline timing
  • PHY — LDPC processing latencies
  • RRC, F1AP, NGAP, E1AP — control and user-plane signalling (stubs, populated over time)

Supported log sources:

  • Log files from any OCUDU application: gnb, du, cu, cu_cp, cu_up
  • Console output from unit tests or runtime
  • Pasted log snippets

fix-gitlab-issue

Autonomously investigates and fixes a GitLab issue in an isolated git worktree. Trigger: share a GitLab issue URL and ask to fix or investigate it.

The skill reads the issue and all comments, assesses whether a local fix is feasible, creates a worktree on a new branch, locates the relevant code, attempts to reproduce the bug, implements a fix, and validates it with targeted ninja/ctest. It then writes a report and—on your approval—commits, pushes, and opens an MR.

Requires GITLAB_AI_TOKEN (api-scoped personal access token) in your environment.

fix-gitlab-mr

Investigates and fixes failing CI jobs on a GitLab MR. Trigger: share an MR URL and ask to fix or diagnose a failing pipeline.

The skill checks the latest pipeline status, lists failed jobs, lets you pick one, downloads and analyses the job log, then for fixable failures (compilation, linker, test, clang-tidy, clang-format) creates a worktree on the MR's source branch, applies a fix, validates it with targeted ninja/ctest, and proposes a commit back to the same branch. Infrastructure failures (timeouts, missing credentials, hardware) are reported but not acted on.

Requires GITLAB_AI_TOKEN (api-scoped personal access token) in your environment.

synthesize-skill-update

Cleans up a personal branch before it is merged into main. Run it when reviewing a PR. It reads the diff, extracts generalisable knowledge, discards personal notes and overly specific hacks, edits the skill files in place, and produces a changelog entry with a list of what was kept and what was dropped.

Installation

Option A — Marketplace (read-only)

Add the marketplace, then install the plugin:

/plugin marketplace add frankist/ocudu-tools
/plugin install ocudu-tools

Or browse via /plugin > Discover.

Option B — Clone and symlink (recommended if you want to edit skills)

Clone the repo and symlink each individual skill into Claude Code's skills directory so your changes are picked up immediately and you can source-control them:

git clone https://github.com/frankist/ocudu-tools
ln -s ./ocudu-tools/<your_skill_of_choice> <path_to_project_or_home>/.claude/skills

With this setup you can branch, edit layer reference files or skill instructions, and commit your findings — then open a PR to share them back.

Configuration

GitLab token

fix-gitlab-issue and fix-gitlab-mr require a GitLab personal access token with api scope. Set it in one of two ways:

Shell environment — add to your .bashrc / .zshrc:

export GITLAB_AI_TOKEN=glpat-xxxxxxxxxxxxxxxxxxxx

Claude Code settings — add to ~/.claude/settings.json so it is always available inside Claude Code sessions:

{
  "env": {
    "GITLAB_AI_TOKEN": "glpat-xxxxxxxxxxxxxxxxxxxx"
  }
}

Usage

Skills trigger automatically from natural language. Examples:

analyze-ocudu-log

  • "Why is RACH failing?" (with a log file open)
  • "Analyze /tmp/gnb.log"
  • Pasting console output from a failed unit test that includes OCUDU log lines

fix-gitlab-issue

fix-gitlab-mr

Contributing

Branch model

Branch Purpose
main Stable, shared skills — the version installed by users
<name> Personal branch — local improvements, lessons learned, experimental notes

Proposing a skill update

  1. Branch off main: git checkout -b <your-name>
  2. Make your changes — add knowledge to layer files, refine instructions, fix gaps
  3. Run /ocudu-tools:synthesize-skill-update to clean up your branch before submitting
  4. Open a PR against main

Review process

PRs are reviewed with the synthesize-skill-update skill, which extracts the generalisable knowledge from your branch, discards personal or overly specific notes, and merges the result cleanly into main. You will receive a summary of what was kept and what was left out.

License

BSD 3-Clause — see LICENSE.

About

A Claude Code skill for analysing log files and console output from OCUDU — an open-source 5G CU/DU implementation.

Resources

Stars

3 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages