- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add MiniMax-AI/mcode-stack --skill engineering-review-comments -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add MiniMax-AI/mcode-stack --skill engineering-review-comments -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add MiniMax-AI/mcode-stack --skill engineering-review-comments -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add MiniMax-AI/mcode-stack --skill engineering-review-comments -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/MiniMax-AI/mcode-stack/tree/HEAD/stacks/ronny/skills/engineering-review-comments게시자 제공
Review comments should improve the code and the developer's future judgment. They should be clear about severity, grounded in engineering reasoning, and directed at the code rather than the person.
Adapted from Google Engineering Practices Documentation, especially "How to write code review comments" and "Handling pushback in code reviews." Source: https://google.github.io/eng-practices/review/reviewer/comments.html. License: CC-BY 3.0.
Use this structure for non-trivial comments:
SEVERITY: Observation about the code.
Why this matters: engineering reason, user impact, maintainability impact, or violated project rule.
Requested action: concrete fix, question, or decision the author needs to make.
Keep tiny comments tiny. Use the full shape when intent could be misunderstood.
BLOCKER: must change before approval because correctness, maintainability, security, data, test, or operational risk is unacceptable.IMPORTANT: should change before approval; can be waived only with an explicit rationale.QUESTION: reviewer needs information before deciding.NIT: minor polish. Do not block approval.OPTIONAL or CONSIDER: a suggestion the author can decline.FYI: educational context or future consideration; no action expected.Use these patterns directly when helpful:
BLOCKER: This path can return success before the write is durable.
If the process crashes after this point, callers will believe the operation completed even though the data may be missing. Please either move the success response after the durable write or make the operation explicitly asynchronous and observable.
QUESTION: What guarantees that this callback cannot run concurrently?
If it can run in parallel, `pending` can be decremented twice from the same value. If the framework serializes this callback, please add a short comment at the boundary where that guarantee comes from.
NIT: This helper name reads as if it validates the payload, but it only normalizes whitespace. Could we rename it to `normalizePayloadText`?
OPTIONAL: Consider extracting this branch into a named helper. The current version is correct, but a helper would make the three policy cases easier to scan.
When the author disagrees:
Do not keep arguing because you wrote the first comment. The goal is the best code, not defending the initial wording.
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 drafting, rewriting, classifying, or improving code review comments as a reviewer. TRIGGER on rough review notes, requests to make comments clearer or kinder, severity labels, "how should I p
---name: engineering-review-commentsdescription: Use when drafting, rewriting, classifying, or improving code review comments as a reviewer. TRIGGER on rough…---# stacks/ronny/skills/engineering-review-comments/SKILL.md개요
Use when drafting, rewriting, classifying, or improving code review comments as a reviewer. TRIGGER on rough review notes, requests to make comments clearer or kinder, severity labels, "how should I phrase this review comment?", "write review comments", author pushback, or turning findings into PR comments. If role is unclear, ask reviewer or author. DO NOT TRIGGER for full code review, PR descriptions, or author responses unless wording is requested.
FAQ
게시자에게서 stacks/ronny/skills/engineering-review-comments/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/MiniMax-AI/mcode-stack에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.