メニュー
Build and push multi-platform Docker images to Google Artifact Registry. Use when user asks to build, push, or deploy a Docker image with a tag. Triggers: "build and push", "push docker image", "build with tag", "deploy image".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | docker-build-push |
| description | Build and push multi-platform Docker images to Google Artifact Registry. Use when user asks to build, push, or deploy a Docker image with a tag. Triggers: "build and push", "push docker image", "build with tag", "deploy image". |
Build and push multi-platform Docker images to Google Artifact Registry for any teammelosys repository.
europe-north1-docker.pkg.dev/nais-management-233d/teammelosys/{REPO_NAME}
Replace {REPO_NAME} with the actual repository name (e.g., melosys-api, melosys-web, melosys-eessi).
# Get repo name from git remote or directory name
REPO_NAME=$(basename "$(git rev-parse --show-toplevel 2>/dev/null || pwd)")
echo "Repository: $REPO_NAME"
| Project Type | Detection | Build Command |
|---|---|---|
| Maven/Java/Kotlin | pom.xml exists | make build-fast or mvn package -DskipTests |
| Node.js/pnpm | pnpm-lock.yaml exists | pnpm install && pnpm build |
| Node.js/npm | package-lock.json exists | npm ci && npm run build |
| Makefile only | Makefile exists | make build |
docker buildx build --platform linux/amd64,linux/arm64 \
-t europe-north1-docker.pkg.dev/nais-management-233d/teammelosys/${REPO_NAME}:TAG \
--push .
Replace TAG with user-specified tag.
REPO_NAME=$(basename "$(git rev-parse --show-toplevel 2>/dev/null || pwd)")--pushdocker buildx create --name multiplatform --use --driver docker-container || docker buildx use multiplatform
Message: "Reauthentication failed"
Solution: Ask user to run gcloud auth login, then retry
Cause: Image built only for arm64
Solution: Use --platform linux/amd64,linux/arm64 flag
Solution: Check if Dockerfile exists in repo root. Some repos may have it in a subdirectory.
After successful push:
Done!
Image details:
- Repository: {REPO_NAME}
- Tag: europe-north1-docker.pkg.dev/nais-management-233d/teammelosys/{REPO_NAME}:TAG
- Platforms: linux/amd64, linux/arm64
- Manifest digest: sha256:...
NAV-spesifikk PR med Jira-nummer krav og norsk format. Triggers: "/nav-pr", "/nav-create-pr", "lag pr", "opprett pr" Use when: Creating PRs with NAV conventions (Jira prefix required, Norwegian, Jira links).
Add new SED types, BUC types, and XSD validation to the melosys-mock RINA/EUX implementation. Use this skill whenever working with the RINA mock — adding SED support (A001-A012, X001-X008), updating BUC-to-SED mappings, adding XSD schemas, debugging mock endpoint issues, or understanding the mock architecture for EESSI integration. Also use when working in melosys-e2e-tests and you need to extend what the mock supports for a new test scenario. Triggers: "legg til SED", "ny SED-type", "mock SED", "eux-rina-mock", "RINA mock", "add SED to mock", "BUC type", "XSD for SED", "mock endepunkt", "mock støtter ikke", "trenger mock for", "utvide mock"
Expert knowledge of NAV SED to RINA SED mapping in eux-rina-api (CDM 4.4). Use when: (1) Creating or modifying SED mappers in melosys-eessi, (2) Mocking eux-rina-api responses for e2e or local testing, (3) Understanding the RINA template JSON structure and $nav/$medlemskap prefixes, (4) Debugging SED mapping issues between NAV format and EESSI format, (5) Understanding which fields map to which RINA paths for specific SED types (A001-A012, X001-X008), (6) Adding new fields during CDM version upgrades (e.g., CDM 4.3 → 4.4), (7) Understanding kodeverk/code mappings for enums and radio buttons, (8) Troubleshooting PDF generation for SEDs.
Generate OAuth tokens and call local Melosys services (melosys-api, melosys-eessi, eux-rina-api, melosys-mock). Use when debugging API calls, testing endpoints, or needing authentication tokens for local development.
Debug SED flows across melosys-eessi → eux-rina-api → RINA mock. Use when: (1) XSD validation errors from RINA or melosys-mock, (2) Tracing missing/wrong NAV SED fields to RINA format, (3) Figuring out what NAV SED JSON is needed for CDM 4.4 (A008), (4) Improving mock XSD validator to show actionable errors, (5) Debugging send-SED flow end-to-end, (6) JSON-to-XML conversion and element ordering in mock, (7) Understanding eux-rina-api template mappings. Triggers: "XSD validation", "SED feil", "mapping error", "missing field", "element order", "RINA validation", "NAV SED", "CDM 4.4", "A008", "trace SED"
NAV-spesifikk commit med norsk format og valgfritt Jira-nummer. Triggers: "/nav-commit", "nav commit", "lag commit", "committ endringene" Use when: User wants to commit with NAV conventions (Norwegian, optional Jira number).