update-rwsdk-docs

Fetch RedwoodSDK docs from GitHub and rebuild the reference index.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/softee-p/redwoodSDK-toolkit --skill update-rwsdk-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-rwsdk-docs
Source: https://github.com/softee-p/redwoodSDK-toolkit/tree/main/plugins/rwsdk-toolkit/skills/update-rwsdk-docs
Command: npx skills add https://github.com/softee-p/redwoodSDK-toolkit --skill update-rwsdk-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

Keeps RedwoodSDK documentation accurate and current by fetching the latest official docs from the RedwoodSDK repository and rebuilding the rwsdk-docs skill reference index when docs become outdated or after major releases.

Core Features & Use Cases

  • Fetches the latest official documentation from the RedwoodSDK GitHub repository.
  • Rebuilds the rwsdk-docs skill reference index after updating docs.
  • Triggered when documentation seems wrong or out of date, or after major RedwoodSDK releases.
  • Supports periodic maintenance to ensure documentation stays aligned with the latest API changes.

Quick Start

Run the update-rwsdk-docs.sh script against your repo root to refresh the documentation.

Frequently Asked Questions about update-rwsdk-docs

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

FAQPage Schema
How do I update RedwoodSDK documentation references after a new release?

To update RedwoodSDK documentation references, run a Git-based fetch from the redwoodjs/sdk repository, clear the references folder, perform a shallow sparse checkout of docs, copy them into references, and rebuild the documentation index.

Why does my RedwoodSDK documentation seem wrong or out of date?

RedwoodSDK documentation appears stale when local reference indexes fall behind major releases; refreshing them requires fetching the latest official docs from the GitHub repository and repopulating the references folder.

Do I need git installed to refresh RedwoodSDK docs automatically?

Yes, git is a required dependency to refresh RedwoodSDK docs, as the workflow performs a Git-based fetch, sparse checkout, and clone operation directly from the redwoodjs/sdk repository.

What's the best way to automate RedwoodSDK documentation maintenance?

The best way to automate RedwoodSDK documentation maintenance is running the update-rwsdk-docs.sh script against your repo root, which handles the fetch, clone, and rebuild workflow to refresh the index.

How does the shallow sparse checkout work when fetching RedwoodSDK docs?

The shallow sparse checkout fetches only the docs directory from the redwoodjs/sdk repository, copying the updated files into your references folder to rebuild the rwsdk-docs skill reference index efficiently.

When should I not use an automated Git fetch to update documentation?

Avoid automated Git fetches for documentation updates if your repository lacks git installed or if your local references folder contains custom modifications that will be cleared during the repopulation workflow.