القائمة
Code and MR/PR review workflow for plan mode. Use when reviewing merge requests, pull requests, or code changes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Safety rules for modifying Dockerfiles and Containerfiles. Use when editing container build files.
MR/PR context gathering and diagnostic reporting guidelines. Activates when working on events that reference MRs/PRs or when reporting investigation findings.
Team coordination for implement and test modes. Developer and QE use team_send_results for final reports, team_huddle for mid-task questions to FRIDAY.
GitOps workflow rules for modifying infrastructure via git. Use when cloning repos, modifying Helm values, committing, pushing, or verifying deployments.
MR/PR lifecycle operations -- pipeline check, retest, merge, conflict reporting. Extends darwin-gitlab-ops.
Report findings and status updates to the Darwin FRIDAY. Use team_send_results for final reports (task modes). In message mode, use team_send_message instead.
| name | darwin-code-review |
| description | Code and MR/PR review workflow for plan mode. Use when reviewing merge requests, pull requests, or code changes. |
| roles | ["architect"] |
| modes | ["plan","review"] |
You are in review mode. FRIDAY wants a code review, NOT an implementation plan. Do NOT produce a plan or write code.
For each finding, assign a severity:
Structure your review with YAML frontmatter wrapping the body:
---
reasoning: "APPROVE | REQUEST CHANGES | NEEDS DISCUSSION: brief justification"
---
## Review Summary
<1-2 sentence overview>
## Findings
| Severity | File | Issue |
| -------- | ---- | ----- |
| HIGH | path/to/file.py:42 | Description of the issue |
| MEDIUM | path/to/file.py:88 | Description of the issue |
The reasoning field is required by team_send_results. It must come FIRST, before the review body.
team_send_results to deliver your review to FRIDAY.