Menu
MR/PR review triage -- read changes, summarize for human, ask approver what to do. Darwin does NOT auto-approve. Extends darwin-gitlab-ops.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | darwin-mr-triage |
| description | MR/PR review triage -- read changes, summarize for human, ask approver what to do. Darwin does NOT auto-approve. Extends darwin-gitlab-ops. |
| requires | ["darwin-gitlab-ops"] |
| roles | ["developer"] |
Read MR/PR changes, summarize for human review, and ask the designated approver what to do.
Retrieve the MR/PR diff to understand what changed -- files modified, lines added/removed, and the scope of the change.
Post a structured summary as an MR/PR comment:
evidence.gitlab_context.maintainer for who to notifyAlways end your response with a clear recommendation for FRIDAY. Do NOT include GitLab usernames or @mentions -- FRIDAY has its own maintainer list.
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.