update-docs

Update Astro Starlight MDX docs and sidebar from changed source files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Grupo-AFAL/claude-plugins --skill update-docs-grupo-afal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-docs
Source: https://github.com/Grupo-AFAL/claude-plugins/tree/main/docs-tools/skills/update-docs
Command: npx skills add https://github.com/Grupo-AFAL/claude-plugins --skill update-docs-grupo-afal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps the Astro Starlight documentation site accurate and up to date by ensuring documentation content matches recent code changes, preventing stale or misleading docs for end users and developers.

Core Features & Use Cases

  • Map code changes to documentation: Inspect changed controllers, models, routes, services, and assets and determine which MDX pages need updates.
  • Source-driven updates: Read the actual source files and copy code examples and parameter tables directly from the codebase so docs reflect the truth.
  • Project-aware MDX editing: Create or modify MDX pages in Spanish, update the docs sidebar (docs/astro.config.mjs), and embed screenshots when available.
  • Verification: Run the docs build and require a zero-error build before finishing to prevent broken site deploys.
  • Use case: After a feature branch adds a new controller and model, generate an end-user task guide in Spanish, add a technical reference entry collapsed in the sidebar, and rebuild the docs to confirm changes.

Quick Start

Run the update-docs skill with a description or list of changed files so it updates the relevant MDX pages in docs/src/content/docs/, adjusts the sidebar, and rebuilds the site.

Frequently Asked Questions about update-docs

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

FAQPage Schema
How do I keep Astro Starlight documentation synchronized with code changes?

Mapping code changes to documentation involves inspecting modified controllers, models, routes, services, and assets to determine which MDX pages need updates. It reads actual source files to copy code examples and parameter tables directly into the docs.

What's the best way to update MDX pages in Spanish after a Rails code change?

Astro Starlight documentation updates support Rails projects by mapping changed controllers, models, routes, services, and assets to specific MDX pages. It writes Spanish content, updates sidebar entries in astro.config.mjs, and verifies a zero-error build.

How do I automatically update the Astro Starlight sidebar when adding new docs?

After updating MDX content and sidebar entries, run the Astro Starlight docs build to verify zero errors. This verification step prevents broken site deploys by requiring a successful build before the documentation update process finishes.

Does the Astro Starlight docs update process work with Rails projects?

To update Spanish MDX pages after a Rails code change, read the modified source files, write or revise MDX content in docs/src/content/docs/, update the sidebar in astro.config.mjs, and run the docs build to verify zero errors.

Why does my Astro Starlight docs build fail after updating MDX content?

To update the Astro Starlight sidebar when adding new docs, modify the docs/astro.config.mjs file to include new entries or collapse technical references alongside the newly created or revised MDX pages in docs/src/content/docs/.