Create and update Tempo documentation pages for user-facing PR changes.
npx skills add https://github.com/grafana/tempo --skill docs-pr-write
Please help me install this Agent Skill. Skill: docs-pr-write Source: https://github.com/grafana/tempo/tree/main/.claude/skills/docs-pr-write Command: npx skills add https://github.com/grafana/tempo --skill docs-pr-write
Writes or updates Tempo documentation pages to reflect user-facing PR changes identified by docs-pr-check, ensuring reviewers and users have accurate guidance.
Run with the PR numbers to process and the target Tempo branch (for example main or 3.x-docs) to generate and commit the updated docs.
High-intent search queries and answers about installing and using this skill.
Tempo documentation updates are automated by detecting user-facing PR changes, selecting canonical docs pages, and writing concise content with runnable examples. The process links related topics and maintains page structure for release notes workflows.
Generating runnable examples for Tempo docs requires reconstructing the capability from the PR and verifying against the Tempo codebase. This ensures field names, versions, and links are accurate before committing the updated documentation pages.
Canonical Tempo docs pages are selected by reconstructing the specific capability introduced by the PR changes. The skill matches this capability to the most relevant existing documentation target to ensure accurate content placement.
Automating Tempo docs writing requires access to docs-pr-check handoff data and the target Tempo branch context, such as main or 3.x-docs. You provide the PR numbers and target branch to generate and commit the updated documentation.
Yes, after writing or updating Tempo documentation pages, the process automatically links the updates to related pages. This cross-linking maintains existing page structure and supports release notes workflows for accurate user guidance.
majunbaoGenerate a PR summary, branch suggestion, title, and draft description from git context.
AztecProtocolGenerate changelog drafts by analyzing git diffs between next and HEAD.
rfhaynAudit PRDs by comparing descriptions with current codebase entities and interfaces.
grafanaReview documentation changes for style, accuracy, and completeness.
