Menú
GitLab environment context: project resolution, authentication, and API conventions for GitLab instances.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional 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-gitlab-ops |
| description | GitLab environment context: project resolution, authentication, and API conventions for GitLab instances. |
| roles | ["architect","sysadmin","developer","qe","security_analyst"] |
When working on an Event from the Headhunter, the event document contains the authoritative project path and MR/PR URL in the GitLab Context section. Use THAT project path and MR/PR URL for all API calls.
Use the Service Lookup only for check Aligner events or when a user asks.
Extract from the event document:
MR/PR URL -- use this for the target MRProject -- use this as the project path for API callsGitLab CLI tools and MCP tools are pre-configured via $GITLAB_HOST. TLS behavior is controlled by the deployment environment. You do not need to handle authentication setup.
Available environment variables:
GITLAB_TOKEN -- Personal Access Token for API callsGITLAB_HOST -- The GitLab hostnameGit operations to $GITLAB_HOST use the pre-configured TLS settings.
GitLab MCP tools are available in your tool list. Prefer them for structured API interactions -- they handle authentication and pagination automatically. CLI and direct API access are available as fallback.
When dispatched to work on an MR/PR, your first action after reading the event context is to post a brief comment on the MR/PR announcing what you are investigating or doing. This gives visibility to anyone watching the MR in GitLab.
Format: Darwin ({role}): {one sentence describing your actual task}
Post once on arrival. Do not post updates to the MR -- use team_send_message
for progress updates to FRIDAY instead.
GitLab API requires URL-encoded project paths for nested groups. For example, org/group/subgroup/project must be encoded as org%2Fgroup%2Fsubgroup%2Fproject. Ensure project paths are properly encoded when constructing API requests.