Index of every page on this site: llms.txt
All skills
minimax-ai avatar

/engineering-change-descriptions

@0db1b4f
by MiniMaxminimax-ai/mcode-stack736 stars
50
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/minimax-ai/mcode-stack/engineering-change-descriptions

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈129 tokens for metadata: the name and description. ≈870 when used: this file.

Description uses 6.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈515 characters, or 6.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.
  • User-visible or developer-visible behavior changes.
  • Important implementation notes.
  • Known limitations or follow-up work.
  • Bug IDs, issue links, benchmark results, design docs, migration docs, or rollout plans.
  • Enough context for links that might later become inaccessible.
  • Test commands and results, when appropriate.

Before submitting, reread the description after review changes and make sure it still matches the final diff.

Templates

Standard PR

[Imperative one-line summary]

## Why
[Problem, user need, production issue, maintainability reason, or design context.]

## What Changed
- ...
- ...

## Testing
- ...

## Risk / Rollback
- Risk:
- Rollback:

Small Change

[Imperative one-line summary]

[One paragraph explaining why this change exists and any non-obvious context.]

Testing: [command or manual check]

Refactor

[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]

Generated or Mechanical Change

[Describe the mechanical rewrite]

Generated by [tool/version/command] to [reason]. Manual edits: [none/list].

Verification: [format/test/build command]

Rewrite Checklist

When improving an existing description:

  1. Extract the actual behavior from the diff.
  2. Replace vague first lines with a concrete action.
  3. Add the missing why.
  4. Preserve useful issue links and test evidence.
  5. Remove process noise that does not help reviewers or future maintainers.

Common Mistakes

  • Describing only the implementation without the reason.
  • Writing a title that future searchers cannot distinguish from similar changes.
  • Depending entirely on external links for crucial context.
  • Leaving the description stale after review significantly changes the diff.
  • Hiding risk, limitations, or rollout requirements because they feel inconvenient.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts23d3 checks · Risk SAFE
  • Gen Agent Trust Hub23d

    This skill provides guidelines and templates for writing high-quality engineering change descriptions and commit messages. It is purely instructional and contains no executable code or security risks.

  • Socket23d

    No alerts

  • Snyk23d

    Risk: LOW · No issues

Signed by skilld at 0db1b4f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 3 weeks ago

README badge

README badge for minimax-ai/mcode-stack/engineering-change-descriptions