engineering-change-descriptions SKILL.md skillA
engineering-change-descriptions from minimax-ai/mcode-stack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add minimax-ai/mcode-stack/engineering-change-descriptions@git:20261028.c6ee606Pins git:20261028.c6ee606 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- minimax-ai/mcode-stack
- Path
stacks/ronny/skills/engineering-change-descriptions/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261028.c6ee606, committed Oct 28, 2026
- Size
- 4,022 bytes
- Repository stars
- 495
- License
- MIT
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Engineering Change Descriptions 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. ## What a Good Description Answers - What changed? - Why did it change? - What context, constraints, or tradeoffs are not obvious from the code? - How was it tested? - What risks, migrations, rollbacks, or follow-ups should reviewers know? Even small changes deserve context when the reason is not obvious. ## First Line The first line should: - Stand alone in version control history. - Be short, specific, and focused on what the change does. - Use an imperative form when writing a commit or CL title. - Avoid vague labels like "fix bug", "cleanup", "phase 1", "misc", or "add helpers". - Be followed by a blank line when there is a body. ## Body Include only useful context: - Problem being solved. - Why this approach was chosen. …
Read the whole file at its exact version.
How to install
mdr add minimax-ai/mcode-stack/engineering-change-descriptions@sha256:2fb12ecadcb5f068The line at the top of this page pins the label git:20261028.c6ee606, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_t7so566xpdq3qxmw)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 28, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4022 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
minimax-ai/mcode-stack · 495 stars · license MIT · pushed 2026-10-29 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t7so566xpdq3qxmw GET https://markdownregistry.com/api/v1/resolve?ref=minimax-ai/mcode-stack/engineering-change-descriptions GET https://markdownregistry.com/api/v1/blob/2fb12ecadcb5f0681f6384cf3ab2bc1aabb9c59017cdba57b39f0d1bdbcf1456
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.