- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add MiniMax-AI/mcode-stack --skill engineering-small-prs -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add MiniMax-AI/mcode-stack --skill engineering-small-prs -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add MiniMax-AI/mcode-stack --skill engineering-small-prs -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add MiniMax-AI/mcode-stack --skill engineering-small-prs -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/MiniMax-AI/mcode-stack/tree/HEAD/stacks/ronny/skills/engineering-small-prsDel publicador
Small PRs are easier to review thoroughly, safer to merge, easier to roll back, and less likely to waste work if the direction changes. "Small" means conceptually focused and self-contained, not merely a low line count.
Adapted from Google Engineering Practices Documentation, especially "Small CLs." Source: https://google.github.io/eng-practices/review/developer/small-cls.html. License: CC-BY 3.0.
A good PR:
Reviewers may reasonably reject a PR solely because it is too large to review well.
For schema, data, API, or infrastructure migrations, prefer an expand/contract sequence:
Each migration PR should state deployment order, rollback behavior, validation signal, and what must not happen until the next PR lands.
## Goal
[Final outcome]
## Proposed PR Sequence
| # | PR | Purpose | Depends On | Tests | Reviewer Notes |
|---|----|---------|------------|-------|----------------|
| 1 | Add characterization tests for ... | Protect existing behavior before refactor | None | ... | ... |
| 2 | Extract ... without behavior change | Prepare smaller implementation | 1 | ... | ... |
| 3 | Implement ... vertical slice | User-visible behavior | 2 | ... | ... |
## Migration Safety
- Expand/contract phase:
- Backfill/validation:
- Observability:
- Rollback:
## Build Safety
- Each PR keeps:
- Rollback notes:
## Large-Change Risk
- What could not be split:
- Reviewer consent needed:
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 planning, splitting, shrinking, or sequencing large features, refactors, migrations, or pull requests into small reviewable PRs or CLs. TRIGGER on "split this PR", "this diff is too large", "
---name: engineering-small-prsdescription: Use when planning, splitting, shrinking, or sequencing large features, refactors, migrations, or pull requests…---# stacks/ronny/skills/engineering-small-prs/SKILL.mdResumen general
Use when planning, splitting, shrinking, or sequencing large features, refactors, migrations, or pull requests into small reviewable PRs or CLs. TRIGGER on "split this PR", "this diff is too large", "stacked PRs", "change sequence", "reviewable chunks", "migration plan", "how should I break this up?", or implementation scope too broad for one review. DO NOT TRIGGER for full code review, PR description writing, or tiny one-file edits that already form one self-contained change.
Preguntas frecuentes
Descarga stacks/ronny/skills/engineering-small-prs/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/MiniMax-AI/mcode-stack.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.