원클릭으로 Manus에서 모든 스킬 실행

maintainer

스타1

포크0

업데이트2026년 3월 26일 21:57

Maintainer actions for MR trusted branch sync. Check sync status between source and trusted branches, then push to the trusted branch so the child pipeline can run. Use when the user says 'allow MR', 'sync trusted branch', 'trigger trusted tests', or asks to review and approve an MR for pipeline execution. Not for: code review or pipeline analysis (use mr-review), creating or merging MRs (use glab), or test reliability (use osdu-quality).

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

danielscholl

danielscholl/claude-osdu

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

OSDU Maintainer Workflow

Maintainer actions for GitLab MR pipelines. Review MRs and allow them to proceed by syncing the trusted branch.

Background

Developers create MRs on regular branches. The child pipeline requires a "trusted" branch that only maintainers can create/sync. The trigger-trusted-tests job verifies the trusted branch SHA matches the source branch before allowing the child pipeline to run.

Actions

Action	Purpose	Default
`review`	Analyze MR changes, show sync status, provide recommendation	Default
`allow`	Sync trusted branch and retry pipeline job	—

Input Parsing

review or no action → review mode
allow → allow mode
MR number or full GitLab URL accepted
Auto-detect from current branch if omitted

URL Parsing

From https://community.opengroup.org/osdu/platform/security-and-compliance/entitlements/-/merge_requests/904:

Host: community.opengroup.org
Project path: osdu/platform/security-and-compliance/entitlements
MR number: 904

CRITICAL: glab defaults to gitlab.com. For OSDU, ALL glab api commands MUST use:

GITLAB_HOST=community.opengroup.org glab api ...

Review Action

Get MR Metadata — title, author, labels, target branch
Check Milestone & Labels — flag missing milestone, suggest labels based on changed files
Analyze Changes — categorize by risk (Dependencies/CI-CD/Source/Tests/Docs/Secrets)
Show Commit History — check conventional commits
Analyze Code Changes — summarize modifications, purpose, impact
Security Checks — scan for hardcoded secrets, suspicious patterns
Check Sync Status — compare source branch SHA vs trusted branch SHA
Provide Recommendation — APPROVE / REVIEW NEEDED / CAUTION

Label Suggestions

Change Pattern	Suggested Label
Common/shared code	`common`
Azure-specific paths	`Azure`
GCP-specific paths	`GCP`
AWS/IBM-specific paths	`AWS` / `IBM`
pom.xml, package.json	`dependencies`
.gitlab-ci.yml, Dockerfile	`ci/cd`
.md, docs/*	`documentation`

Allow Action

Parse MR number or detect from branch
Derive trusted branch: trusted-<source-branch>
Sync: git push origin <source-branch>:refs/heads/<trusted-branch> --force
Retry trigger-trusted-tests job

Multi-Repo Context

In a multi-repo workspace:

Determine which service repo the MR belongs to
If a local clone exists, use it for git push operations
If no local clone, use a temp clone for the sync
The project ID resolution uses the GitLab API with URL-encoded paths

이 저장소의 다른 Skills

같은 저장소

briefing

danielscholl/claude-osdu

Generate daily OSDU briefing notes by aggregating GitLab MRs, SPI fork health, vault goals, and brain knowledge into an insightful daily note. Use when the user says "gm", "good morning", "briefing", "daily briefing", "morning standup", "what's on my plate", or "start my day". Not for: ad-hoc status checks or single-service queries.

2026-04-011

forks

danielscholl/claude-osdu

Fork management lifecycle for Azure OSDU SPI service forks — three-branch strategy, upstream sync, cascade integration, conflict resolution, template propagation, and multi-repo status monitoring across 8 service forks. Use when checking sync status, reviewing cascades, resolving conflicts, triggering manual syncs, managing fork_upstream/fork_integration/main branches, or coordinating template updates across osdu-spi-* repos. Not for: infrastructure deployment (use iac skill), OSDU GitLab services (use osdu plugin), or tool installation (use setup skill).

2026-03-311

health

danielscholl/claude-osdu

Comprehensive health assessment of deployed SPI environments — cluster infrastructure, Azure PaaS resources, workloads, and OSDU platform services. Use when the user asks about SPI environment health, cluster status, Azure PaaS health, CosmosDB status, Service Bus health, or wants a report on their deployed SPI environments. Trigger on phrases like "report on my SPI environment", "environment health", "how is my cluster", "cluster status", "is CosmosDB healthy", or "what's deployed". Not for: deploying or modifying infrastructure (use the iac skill), fork management (use the forks skill), installing tools (use the setup skill), or CIMPL environments (use cimpl:health).

2026-03-311

iac

danielscholl/claude-osdu

Infrastructure as Code for Azure SPI — Terraform modules, Azure PaaS services (CosmosDB, Service Bus, Storage, Key Vault), Helm/Kustomize deployments, AKS Deployment Safeguards, azd integration, multi-partition support, and systematic debugging for the osdu-spi-infra repository. Use when working with SPI Terraform, Azure PaaS provisioning, azd up/down, Workload Identity, multi-partition resources, feature flags, blue/green stacks, deployment failures, or infrastructure verification. Not for: fork management (use the forks skill), CIMPL infrastructure (use cimpl:iac), OSDU platform services, or tool installation (use setup skill).

2026-03-311

setup

danielscholl/claude-osdu

Check and install CLI tool dependencies required by SPI skills. Use when the user says "setup", "check dependencies", "what do I need installed", or when a skill fails with "command not found". This does NOT set up a specific project. It ensures the tools needed by SPI skills are present on the machine. Not for: project-specific setup, IDE configuration, or environment provisioning.

2026-03-311

status

danielscholl/claude-osdu

Cross-repository status aggregation for SPI service forks — issues, pull requests, workflow runs, and alerts across all fork repos in a single dashboard. Highlights cascade-blocked issues, human-required labels, failing workflows, and pending sync/template-sync PRs. Configurable org via SPI_ORG. Use when checking overall fork health, asking what's open across repos, looking for blocked cascades, pending reviews, needing a dashboard of all SPI fork activity, or monitoring the state of the engineering system. Trigger on "status", "dashboard", "what's open", "any blocked cascades", "pending PRs across forks", "fork health overview", "failing workflows", "issues across repos". Not for: triggering syncs or cascades (use forks skill), infrastructure health or cluster status (use health skill), deploying (use iac skill), tool installation (use setup skill).

2026-03-311

name	maintainer
allowed-tools	Bash, Read, Glob
description	Maintainer actions for MR trusted branch sync. Check sync status between source and trusted branches, then push to the trusted branch so the child pipeline can run. Use when the user says 'allow MR', 'sync trusted branch', 'trigger trusted tests', or asks to review and approve an MR for pipeline execution. Not for: code review or pipeline analysis (use mr-review), creating or merging MRs (use glab), or test reliability (use osdu-quality).

OSDU Maintainer Workflow

Maintainer actions for GitLab MR pipelines. Review MRs and allow them to proceed by syncing the trusted branch.

Background

Actions

Action	Purpose	Default
`review`	Analyze MR changes, show sync status, provide recommendation	Default
`allow`	Sync trusted branch and retry pipeline job	—

Input Parsing

review or no action → review mode
allow → allow mode
MR number or full GitLab URL accepted
Auto-detect from current branch if omitted

URL Parsing

From https://community.opengroup.org/osdu/platform/security-and-compliance/entitlements/-/merge_requests/904:

Host: community.opengroup.org
Project path: osdu/platform/security-and-compliance/entitlements
MR number: 904

CRITICAL: glab defaults to gitlab.com. For OSDU, ALL glab api commands MUST use:

GITLAB_HOST=community.opengroup.org glab api ...

Review Action

Get MR Metadata — title, author, labels, target branch
Check Milestone & Labels — flag missing milestone, suggest labels based on changed files
Analyze Changes — categorize by risk (Dependencies/CI-CD/Source/Tests/Docs/Secrets)
Show Commit History — check conventional commits
Analyze Code Changes — summarize modifications, purpose, impact
Security Checks — scan for hardcoded secrets, suspicious patterns
Check Sync Status — compare source branch SHA vs trusted branch SHA
Provide Recommendation — APPROVE / REVIEW NEEDED / CAUTION

Label Suggestions

Change Pattern	Suggested Label
Common/shared code	`common`
Azure-specific paths	`Azure`
GCP-specific paths	`GCP`
AWS/IBM-specific paths	`AWS` / `IBM`
pom.xml, package.json	`dependencies`
.gitlab-ci.yml, Dockerfile	`ci/cd`
.md, docs/*	`documentation`

Allow Action

Parse MR number or detect from branch
Derive trusted branch: trusted-<source-branch>
Sync: git push origin <source-branch>:refs/heads/<trusted-branch> --force
Retry trigger-trusted-tests job

Multi-Repo Context

In a multi-repo workspace:

Determine which service repo the MR belongs to
If a local clone exists, use it for git push operations
If no local clone, use a temp clone for the sync
The project ID resolution uses the GitLab API with URL-encoded paths