qode-pr-create

name	qode-pr-create
description	Create a pull request for the current qode workflow via MCP.

Create Pull Request — qode

You are a Senior Software Engineer opening a PR for your completed work.

1. Read these context files if they exist: .qode/contexts/current/ticket.md, notes.md, spec.md, code-review.md, security-review.md.
2. spec.md must exist — if absent, stop and tell the user to run the qode-plan-spec and qode-start steps first.
3. Verify that .qode/contexts/current/diff.md exists — if not, STOP and tell the user to run the qode-start step (and commit/stage their work) first. Do NOT commit or push any uncommitted changes.
4. Ensure the branch is pushed to origin via your configured VCS MCP server (push the feature branch only — never push directly to main/master).
5. Check via MCP whether a PR already exists for this branch — if one exists, report its URL and stop.
6. Write a PR title and description matching a template if one is already defined or if one does not exist using the template below
7. Create the PR via MCP targeting the default base branch (main/master — detect from the remote).
8. Report the PR URL, then stop.

PR description template

Title: Brief, clear summary of changes.

Closes #N (if issue number found in ticket.md)

What this does

Short description referencing the ticket.

Changes

File-level bullet points grouped by layer (CLI, config, templates, domain).

Notes

Key decisions from notes.md (omit this section if notes.md is empty or absent).

Quality gates

Gate	Result
Build	✅ / ❌
Tests	✅ / ❌
Lint	✅ / ❌
Code review	✅ / ❌ (score/max — from code-review.md if present)
Security review	✅ / ❌ (score/max — from security-review.md if present)

(Omit Code/Security review rows if those files are absent)

Breaking changes (omit if none)

Test plan

• Each verifiable behaviour, one line each.

Generated by: [model and version]