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.
Use when running production incident triage for an on-call service and you need a repeatable, config-driven workflow that correlates ticket evidence, metrics, logs, releases, and code before writing back findings.
Inspect Oracle Ticketing Platform tickets and related resources from an OCI CLI session-backed profile. Use when Codex needs to fetch ticket details, comments, activity history, project metadata, TQL search results, dashboards, subQueries, linked tickets, attachment resources, post ticket comments to ticketing-platform.us-chicago-1.oci.oraclecloud.com, or mutate ticket labels.