القائمة
Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Trigger: update skills, commands, agents, orchestrator assets. Sync upstream AI into the @ai canonical tree while preserving local policy.
Trigger: judgment day, judgement day, dual review, adversarial review, juzgar. Run blind dual review, fix confirmed issues, then re-judge.
Trigger: judgment day, judgement day, dual review, adversarial review, juzgar. Run blind dual review, fix confirmed issues, then re-judge.
Trigger: judgment day, judgement day, dual review, adversarial review, juzgar. Run blind dual review, fix confirmed issues, then re-judge.
Design and manipulate Penpot projects using the Penpot MCP Plugin. Use when working with Penpot designs including creating shapes, boards, layouts, styling, components, generating CSS/HTML from designs, or any design task when Penpot MCP is connected. Triggers on mentions of "Penpot", design manipulation requests with connected MCP, or design-to-code workflows.
Trigger: sdd init, iniciar sdd, openspec init. Initialize SDD context, testing capabilities, registry, and persistence.
| name | comment-writer |
| description | Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments. |
| license | Apache-2.0 |
| metadata | {"author":"iperez","version":"1.0"} |
Load this skill whenever you write a comment that another human will read.
Use it for:
| Rule | Requirement |
|---|---|
| Be useful fast | Start with the actionable point. Do not recap the whole PR before feedback. |
| Be warm and direct | Sound like a thoughtful teammate, not a corporate bot. |
| Keep it short | Prefer 1 to 3 short paragraphs or a tight bullet list. |
| Explain why | Give the technical reason when asking for a change. |
| Avoid pile-ons | Comment on the highest-value issue, not every tiny preference. |
| Match target context language | Write in the target context language by default: Spanish thread -> Spanish comment, English thread -> English comment, mixed context -> target message language. If the user explicitly requests a language or tone, follow that request. For Spanish comments, use neutral/professional Spanish unless the user or target context clearly calls for regional tone (e.g. voseo). |
| No em dashes | Use commas, periods, or parentheses instead. |
<Direct observation or request>
<Why it matters, only if needed>
<Concrete next action>
Good approach overall. I'd split this into a separate commit because it mixes validation logic with UI wiring.
That keeps the reviewer's focus narrower and makes rollback cleaner if the integration fails.
Approved. The scope is clear and the change is well-contained.
For the next PR, add links to the previous and following PRs so the chain stays navigable.
This PR exceeds the 400-line budget, so we need to split it or justify `size:exception`.
Suggested order: foundation + tests first, then integration, then docs. That gives each review a clear start and end.
# Inspect a PR before writing review feedback
gh pr view <PR_NUMBER> --json title,body,additions,deletions,changedFiles