Menu
MR/PR comment thread interaction -- read threads, respond concisely. Extends darwin-gitlab-ops.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle 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-mr-conversation |
| description | MR/PR comment thread interaction -- read threads, respond concisely. Extends darwin-gitlab-ops. |
| requires | ["darwin-gitlab-ops"] |
| roles | ["developer","sysadmin"] |
Read MR/PR comment threads, understand context, and respond concisely.
Retrieve the MR/PR discussion threads to understand the context and history of the conversation.
Post a concise, actionable response as an MR/PR comment. Prefix with "Darwin:" to identify automated responses.
Always end your response with a clear recommendation for FRIDAY. Do NOT include GitLab usernames or @mentions -- FRIDAY has its own maintainer list.
