git:20260610.93494b8 to git:20260718.85ce762

27 added, 100 removed. Audit A to A.

---

name: pr-create

- description: Use when creating or updating a Basic Memory pull request from Codex with BM Bossbot merge-gate monitoring.

+ description: Use when explicitly creating or updating a Basic Memory pull request. This compatibility entry point delegates the full workflow to pull-request and the latest-head Codex gate to pr-review-loop.

---

# Create A Basic Memory PR

- Create or update a pull request for the current branch, then wait for BM

- Bossbot to approve the latest head SHA. This skill never merges a PR.

- ## Inputs

- - Optional `<theme>`: free-form visual direction for the non-gating PR

- image. Example: `$pr-create "Italian movie poster"`.

- - Treat `<theme>` as style guidance only. It must not affect PR readiness,

- BM Bossbot review, status checks, or merge behavior.

- ## How To Use

- Ask Codex to use the skill from a feature branch:

- ```text

- $pr-create

- $pr-create "Italian movie poster"

- $pr-create "80's action movies"

- ```

- Use the plain form when you only want the PR workflow. Pass a theme when you

- want the non-gating image to lean toward a particular visual direction. The

- theme can be specific ("Rembrandt-inspired approval scene") or broad ("let the

- model choose from BM categories").

- ## What Happens

- 1. Codex checks the branch, local verification, GitHub auth, commit sign-offs,

- and semantic PR title shape.

- 2. Codex pushes the branch, creates or reuses the PR, and adds the optional

- `BM_INFOGRAPHIC_THEME` block when a theme was supplied.

- 3. BM Bossbot runs from trusted base code, reviews sanitized PR metadata and

- diff context, and sets the required `BM Bossbot Approval` status for the

- exact head SHA.

- 4. If approval succeeds, BM Bossbot may publish a non-gating image block and a

- provenance block:

- ```markdown

-

- ...

-

- ```

- The provenance records the image mode, theme source, selected visual

- direction, and image settings. It is for review/debugging context only.

- 5. Codex reports the PR URL, head SHA, checks watched, verification run, and BM

- Bossbot verdict.

- The skill never merges, never enables auto-merge, and never treats the image or

- provenance block as a gate. The only required merge signal is the

- `BM Bossbot Approval` status on the current PR head SHA.

- ## Preflight

- 1. Confirm the repo and branch:

- - `git status --short --branch`

- - stop if detached or on `main`

- - keep unrelated user changes intact

- 2. Confirm GitHub access:

- - `gh auth status`

- - `gh repo view --json nameWithOwner,defaultBranchRef,url`

- 3. Check PR readiness:

- - commits are signed off with `git commit -s`

- - title uses the repo semantic format

- - local verification appropriate to the change has run

- ## Create Or Reuse

- 1. Push the branch:

- - `git push -u origin HEAD`

- 2. Check for an existing PR:

- - `gh pr view --json number,url,headRefOid,mergeStateStatus,statusCheckRollup`

- 3. If no PR exists, create one:

- - `gh pr create --fill`

- - adjust the title if it does not satisfy the semantic PR title workflow

- 4. If `<theme>` is provided, add or update this managed block in the PR body:

+ Create or update a pull request by applying `pull-request` in full. Use

+ `pr-description` for the body and enter `pr-review-loop` as soon as the PR is

+ open or materially updated. This skill never merges a PR.

- ```markdown

-

- <theme>

-

- ```

+ ## Compatibility

- Keep the rest of the PR body intact. The theme is non-gating image guidance

- only.

+ `$pr-create` remains available for existing prompts, but its former BM Bossbot

+ and automatic PR-infographic workflow has been retired. Do not wait for the

+ deleted `BM Bossbot Approval` status or `.github/workflows/bm-bossbot.yml`.

- 5. Do not merge. Do not enable auto-merge.

+ If a legacy `$pr-create "<theme>"` prompt includes an image theme, do not add

+ the retired managed theme or provenance blocks. Explain that the automatic PR

+ image path is no longer part of this workflow.

- ## Watch The Gate

+ ## Workflow

- 1. Trigger or wait for `.github/workflows/bm-bossbot.yml`.

- 2. Watch the required commit status named `BM Bossbot Approval`.

- 3. Treat approval as valid only when it is green for the current `headRefOid`.

- 4. If the branch changes after approval, wait for BM Bossbot to review the new

- head SHA.

- 5. If BM Bossbot fails or requests changes, use `$fix-pr-issues`.

+ 1. Read and follow `pull-request` for branch hygiene, validation, pushing, and

+ PR creation or reuse.

+ 2. Read and follow `pr-description` when creating or materially updating the

+ PR body.

+ 3. Confirm commits are signed off, the title follows the repository's semantic

+ PR-title format, and the validation appropriate to the changed surface has

+ passed.

+ 4. Push the branch and create or reuse the PR. Do not enable auto-merge.

+ 5. Read and follow `pr-review-loop` on the latest head SHA. Green CI alone is

+ not approval.

+ 6. If Codex or CI reports a blocker, use `fix-pr-issues`, push the fix, and

+ restart `pr-review-loop` for the new head.

## Report

- Return the PR URL, current head SHA, checks watched, verification run, and the

- BM Bossbot verdict. Include the image `<theme>` if one was supplied. Be

- explicit when any check is still pending.

+ Return the PR URL, current head SHA, validation run, check status, and Codex

+ gate evidence. Report pending or blocking state explicitly. Do not merge unless

+ the user separately requests it and the current-head gate permits it.