Classify PRs into four documentation categories and generate prioritized gap summaries.
npx skills add https://github.com/grafana/tempo --skill docs-pr-check
Please help me install this Agent Skill. Skill: docs-pr-check Source: https://github.com/grafana/tempo/tree/main/.claude/skills/docs-pr-check Command: npx skills add https://github.com/grafana/tempo --skill docs-pr-check
This skill helps engineering and documentation teams assess whether PR changes include user-facing docs, and identifies gaps between proposed changes and existing Tempo documentation.
Run /docs-pr-check on a curated PR list to classify documentation status and surface gaps.
High-intent search queries and answers about installing and using this skill.
To identify Tempo documentation gaps in pull requests, you classify each PR into one of four categories: Docs present, Docs needed, Docs update needed, or No docs required, while cross-referencing existing docs/sources/tempo pages.
Auditing PR docs for Tempo release notes involves scanning a curated PR list to classify documentation status, validating coverage against existing docs, and generating a prioritized gap summary to highlight missing or required updates.
You classify Tempo PRs by comparing proposed code changes against existing documentation pages under docs/sources/tempo, assigning each PR a status of Docs present, Docs needed, Docs update needed, or No docs required.
Yes, after identifying documentation gaps in Tempo PRs, you generate an output format suitable for the docs-pr-write handoff, providing a prioritized summary of required updates for the technical writing team.
You need to run a gap analysis on Tempo pull requests when preparing for a release, ensuring all user-facing changes have corresponding documentation updates mapped correctly within the docs/sources/tempo directory structure.
No, the docs-pr-check workflow operates without external dependencies, directly analyzing your curated PR list and referencing the existing docs/sources/tempo repository to classify documentation needs.
wmb81321Answer Tempo protocol questions by fetching official documentation and MCP tools.
grafanaCreate and update Tempo documentation pages for user-facing PR changes.
sei-newbearGenerate release summaries from GitHub release notes for team communication.
IAmKongHaiRefresh and maintain documentation in 'docs/solutions/' against the current codebase.
