doc-maintenance

Guide version and dependency updates across documentation and build configs.

Updated Oct 19, 2025
One-click install
npx skills add https://github.com/ksoichiro/ChronoDawn --skill doc-maintenance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-maintenance
Source: https://github.com/ksoichiro/ChronoDawn/tree/main/.claude/skills/doc-maintenance
Command: npx skills add https://github.com/ksoichiro/ChronoDawn --skill doc-maintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps maintain documentation by guiding updates to version numbers, dependencies, and release preparations across multiple files and artifacts, ensuring consistency and reducing manual toil.

Core Features & Use Cases

  • Centralized maintenance checklists for version updates, boss/structure additions, and mod dependencies.
  • Step-by-step guidance for updating key files (gradle.properties, README.md, docs, and loader configs) to prepare releases.
  • Quick Start: describe your maintenance task and Claude will apply the appropriate checklist.

Quick Start

Simply describe the maintenance task (e.g., "update Minecraft to 1.21.2 across all docs and configs") and Claude will reference the correct checklist and provide recommended actions.

Frequently Asked Questions about doc-maintenance

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

FAQPage Schema
How do I update Minecraft version numbers across Gradle properties and documentation files?

To update Minecraft version numbers across Gradle properties and documentation files, describe your maintenance task and a standardized checklist guides updates for gradle.properties, README.md, docs, and loader configs to ensure consistency.

What is the best way to prepare a mod release with multiple dependency updates?

Preparing a mod release with multiple dependency updates requires a centralized maintenance checklist that enforces standardized processes for Gradle properties, loader metadata, and description documents during release preparation.

How do I add new bosses and structures to Chrono Dawn documentation and configs?

Adding new bosses and structures to Chrono Dawn documentation requires referencing the maintenance checklist to receive step-by-step recommended actions for updating description documents and build configs.

Does this documentation maintenance process work with Gradle build configurations?

Yes, the documentation maintenance process works with Gradle build configurations by listing updated files and workflows for Gradle properties and loader metadata alongside standard README and docs updates.

Why do my documentation updates end up inconsistent across multiple files?

Documentation updates end up inconsistent across multiple files when lacking a standardized process that lists updated files and workflows for Gradle properties, loader metadata, and description documents to enforce consistency.