- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add MiniMax-AI/mcode-stack --skill engineering-change-descriptions -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add MiniMax-AI/mcode-stack --skill engineering-change-descriptions -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add MiniMax-AI/mcode-stack --skill engineering-change-descriptions -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add MiniMax-AI/mcode-stack --skill engineering-change-descriptions -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/MiniMax-AI/mcode-stack/tree/HEAD/stacks/ronny/skills/engineering-change-descriptionsFrom the publisher
A change description is permanent engineering history. It should let reviewers understand the change now and help future maintainers find and understand it later.
Adapted from Google Engineering Practices Documentation, especially "Writing good CL descriptions." Source: https://google.github.io/eng-practices/review/developer/cl-descriptions.html. License: CC-BY 3.0.
Even small changes deserve context when the reason is not obvious.
The first line should:
Include only useful context:
Before submitting, reread the description after review changes and make sure it still matches the final diff.
[Imperative one-line summary]
## Why
[Problem, user need, production issue, maintainability reason, or design context.]
## What Changed
- ...
- ...
## Testing
- ...
## Risk / Rollback
- Risk:
- Rollback:
[Imperative one-line summary]
[One paragraph explaining why this change exists and any non-obvious context.]
Testing: [command or manual check]
[Describe the structural change and what it replaces]
This prepares for [future change] by [specific reason], without intentionally changing behavior.
Testing: [existing or new tests that protect behavior]
[Describe the mechanical rewrite]
Generated by [tool/version/command] to [reason]. Manual edits: [none/list].
Verification: [format/test/build command]
When improving an existing description:
Also published in agentara/skills (MIT, Copyright (c) 2026 agentara) by the same author. The content is adapted from Google Engineering Practices under CC-BY 3.0; see the source note above. Full notices: NOTICE.md.
Use when writing, rewriting, or reviewing PR/CL descriptions, commit messages, or code-change summaries that explain what changed and why. TRIGGER on "write PR description", "improve this commit messa
---name: engineering-change-descriptionsdescription: Use when writing, rewriting, or reviewing PR/CL descriptions, commit messages, or code-change summaries that…---# stacks/ronny/skills/engineering-change-descriptions/SKILL.mdOverview
Use when writing, rewriting, or reviewing PR/CL descriptions, commit messages, or code-change summaries that explain what changed and why. TRIGGER on "write PR description", "improve this commit message", "summarize this diff", "CL description", "change description", or "make this PR/CL description easier to review". DO NOT TRIGGER for code review, PR splitting, code restructuring, user-facing changelogs, or reviewer replies unless the requested output is a change description.
FAQ
Download stacks/ronny/skills/engineering-change-descriptions/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/MiniMax-AI/mcode-stack.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.