Skip to content

add O11y Engineer community module - #13

Open
henrikrexed wants to merge 1 commit into
bmad-code-org:mainfrom
henrikrexed:add/o11y-engineer-module
Open

add O11y Engineer community module#13
henrikrexed wants to merge 1 commit into
bmad-code-org:mainfrom
henrikrexed:add/o11y-engineer-module

Conversation

@henrikrexed

@henrikrexed henrikrexed commented Apr 30, 2026

Copy link
Copy Markdown

"## New Module Submission

Module: O11y Engineer (o11y)
Repository: https://github.com/henrikrexed/bmad-observability-agent
Version: 2.0.0
Category: infrastructure-and-platforms / observability
License: MIT

Description

OpenTelemetry observability expert module providing 6 skills:

Skill Purpose
o11y-engineer (Ollie) Obserability assessment, Opentelemetry collector design, SLO planning, Dynatrace automation
o11y-write-ottl Generate OTTL expressions for transform, filter, and
routing processors |

| o11y-generate-epics | Generate observability epics and stories for
BMAD sprint planning |
| o11y-instrument-app | Add OpenTelemetry instrumentation with
per-language guidance |
| o11y-redact-pii | Configure PII and sensitive data redaction for OTel
pipelines |
| o11y-setup | Module configuration and registration |

Checklist

  • Module built with BMad Builder
  • Validated with Validate Module (VM) — 0 structural findings
  • .claude-plugin/marketplace.json present
  • Tagged release (v2.0.0) with SHA
    12b56ecdfc0c8c496afe45efd0aa9628579055ac
  • Registry YAML follows community format
  • Category/subcategory from categories.yaml"2>&1
    Create PR against upstream marketplace repo

Add OpenTelemetry observability expert module (o11y) to the community
registry. Provides 6 skills: agent architect, OTTL writer, epic
generator, app instrumentation, PII redaction, and module setup.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Apr 30, 2026

Copy link
Copy Markdown

Walkthrough

A new community skill manifest for observability engineering is introduced, defining identification fields, scope description for OpenTelemetry work, repository configuration, licensing metadata, classification properties, and release governance including version 2.0.0 with unverified trust tier status.

Changes

Cohort / File(s) Summary
Community Skill Manifest
registry/community/o11y-engineer.yaml
Added new observability engineer skill definition with code o11y, version 2.0.0, covering OpenTelemetry collector configuration, instrumentation, semantic conventions, and Dynatrace automation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A new skill hops into the registry today,
Observability wisdom on its way,
O11y-engineer, collecting traces so bright,
Telemetry flowing through day and night! 📊✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title 'add O11y Engineer community module' directly and clearly describes the main change: addition of a new O11y Engineer community skill manifest to the registry.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@registry/community/o11y-engineer.yaml`:
- Line 28: The YAML has a placeholder reviewer value "pending" which violates
release-governance metadata; update the reviewer field in
registry/community/o11y-engineer.yaml by replacing reviewer: pending with the
actual GitHub handle of the approving reviewer (e.g., reviewer: <handle>) so the
reviewer key contains a valid GitHub identity rather than the placeholder.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a49df763-1c6b-4ca5-8b40-62664a9a403c

📥 Commits

Reviewing files that changed from the base of the PR and between b1cc5e3 and d1bd5ea.

📒 Files selected for processing (1)
  • registry/community/o11y-engineer.yaml

approved_sha: 12b56ecdfc0c8c496afe45efd0aa9628579055ac
trust_tier: unverified
approved_date: "2026-04-30"
reviewer: pending

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Replace placeholder reviewer with an actual GitHub handle.

reviewer: pending is not a valid reviewer identity and breaks release-governance metadata expectations for community modules. Please set this to the real GitHub handle of the approving reviewer (e.g., reviewer: <handle>).

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@registry/community/o11y-engineer.yaml` at line 28, The YAML has a placeholder
reviewer value "pending" which violates release-governance metadata; update the
reviewer field in registry/community/o11y-engineer.yaml by replacing reviewer:
pending with the actual GitHub handle of the approving reviewer (e.g., reviewer:
<handle>) so the reviewer key contains a valid GitHub identity rather than the
placeholder.

@bmadcode

bmadcode commented May 6, 2026

Copy link
Copy Markdown
Contributor

@henrikrexed thank you - team is reviewing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants