docs-update

Audit OnSpeed docs against firmware code to identify drift.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/flyonspeed/OnSpeed-Gen3 --skill docs-update-flyonspeed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-update
Source: https://github.com/flyonspeed/OnSpeed-Gen3/tree/main/.claude/skills/docs-update
Command: npx skills add https://github.com/flyonspeed/OnSpeed-Gen3 --skill docs-update-flyonspeed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits the OnSpeed docs site against the current firmware to identify and fix drift, ensuring that defaults, console commands, log columns, tone mapping, and wizard UI remain accurate before each release.

Core Features & Use Cases

  • Verifies that documentation reflects actual firmware behavior and data points (defaults, commands, log columns, tone thresholds, wizard fields).
  • Detects drift across multiple pages and recommends minimal, targeted fixes to restore alignment.
  • Performs pre-release checks to prevent drift from reaching production documentation.

Quick Start

Run the docs-update skill before every release to audit and fix drift.

Frequently Asked Questions about docs-update

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

FAQPage Schema
How do I detect documentation drift before a firmware release?

To detect documentation drift before a firmware release, audit your docs site against firmware code to identify misalignments in defaults, commands, log columns, and wizard UI. This process traces factual claims directly to code sources to ensure accuracy.

What is documentation drift in firmware projects?

Documentation drift in firmware projects occurs when published docs no longer match actual firmware behavior, such as outdated console commands, default values, or tone thresholds. Auditing code sources like LoadDefaults and ConsoleSerial identifies these misalignments.

How do I fix MkDocs site misalignments with firmware code?

To fix MkDocs site misalignments with firmware code, trace every factual claim to its code source and propose precise, minimal fixes that restore alignment while preserving the site's voice. This targets drift across multiple pages efficiently.

When do I need to run a docs audit against firmware code?

You need to run a docs audit against firmware code during pre-release checks. This ensures that defaults, console commands, log columns, tone thresholds, and wizard UI fields accurately reflect the firmware before reaching production documentation.

What firmware code sources should I check to verify documentation accuracy?

To verify documentation accuracy, check firmware code sources such as LoadDefaults for values, ConsoleSerial for commands, LogSensor for columns, ToneCalc for thresholds, and wizard field definitions. Tracing claims to these sources ensures factual alignment.