Stats
Actions
Tags
From opentelemetry-docs-skills
Review OpenTelemetry documentation PRs for CI compliance, contribution conventions, refcache impact, and content quality. Use when reviewing PRs in opentelemetry.io or debugging CI failures.
How this skill is triggered — by the user, by Claude, or both
Slash command
/opentelemetry-docs-skills:otel-pr-reviewsonnetThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Review workflow for pull requests in the opentelemetry.io repository, encoding
Review workflow for pull requests in the opentelemetry.io repository, encoding CI checks, contribution conventions, and review procedures.
gh pr view <number> --json title,body,files,reviews,labels,headRepositoryOwner
gh pr diff <number>
gh pr checks <number>
The opentelemetry.io repo runs these CI checks:
| Check | What It Validates |
|---|---|
check-links | Link validity (3 shards: en, locales-A-to-M, locales-N-to-Z) |
check-spelling | cSpell compliance + page-local word lists |
check-text | textlint for terminology and style |
check-file | Expired files, filenames, formatting, branch names |
check-registry | Registry data schema (only for data/registry/** changes) |
Fork PR caveat: CI may fail on fork PRs due to otelbot token scope limitations. This is expected and not a blocker. Look at the specific failure to determine if it's a real issue or a permissions problem.
Classify changed files to apply the right review criteria:
content/en/blog/**): Apply blog review checklistcontent/en/docs/**): Apply docs review checklistdata/registry/**): Validate schema compliance.github/**, scripts/**): Review for correctnesspackage.json, config files): Check for side effectsFor documentation and blog content, check:
For blog-specific rules, refer to the otel-blog-review skill.
Signed-off-by: trailer)sig
labelWhen a PR adds new external links:
static/refcache.json by CIrefcache.json changes are included, verify status codes are 200npm run fix:refcache
These automation commands can be run in PR comments or locally:
PR comment commands (triggered by otelbot):
/fix:all - Run all automated fixes/fix:dict - Normalize spelling dictionaries/fix:format - Auto-format with PrettierLocal npm scripts:
npm run check:all # Run all checks
npm run check:links # Link validation
npm run check:spelling # Spell checking
npm run check:text # Textlint
npm run check:format # Format checking
npm run fix:all # Run all fixes
npm run fix:refcache # Prune refcache + check links
sig label present if blog references a SIGrefcache.json updated if new external links addedcSpell:ignore)Words not in the dictionary. Fix by adding to cSpell:ignore in the page
frontmatter:
cSpell:ignore: myword anotherword
Or add to the repo-level dictionary if the word is used across multiple pages.
Broken links. Common causes:
Textlint rule violations. Common issues:
File-level issues:
expiryDate in frontmatter)Structure your review as:
List each check with pass/fail/skip status and any relevant notes.
Issues that must be fixed before merge.
Recommendations for better quality.
What the author did well.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.
npx claudepluginhub vitorvasc/opentelemetry-docs-skills --plugin opentelemetry-docs-skills