create-manifest

Name: create-manifest
Availability: InStock
Author: Herbivore

Generate Trellis migration manifests and English/Chinese MDX changelogs from git commits.

92|8|Updated May 15, 2026

Search Tags:#changelog #release #MDX #git commits #docs-site #migration manifest #trellis update

Ready to run

npx skills add https://github.com/LonelyHerbivore/Trellis-Herbivore --skill create-manifest

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-manifest
Source: https://github.com/LonelyHerbivore/Trellis-Herbivore/tree/main/.codex/skills/create-manifest
Command: npx skills add https://github.com/LonelyHerbivore/Trellis-Herbivore --skill create-manifest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the risk and effort of manually preparing accurate Trellis migration manifests and matching docs-site changelogs for each new release, especially when changes span many files and commit types.

Core Features & Use Cases

Commit-to-changelog analysis: Reviews commits since the last release tag and drafts conventional, technical changelog entries focused on user-observable source behavior.
Migration manifest authoring: Produces the required JSON fields for breaking behavior and file migrations so trellis update can guide users correctly.
Docs-site changelog synchronization: Generates both English and Chinese MDX changelogs and updates docs.json navbar/page lists for the new version.

Quick Start

Ask the AI to create the Trellis migration manifest and both docs-site changelog files for version 0.6.0-beta.14 by analyzing commits since the previous release tag and outputting the finalized manifest JSON and the required MDX updates.

Frequently Asked Questions about create-manifest

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

FAQPage Schema

How do I generate a Trellis migration manifest from git commits?▼

To generate a Trellis migration manifest from git commits, analyze the commit history since your previous release tag to extract user-observable behavior changes. This process categorizes conventional commits to produce the required JSON fields for breaking behaviors and recommendMigrate rules.

How do I automate docs-site changelog updates for a new release?▼

Automating docs-site changelog updates involves generating matching MDX changelog files from your git commit history. It updates the docs.json navbar and page lists to synchronize mirrored English and Chinese sections for the new release version.

What is a migration manifest and when do I need one?▼

A migration manifest is a JSON file that defines breaking behaviors and file migrations so `trellis update` can guide users correctly. You need one for patch, beta, rc, and minor releases where changelog voice and migration actions must be strictly accurate.

Does the changelog generation support both English and Chinese MDX files?▼

Changelog generation supports both English and Chinese MDX files by applying strict MDX structure rules. It mirrors the technical content across both language sections to ensure accurate docs-site synchronization for diverse audiences.

Do I need conventional commit messages to generate release changelogs?▼

You need conventional commit-style messages to generate accurate release changelogs. The analysis process relies on these commit conventions to draft technical changelog entries focused on user-observable source behavior.

Why are my manually written Trellis manifests failing during trellis update?▼

Manually written Trellis manifests fail during `trellis update` when they lack correct JSON fields for breaking behavior or recommendMigrate rules. Automating manifest generation from git commits ensures strict manifest correctness and prevents manual oversights.