菜单
Use when maintaining OCM engineering workflows across multiple repos or services and you need the canonical OCM runbooks, shepherd/release anchors, prerequisites context, or TC handoff guidance.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Read, create, update, inspect, and reply to Bitbucket pull requests or commit diffs using Bitbucket URLs plus environment-backed auth. Use when Codex needs Bitbucket API operations for PR metadata, compare or commit evidence, PR discussion threads, PR creation/update, reviewer preservation, or prefixed replies. This skill does not perform full code-change review or own code remediation.
Review change-management tickets such as Jira CHANGE or CM requests for deployment readiness, scope drift, documentation quality, and runbook adherence. Use when Codex needs to assess implementation steps, validation evidence, rollback clarity, Shepherd release scope and plan diffs, regional outliers, manual data-fix or host-maintenance procedures, team-specific runbook alignment, and commit or artifact-version alignment, and optionally write findings back to the ticket.
Bootstrap a local Codex setup from this shared starter repo. Use when an engineer needs an interactive onboarding flow that asks for local paths, required MCP settings, and only the overrides that differ from the shared Enterprise ChatGPT defaults, then generates or repairs a real local Codex config and verifies that shared path placeholders were resolved.
Use when onboarding OCI users to available packs, registry entries, PromptLib spaces, ORA skills, Skills Hub / AI Skills Registry, Codex Enterprise apps/connectors, or non-pack content sources after installing OCI starter packs.
Inspect DevOps MFO or region-build flock dependency status for a specific region, project, flock, and phonebookId. Use when Codex needs to determine which region-build phases are satisfied, unsatisfied, or optional; identify whether a flock has published the required capabilities; recursively trace missing capability producers; discover related infrastructure or application flocks from the dependency graph; or explain which upstream project or flock is blocking publication.
Preflights local ossh and oci-ops access, reads a Jira ticket to identify a target hostname and region, validates OCI authentication, resolves the tenancy OCID, and returns the appropriate oci-ops SSH connection command. Use when a user asks to SSH to an OCI host from a Jira ticket, set up ossh or oci-ops access, resolve a host region or tenancy, or needs an oci-ops SSH command.
| name | ocm-dev |
| description | Use when maintaining OCM engineering workflows across multiple repos or services and you need the canonical OCM runbooks, shepherd/release anchors, prerequisites context, or TC handoff guidance. |
| metadata | {"owner":"ocm","last_updated":"2026-03-09T00:00:00.000Z","audience":"maintainers","workflow":"ocm, release, shepherd, docs"} |
AGENTS.md and local docs first.aipack-system skill or the oracle/mcp repo.AGENTS.md (or equivalent rules discovery) and it contains the repo-specific commands/versions you should follow.aipack doctor and ensure it exits 0.AGENTS.md / README; re-derive the answer from repo-local commands and validation steps.INDEX.md — consolidated routing table (workflows, Confluence anchors, repos, developer phases)ai/ — OCM AI practice, MCP governance, Migration Assistant playbooknorth-star.md — OCM North Star 2026 roadmap (streams, phases, metrics)release-terms.md — release/deployment glossary (15 terms)scripts.md — oracle-quickstart script inventory (classified by mutability)safety-rubric.md — script safety classification + preflight checklistcm-operations.md — manual CM creation/validation (CHANGE project field mappings, process, location alignment)ocm-shepherd: {env:HOME}/src/bb/ocicm/ocm-shepherdocm-runbooks: {env:HOME}/src/bb/ocicm/ocm-runbooksocm-ops-tools: {env:HOME}/src/bb/ocicm/ocm-ops-toolsocm-onboarding: {env:HOME}/src/bb/ocicm/ocm-onboardingAGENTS.md.