upstream-release-docs

Analyze upstream releases and update documentation with source-verified change tracking.

4|3|Updated Jun 5, 2025
One-click install
npx skills add https://github.com/stacklok/docs-website --skill upstream-release-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upstream-release-docs
Source: https://github.com/stacklok/docs-website/tree/main/.claude/skills/upstream-release-docs
Command: npx skills add https://github.com/stacklok/docs-website --skill upstream-release-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps documentation teams keep product documentation accurate during upstream releases by replacing assumptions from release notes with verified source-code analysis and structured documentation updates.

Core Features & Use Cases

  • Release Analysis Workflow: Discovers release changes, categorizes impact areas, and traces upstream PRs, issues, and source code to understand what changed.
  • Documentation Verification: Audits existing docs, identifies stale claims, verifies behavior against release tags, and guides accurate updates.
  • Use Case: When an upstream project publishes a new version, use this Skill to analyze the release, determine documentation impact, and prepare source-backed documentation changes for review.

Quick Start

Use the upstream-release-docs skill with the target repository and release tag to analyze changes and update documentation guidance.

Frequently Asked Questions about upstream-release-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update documentation based on upstream GitHub releases?

To update documentation from upstream GitHub releases, analyze the target repository and release tag to discover changes, trace source code, and prepare verified documentation updates for review.

What is source verification for release documentation?

Source verification for release documentation audits existing docs against actual release tags and source code, replacing assumptions from release notes with verified behavioral analysis to identify stale claims.

Can I trace upstream pull requests to determine documentation impact?

Yes, you can trace upstream pull requests and issues to categorize impact areas, understand what changed in the code, and guide accurate documentation updates based on source-verified analysis.

Does documentation maintenance work with GitHub release tags and source code audits?

Documentation maintenance supports GitHub release tags and source code audits by discovering release changes, verifying behavior against specific tags, and generating structured documentation updates for review workflows.

Why should I verify release notes against source code for documentation updates?

Verifying release notes against source code prevents inaccurate documentation by replacing assumptions with source-backed analysis, ensuring that documentation accurately reflects verified behavior changes from the release.

What is the best way to handle stale claims in product documentation during a new release?

The best way to handle stale claims is auditing existing documentation against the new release tag, identifying outdated statements, and preparing source-verified documentation changes for structured review handling.