Menu
Update Go version across the Tempo codebase (go.mod, tools/go.mod, Dockerfile, CI workflows, tools image tag)
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | update-go-version |
| description | Update Go version across the Tempo codebase (go.mod, tools/go.mod, Dockerfile, CI workflows, tools image tag) |
| allowed-tools | WebFetch, Grep, Read, Write |
Updates the Go version across all relevant files in the Tempo codebase.
Invoke with /update-go-version
Extract Go version from tools/Dockerfile.
This file is updated by a Renovate workflow automatically.
Check these files:
go.mod (main module)tools/go.mod (tools module)
If the versions already match, advise user that tools/Dockerfile needs to be updated and merged first to build new image, then stop.Update the go X.Y.Z directive in both:
go.mod (main module)tools/go.mod (tools module)Fetch the latest tools image tag from Docker Hub:
curl -s "https://hub.docker.com/v2/repositories/grafana/tempo-ci-tools/tags?page_size=5&ordering=last_updated" | jq -r '.results[0].name'
Update TOOLS_IMAGE_TAG ?= main-XXXXXXX with the latest tag.
make vendor
make build
| File | What to change |
|---|---|
go.mod | go X.Y.Z directive |
tools/go.mod | go X.Y.Z directive |
build/tools.mk | TOOLS_IMAGE_TAG value |
Assess documentation status for PRs — classify gaps, identify existing docs that need updating, and flag UI changes that may affect screenshots. Use when the user asks to check docs coverage for PRs, triage documentation needs, audit PRs for missing docs, assess whether a set of changes needs documentation, or check what recently merged PRs need docs.
Write or update product documentation for user-facing PR changes. Use when the user asks to write docs for a PR, document a PR, update existing docs based on a code change, process PRs flagged by docs-pr-check, or provides PR numbers or links and wants the corresponding documentation created or updated — even if they say "document these changes" without mentioning PRs explicitly. This skill writes and updates docs only; it does not triage PRs (use docs-pr-check), review existing docs (use docs-review), or generate release notes.
Review documentation changes for style, accuracy, and completeness. Use when docs have been written or updated and need a quality check before submission, when the user asks to review docs, proofread, check style compliance, or verify technical accuracy of documentation.
End-to-end workflow for PR documentation — check, write, review, and optionally validate screenshots. Use when the user wants to document one or more PRs from start to finish, run the full docs pipeline, or asks for a complete documentation pass on PRs.
Use this skill to assess whether documentation content fits its intended audience. Identifies the target persona (Learner, Practitioner, Expert, Operator), use case, and entry state, then flags mismatches between the content and what that audience needs. Use when the user asks to check persona fit, review audience alignment, asks "who is this page for?", questions whether content is at the right level of detail, or mentions /persona-check. Also use when reviewing a PR where content seems too advanced, too basic, or aimed at the wrong reader. This is not for style guide, grammar, or link checking — use docs-review for those.
Create or fix Tempo changelog entries with .chloggen. Use when a PR needs a changelog, CHANGELOG.md was edited directly, or the user asks to add/update/amend release notes.