Skip to content

docs: list openmetadata-pr-review in CLAUDE.md skill pointer index - #32769

Open
detail-app[bot] wants to merge 1 commit into
mainfrom
detail/fix-docs/docs-list-openmetadata-pr-review-in-claude-md-skil-04450f
Open

docs: list openmetadata-pr-review in CLAUDE.md skill pointer index#32769
detail-app[bot] wants to merge 1 commit into
mainfrom
detail/fix-docs/docs-list-openmetadata-pr-review-in-claude-md-skil-04450f

Conversation

@detail-app

@detail-app detail-app Bot commented Sep 6, 2026

Copy link
Copy Markdown

Describe your changes:

Added a row for the new openmetadata-pr-review skill to the always-loaded
skill pointer index in CLAUDE.md. The index lists every skill as the
authoritative map agents consult at session start, but it was missing the
openmetadata-pr-review skill added by 9a73f6c.
Without this row, an agent asked to review a real GitHub PR would follow the
existing code-review row ("reviewing a diff/PR") and run /code-review,
which is scoped to local not-yet-a-PR changes — missing the new skill's
live-diff pinning, meaningful-test rubric, CI inspection, and merge verdict.

Type of change:

  • Documentation

High-level design:

N/A — one-line addition to a doc table.

Tests:

N/A — documentation only.

UI screen recording / screenshots:

Not applicable.

Checklist:

  • I have read the CONTRIBUTING document.
  • My PR is linked to a GitHub issue via Fixes #<issue-number> above. (N/A — doc drift fix)

Introduced by commit 9a73f6c (@pmbrull, #32308)


Doc Drift PRs can be configured here.

@detail-app
detail-app Bot requested a review from pmbrull September 6, 2026 23:52
@github-actions

github-actions Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

@github-actions

github-actions Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

🔴 Playwright Results — workflow failed

Validated commit 236f760c0990ece718fd3ba4195da6cc84cd94ef in Playwright run 34068060092, attempt 2.

✅ 0 passed · ❌ 0 failed · 🟡 0 flaky · ⏭️ 0 skipped · 🧰 0 lifecycle flaky

⚙️ No test failures. This run failed in CI infrastructure or reporting (see Pipeline and setup failures), not because of your changes — no test action needed from you.

Pipeline and setup failures (6)

  • The build job finished with status failure.
  • Duration-aware shard planning finished with status skipped.
  • Fixture cache restoration finished with status skipped.
  • Seeded fixture preparation finished with status skipped.
  • The Playwright shard matrix was unexpectedly skipped.
  • No expected Playwright shards were declared.

Performance

⚪ Performance metrics unavailable; see the CI and reporting failures above.

Shard Passed Failed Flaky Skipped Lifecycle failed Lifecycle flaky

📦 Download artifacts

How to debug locally
# Download playwright-test-results-<shard> artifact and unzip
npx playwright show-trace path/to/trace.zip    # view trace

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.

1 participant