菜单
Bootstrap the gitignored .claude/CLAUDE.md for any api-cp-* or service-cp-* repo with three @import lines pointing to hmcts-apim-sdlc-orchestrator context standards. Runs automatically on every session start via the SessionStart hook — invoke manually only to force an update.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when working inside an api-cp-* repo and the user wants to publish/expose their API docs, "add my API to the catalog", set up the publish-api-docs workflow, or get a hmcts.github.io docs site. Wires the current repo into the amp-catalog Swagger UI pipeline, handles the two one-time GitHub Pages admin gaps that fail silently otherwise, and verifies the live site. This is the per-repo counterpart to the catalog-publisher agent, which only touches amp-catalog/docs/apis.json.
Wire up auto-dev and auto-SIT deployment CI for a service-cp-* repo after Azure provisioning and cp-vp-aks-deploy registration are complete. Idempotent — safe to invoke again if the jobs already exist. Use when a service-cp-* repo is missing the deploy-dev and deploy-sit jobs in its ci-build-publish.yml, or when setting up a newly bootstrapped service for the first time.
Start a new HMCTS API-Marketplace API specification repo using the canonical HMCTS template (api-hmcts-crime-template) as master source. Use when creating a new api-cp-* repo (OpenAPI-first, spec-only) distinct from a runtime service-cp-* service.
Stand up a new HMCTS API-Marketplace service-cp-* using the canonical HMCTS template (service-hmcts-crime-springboot-template) as master source. Use when creating a new Spring Boot service for the Common Platform.
Use when the user wants to review, audit, or check an OpenAPI v3 spec — applies HMCTS data-sharing policy (UK GDPR/DPA 2018), infrastructure SLA (Azure APIM/AKS), API standards, and security standards (OAuth 2, TLS, input validation). Returns a scored report with Critical/Warning/Info findings.
Export a self-contained, night-friendly HTML artifact for a CPP pipeline stage — using the right template from the bundled gallery. Use whenever a decision must be made, a plan needs improving, or a design gap is discovered — AND always to export the implementation plan before any code is written. Picks the template that fits the scenario (plan, decision, comparison, architecture, investigation, status) and writes it to docs/pipeline/artifacts/. <example> user: "We've finished the design — get ready to implement the booking engine." assistant: "Before implementation starts I'll use export-design-artifact to export the implementation plan (template 03) to docs/pipeline/artifacts/ and surface it at the Stage 4 gate." </example> <example> user: "Should the move-to-past action be a new endpoint or extend the existing one?" assistant: "That's a decision — I'll use export-design-artifact to produce a decision record (template 07) weighing the options before we commit." </example> <example> user: "The design does
| name | bootstrap-context |
| description | Bootstrap the gitignored .claude/CLAUDE.md for any api-cp-* or service-cp-* repo with three @import lines pointing to hmcts-apim-sdlc-orchestrator context standards. Runs automatically on every session start via the SessionStart hook — invoke manually only to force an update. |
Automatic: The
SessionStarthook (hooks/bootstrap-context.sh) runs this logic automatically whenever Claude Code opens in anapi-cp-*orservice-cp-*repo. Run/bootstrap-contextmanually only to force-update.
Invoke this skill when a user asks to:
/bootstrap-context.claude/CLAUDE.mdInvocation command: /bootstrap-context
REPO_NAME=$(basename "$PWD")
echo "Repo: $REPO_NAME"
$REPO_NAME starts with api-cp- → API spec repo → use api-spec-shared.md$REPO_NAME starts with service-cp- → Service repo → use service-shared.mdapi-cp-* and service-cp-* repos. Current directory: $REPO_NAME.".claude/ directory if neededmkdir -p .claude
.claude/CLAUDE.mdWrite exactly 3 lines. Paths are relative from .claude/CLAUDE.md — ../../agentic-plugins-marketplace/ navigates up to the workspace root and into the marketplace repo. This works on any machine where repos are cloned as siblings.
For api-cp-* repos:
@../../agentic-plugins-marketplace/plugins/agents/hmcts-apim-sdlc-orchestrator/context/shared-code-rules.md
@../../agentic-plugins-marketplace/plugins/agents/hmcts-apim-sdlc-orchestrator/context/api-spec-shared.md
@../../agentic-plugins-marketplace/plugins/agents/hmcts-apim-sdlc-orchestrator/context/claude-md-standards.md
For service-cp-* repos:
@../../agentic-plugins-marketplace/plugins/agents/hmcts-apim-sdlc-orchestrator/context/shared-code-rules.md
@../../agentic-plugins-marketplace/plugins/agents/hmcts-apim-sdlc-orchestrator/context/service-shared.md
@../../agentic-plugins-marketplace/plugins/agents/hmcts-apim-sdlc-orchestrator/context/claude-md-standards.md
Claude Code automatically reads both CLAUDE.md (repo root, committed) and .claude/CLAUDE.md (gitignored) on every session. No explicit import of CLAUDE.md is needed — it is loaded natively.
.claude/CLAUDE.md is gitignoredCheck if .gitignore already contains .claude/CLAUDE.md:
grep -q "\.claude/CLAUDE\.md" .gitignore 2>/dev/null && echo "already ignored" || echo "missing"
.claude/CLAUDE.md to .gitignoreecho ".claude/CLAUDE.md" >> .gitignore
Note: .claude/settings.local.json and the root CLAUDE.md must remain committed — do not add .claude/ (the whole directory) to .gitignore, only .claude/CLAUDE.md.
Tell the user:
✓
.claude/CLAUDE.mdbootstrapped for<REPO_NAME>(gitignored).On every Claude Code session, Claude loads:
CLAUDE.md(this repo) — repo-specific context, committed herehmcts-apim-sdlc-orchestrator/context/shared-code-rules.md— team-wide code ruleshmcts-apim-sdlc-orchestrator/context/api-spec-shared.md(orservice-shared.md) — repo-category standardshmcts-apim-sdlc-orchestrator/context/claude-md-standards.md— HMCTS guidance for generatingCLAUDE.mdThis will also happen automatically on every future session start — the
SessionStarthook inhmcts-apim-sdlc-orchestratorcreates or verifies.claude/CLAUDE.mdbefore Claude reads any prompt.Next step: run
/initto generate (or refresh) the committedCLAUDE.mdfor this repo./initwill use the HMCTS standards now in context to produce a compliant, non-duplicating file.When shared standards change in
hmcts-apim-sdlc-orchestrator, this repo picks them up automatically — no further action needed.
.claude/CLAUDE.md — it is a local developer file; only gitignore it, never stage it..claude/settings.local.json — that file is separate and is committed.CLAUDE.md — that file is committed and owned by this repo; use /init to generate or refresh it..claude/CLAUDE.md — ../../agentic-plugins-marketplace/ navigates up to the workspace root. This works on any machine where repos are cloned as siblings under the same workspace root..claude/CLAUDE.md safely with the same content.