Improve upstream-release-docs skill with verification lessons#686
Merged
Improve upstream-release-docs skill with verification lessons#686
Conversation
Add three improvements based on lessons learned during the Registry Server v1.0.0/v1.0.1 docs update: - Check related repositories (operators, CLIs) for coordinated changes - Deep-verify behavioral claims (API routes, required fields, defaults, precedence rules, delete behavior, query param wiring, auth direction) - Spawn parallel verification agents for large doc sets Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the .claude/skills/upstream-release-docs skill to reduce documentation accuracy bugs by expanding the verification workflow used when documenting upstream releases.
Changes:
- Add an explicit “check related repositories” step to catch coordinated multi-repo changes (e.g., operator/CRD vs server).
- Add a behavioral verification checklist to validate runtime behavior (routes, validation, defaults, precedence, deletes, query params, auth containment direction), not just structs/types.
- Extend final validation guidance to optionally use parallel verification agents for large doc sets.
5 tasks
danbarr
approved these changes
Apr 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Improves the
upstream-release-docsskill based on lessons learned during the Registry Server v1.0.0/v1.0.1 documentation update (#683).Changes
Motivation
During the Registry Server docs update, we found 9 accuracy bugs that survived multiple editorial review rounds but were caught by source code verification agents:
descriptionlisted as requiredstatusfilter documented but non-functionalif/elsechain was branch > tag in actual codeformatincorrectly marked required/openapi.jsonmissing from public pathsAll of these would have been caught earlier with the behavioral verification checklist now added to the skill.
Test plan
🤖 Generated with Claude Code