// Write or update Tempo docs for user-facing PR changes identified by docs-pr-check
Resolve vendor/ conflicts during a merge, rebase, or dependency upgrade on main or release branches
Assess documentation status for each PR in a Tempo release — classify gaps and identify existing docs that need updating
Review documentation changes for style, accuracy, and completeness. Use when docs have been written or updated and need a quality check before submission.
End-to-end workflow for PR documentation — check, write, review. Use at any stage of documenting PR changes.
Update Go version across the Tempo codebase (go.mod, tools/go.mod, Dockerfile, CI workflows, tools image tag)
| name | docs-pr-write |
| description | Write or update Tempo docs for user-facing PR changes identified by docs-pr-check |
| allowed-tools | Bash Read Grep Write |
For a prioritized PR list from docs-pr-check, create or update the required documentation pages.
This skill is for documentation execution only. Do not generate release notes.
Invoke with /docs-pr-write.
Provide:
Docs needed and Docs update needed rows from docs-pr-check)main, release-2.10, or 3.0-docs)If the PR list is missing, ask for the output table from docs-pr-check.
Expected handoff from docs-pr-check:
Docs neededDocs update neededconfiguration and API behaviorFor each PR:
gh pr view XXXX --repo grafana/tempo --json title,body,files,labels
Extract:
Prefer updating existing docs over creating new pages.
Use this order:
When uncertain between two pages, choose the one closest to user workflow and cross-link the other.
For each required change:
Keep content concise and avoid duplicating large reference material.
Do not rely only on PR description text.
Use the PR's changed file list as your guide to where to look. Only search within the grafana/tempo repository — do not search across other Grafana repositories.
For each claim you document, verify in the file type most likely to be authoritative:
RegisterFlagsAndApplyDefaults), accepted enum valuesCorrect docs if code and PR text differ.
Add links where users need them:
Use consistent, clear link text (for example documentation when requested).
Before returning:
After completing all doc changes, output a "Before you submit" block. Select only the checklist sections from .agents/doc-agents/shared/verification-checklist.md that are relevant to what you just documented:
Present the selected items as a short checklist for the user to complete before submitting the PR. Do not attempt to complete these items yourself.
Return:
.claude/skills/docs-pr-check/SKILL.md.agents/doc-agents/shared/docs-context-guide.md — code-to-docs mapping, key file paths, and Tempo doc conventions.agents/doc-agents/shared/release-notes-workflow.md.agents/doc-agents/shared/verification-checklist.md