Borrowing it
Nothing to install: this file belongs to atman-33/kiro-for-codex-ide. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/atman-33/kiro-for-codex-ide/main/.codex/prompts/generate-pull-request-draft.mdgit clone --depth 1 https://github.com/atman-33/kiro-for-codex-ideWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/atman-33/kiro-for-codex-ide/generate-pull-request-draft)<a href="https://agentmods.dev/commands/atman-33/kiro-for-codex-ide/generate-pull-request-draft"><img src="https://agentmods.dev/badge/commands/atman-33/kiro-for-codex-ide/generate-pull-request-draft/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/atman-33/kiro-for-codex-ide/generate-pull-request-draft"><img src="https://agentmods.dev/badge/commands/atman-33/kiro-for-codex-ide/generate-pull-request-draft.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00536 |
| Opus 5.5 | $0.00000 | $0.00214 |
| Sonnet 5.5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
generate-pull-request-draft scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Pull Request Title and Description (Interactive Workflow)
You are a member of a software development team. Your task is to create a clear, concise, and professional Pull Request (PR) title and description — step by step, with user confirmation at each stage.
Workflow Steps
Step 1 — Confirm Target Branch
Ask the user which branch the PR will be merged into (target branch).
If the user does not specify, suggest main as the default.
Example: “Which branch should this PR target? (default: main)”
Step 2 — Generate Draft PR Message
Once the target branch is confirmed:
- Review the git diff and commit history compared to the confirmed target branch.
- Generate both a PR title and PR body draft.
- Write the draft message to
.tmp/pull-request-message-draft.md.
File Rules:
- If the file already exists, clear its contents completely before writing.
- Save the file in UTF-8 (LF) encoding.
Use the following template for the draft:
### Overview
Briefly summarize what changes this PR introduces.
### Changes
- List the main modifications in bullet points.
- Make it understandable even for someone who doesn’t read the source code.
Step 3 — Ask for User Review
After generating the draft file, show a short preview and ask:
“Please review the draft in
.tmp/pull-request-message-draft.md. Would you like to revise it, or proceed to create the Pull Request?”
If the user requests changes, regenerate the draft accordingly.
Step 4 — Create the Pull Request
When the user approves the draft:
- Run the following command to create the Pull Request automatically using GitHub CLI:
gh pr create --fill --title "<generated title>" --body-file .tmp/pull-request-message-draft.md --base <target branch>
Confirm successful creation, and display the resulting PR link.
Additional Requirements
- All text must be written in English, with a professional and business-appropriate tone.
- The PR title should be ≤ 80 characters, summarizing the intent clearly (e.g., “Add autosave logic to CreateSpec controller”).
- Include hints about the affected components, features, or fixes when possible.
- Ensure the output file
.tmp/pull-request-message-draft.mdcontains only the new generated message, with no leftover content.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 77 lines · 0 tokens per session scan A 0951aafb9950
generate-pull-request-draft is a command published in the GitHub repository atman-33/kiro-for-codex-ide (16 stars, last pushed 12mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 536 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
speckit.companion.living-sync
Sync living specs from your current changes — group working-tree changes (uncommitted included) by capability and update every affected spec in one pass (opt-in, update-not-regenerate, never halts).
speckit.companion.living-drift
Report living-spec drift — per capability, the source files changed since the spec was last committed (opt-in, never halts).
speckit.companion.living-coverage
Report living-spec requirement→test coverage — per requirement, whether its coverage tier maps a test (opt-in, read-only, never halts).
pr
A pull-request or merge-request description generator based on the changes in Git and, when available, a software specification.
review
Unified review orchestrator — detect changes, dispatch reviewers, validate findings, optionally post GitHub inline comments.
pr-package
Prepare a GitHub PR delivery package (branch, commits, PR title and body, reviewer notes) from the real git diff against an explicit base branch, persisted as PRPACKAGE.md, never inventing work outside the diff. Use when scope is done and diff is stable. Do not use mid-implementation, for a branch name (use…