docs-changelog

Generate MDX changelog pages with required frontmatter under docs/changelog.

1|Updated May 20, 2026
One-click install
npx skills add https://github.com/mDevsLabs/mAI --skill docs-changelog-mdevslabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docs-changelog
Source: https://github.com/mDevsLabs/mAI/tree/main/.agents/skills/docs-changelog
Command: npx skills add https://github.com/mDevsLabs/mAI --skill docs-changelog-mdevslabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The repetitive task of drafting and maintaining consistent website changelog posts is time-consuming and error-prone; this skill standardizes the process for EN/ZH updates under docs/changelog/*.mdx.

Core Features & Use Cases

  • Generates MDX-formatted changelog pages with required frontmatter (title, description) and user-facing content.
  • Enforces the strict file-naming convention (e.g., XXX-XX-XX-XXXX) and coordinates with bilingual i18n and microcopy companions to ensure consistent terminology across languages.
  • Supports creating new entries for product updates, release notes, or documentation changes, and updating existing changelogs.

Quick Start

Create a new changelog entry named XXX-XX-XX-XXXX.mdx under docs/changelog with the proper frontmatter and content.

Frequently Asked Questions about docs-changelog

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

FAQPage Schema
How do I generate bilingual changelog pages in MDX format?▼

You generate bilingual changelog pages by creating MDX files under docs/changelog with required frontmatter like title and description. This standardizes EN/ZH product updates and documentation changes into consistent multilingual entries.

What is the required file-naming convention for docs changelog entries?▼

The required file-naming convention for docs changelog entries is XXX-XX-XX-XXXX. Adhering to this strict pattern under the docs/changelog directory ensures proper chronological sorting and automated retrieval of release notes.

How do I maintain terminology consistency for i18n documentation updates?▼

Maintain terminology consistency for i18n documentation updates by coordinating with bilingual i18n and microcopy companion skills. This integration enforces standardized vocabulary and phrasing across EN/ZH changelog entries during generation.

Can I use this approach to update existing changelogs instead of creating new ones?▼

Yes, you can use this approach to update existing changelogs. The process supports modifying existing MDX documentation files alongside creating new entries, while continuously enforcing required frontmatter and strict file-naming conventions.

What frontmatter is needed for a standardized documentation changelog?▼

The frontmatter needed for a standardized documentation changelog includes name and description fields. Enforcing these specific metadata properties within MDX files guarantees that user-facing content and release notes render correctly.