Menu
Draft and update PR/MR title and description from full branch scope; use before gh pr create or gh pr edit.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Expected shape of the planning phase output before code-implementer; aligns with write-implementation-plan.
Write or update project skills and rules markdown files (.ai/skills/, .ai/rules/, .cursor/rules/). Use when creating a new SKILL.md or rule, updating an existing one, or when the user asks to document a workflow, pattern, or convention as a reusable skill.
Guard architecture, style, and security in meta-secret core crate changes.
Guard architecture, style, and security in cli/meta-cli changes.
Guard architecture, style, and security in mobile/uniffi library changes.
Guard architecture, style, and security in web-cli/ui changes.
| name | workflow-mr-body |
| description | Draft and update PR/MR title and description from full branch scope; use before gh pr create or gh pr edit. |
Use with release-notes (draft) and release-manager (create/update PR). Keeps MR text consistent with SECURITY.md (no secrets in text).
The PR title and description must reflect the entire branch, not only the first commit or the original PR text.
Before writing or updating copy:
git log main..HEAD --oneline — all commits on the branchgit diff main...HEAD --stat — full diff vs basegh pr view --json title,body — current PR text (if a PR already exists)If new commits landed after the PR was opened, update title and body before asking the user to merge.
task … from build-via-taskAfter user approves title and body:
gh pr create --title "…" --body "$(cat <<'EOF'
…
EOF
)"
When a PR already exists and the branch has new themes or commits since the last description:
gh pr edit <number> --title "…" --body "$(cat <<'EOF'
…
EOF
)"
Also run when the user asks to update title and description of the PR, or before final merge if the body is stale.
Use PR number from gh pr view / branch tracking, or gh pr list --head "$(git branch --show-current)".
feature A + infra B)| Trigger | Action |
|---|---|
Stage 8 / /only-release-manager | Draft from full branch; create or gh pr edit |
| User: “update PR title/description” | Re-read diff + commits; gh pr edit |
| Significant push after PR open | Propose updated title/body; edit after user ok |
/only-release-notes | Draft only; release-manager applies via gh pr edit |