release-docs

Sync README counts and plugin metadata after recategorizing plugin components.

12|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/jikig-ai/soleur --skill release-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-docs
Source: https://github.com/jikig-ai/soleur/tree/main/plugins/soleur/skills/release-docs
Command: npx skills add https://github.com/jikig-ai/soleur --skill release-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures documentation metadata, component counts, and plugin descriptions remain accurate after adding, removing, or recategorizing plugin components so the public docs and plugin manifest match the repository state.

Core Features & Use Cases

  • Automated README sync: Run the provided sync script to update component counts across repository README files and plugin README.
  • Plugin manifest update: Guides updating the plugins/soleur/.claude-plugin/plugin.json description to reflect correct counts.
  • Catalog mapping maintenance: Instructs where to update skill category mappings to prevent "Uncategorized" entries in the auto-generated catalog.
  • Build and verification: Describes running an Eleventy build and validating generated pages and JSON with grep and jq to confirm counts and well-formed output.
  • Release reporting: Provides a template summary of updated counts and files to include in the release notes or changelog.

Quick Start

Run the sync-readme-counts.sh script, update plugin.json counts if needed, run the Eleventy build, and verify counts and JSON with grep and jq.

Frequently Asked Questions about release-docs

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

FAQPage Schema
How do I sync documentation metadata after adding or removing plugin components?

To sync documentation metadata, run the sync-readme-counts.sh script to update component counts across README files, then update the plugin.json description to reflect the correct counts before publishing.

How do I verify an Eleventy build and validate generated JSON output?

Verify an Eleventy build by running npx @11ty/eleventy for site generation, then use grep and jq to validate generated HTML pages and JSON files for accurate counts and well-formed output.

Why are my plugin components showing as Uncategorized in the auto-generated catalog?

Components appear Uncategorized in the auto-generated catalog when skill category mappings are not updated after recategorizing plugin components, requiring manual adjustments to the catalog mapping files.

Do I need jq and grep to verify generated HTML and JSON during an Eleventy build?

Yes, you need jq and grep to verify generated HTML and JSON during an Eleventy build, as these tools validate well-formed output and confirm that component counts match the repository state.

What is the best way to maintain plugin manifest descriptions and README counts across a repository?

The best way to maintain plugin manifest descriptions and README counts is running an automated sync script to synchronize metadata, followed by an Eleventy build verification to ensure public docs match repository state.

Can I use release-docs to generate a release report summary for updated documentation files?

Yes, release-docs provides a release reporting template that summarizes updated component counts and modified files to include directly in release notes or changelogs after synchronizing metadata.