Menu
Version bump conventions and changelog update rules for the m plugin
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | versioning |
| description | Version bump conventions and changelog update rules for the m plugin |
The m plugin follows semantic versioning (MAJOR.MINOR.PATCH):
| Bump | When |
|---|---|
patch | Bug fixes, typo corrections, minor skill/command refinements |
minor | New commands, new skills, notable skill enhancements |
major | Breaking changes to command interfaces, skill restructuring, plugin format changes |
The canonical version lives in molcajete/.claude-plugin/plugin.json under the "version" field.
Use scripts/bump.sh to increment the version:
./scripts/bump.sh patch # 2.3.9 -> 2.3.10
./scripts/bump.sh minor # 2.3.9 -> 2.4.0
./scripts/bump.sh major # 2.3.9 -> 3.0.0
After bumping, update prd/changelog.md with:
| Section | Content |
|---|---|
| Added | New commands, skills, or features |
| Changed | Updates to existing commands or skills |
| Fixed | Bug fixes and corrections |
| Removed | Deleted commands, skills, or deprecated items |
scripts/bump.sh <level>prd/changelog.mdBumps version to X.Y.ZDecompose a use case into ordered, independently-executable slices. Owns the slice file format — one Markdown file per slice, holding the contract surface and the test plan as language-tagged snippets and nested bullets. Referenced by /m:plan (default and cover modes) to emit the per-slice files the build consumes.
Engineering principles that bind any code Molcajete plans, builds, or reviews — integration tests as the trust contract, hexagonal default, dependency injection, 80% coverage floor, universal software craft (small functions, clear boundaries, no god files, refactor to reuse), technology-agnostic. Loaded by /m:plan and /m:build. Mirrored to the host project at `.claude/rules/principles.md` by /m:setup.
Technology-agnostic rules for the test-first build loop. Implementer and Validator role contracts, outer-edge mocking, reading specs/TECH-STACK.md, Runner Inference, coverage gate scoped to touched files, reactive refactor.
Rules and templates for the /m:setup command. One-shot foundation setup from a single project description plus codebase detection. Generates PROJECT.md, TECH-STACK.md, ACTORS.md, GLOSSARY.md, MODULES.md, DOMAINS.md, FEATURES.md, and .molcajete/settings.json.
Conventions for generating README.md files as LLM-optimized navigation documents. Covers YAML frontmatter, file tables, subdirectory tables, Mermaid diagrams, and stack-specific variants (backend, frontend, config). Used by /m:doc and the documentation task in build plans.
Status as first-class state on slices, use cases, and features. Defines the three-value enum (pending | dirty | implemented), per-level semantics, the bottom-up roll-up rule, and which command writes which level's status. Status lives on the artifact's frontmatter and is the source of truth — the CHANGELOG is for context and markers, not state.