comment-writer

Lead with the actionable point instead of recapping the PR, explain the technical reason for any requested change, and keep it to one to three short paragraphs. Focus on the highest-value issue rather than listing every minor preference.

State the concrete reason, such as exceeding a 400-line budget, then suggest a specific split order like foundation plus tests first, then integration, then docs. This gives the author a clear path forward without sounding dismissive.

Yes, the Skill matches the target thread's language by default, so a Spanish issue gets a Spanish comment. It uses neutral professional Spanish unless the context or user explicitly requests a regional tone.

Aim for warm and direct, like a thoughtful teammate rather than a corporate bot. Start with the useful point, avoid pile-ons over trivial preferences, and skip em dashes in favor of commas or periods.

Avoid it for sensitive conversations like performance concerns or conflict resolution where fully personal wording matters. It is designed for routine technical collaboration such as PR feedback, approvals, and issue replies.