specclaw pr

specclaw pr

First, run specclaw-ensure-init .specclaw — idempotently creates .specclaw/ if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name).

Create a GitHub PR for a verified change. Requires verify-report.md (build + verify must complete first).

1. Code review block (conditional): Read workflow.code_review_block from .specclaw/config.yaml. If true:
   • Check if .specclaw/changes/<change>/review-report.md exists. If it does not exist, warn: "code_review_block is enabled but no review-report.md found — run /specclaw:verify first" and continue.
   • If review-report.md exists and verdict is CHANGES_REQUESTED, abort with: "PR blocked: code review verdict is CHANGES_REQUESTED. Fix BLOCK findings in review-report.md then re-run /specclaw:verify." List all BLOCK findings from the report before aborting.
2. Validate: specclaw-validate-change .specclaw <change> pr. Exits with a warning (exit 0) if a PR already exists for this change. Fails if verify-report.md is missing.
3. Run: specclaw-pr .specclaw <change> — always create the PR through this script, never hand-roll gh pr create. specclaw-pr stages and commits the full .specclaw/changes/<change>/ planning trail (proposal, spec, design, tasks, status, verify-report) into the branch and aborts if any of it is left uncommitted — a raw gh pr create skips this and ships a PR missing the proposal artifacts.
   • First run: prompts for test policy (none|unit|e2e|both), saves it to config.yaml under pr.test_policy. Never prompts again.
   • Test enforcement: if policy is not none, verifies build.test_command is set and that verify-report.md contains test evidence. Fails (strict) or warns (non-strict) if evidence is missing.
   • Version bump: if plugin.version_files is set in config.yaml, compares each file's "version" against the base branch. If unchanged, auto-bumps the patch version and commits before PR creation. Configure in .specclaw/config.yaml:

     plugin:
       version_files:
         - "plugins/specclaw/.claude-plugin/plugin.json"
         - ".claude-plugin/marketplace.json"
     

   • PR creation: builds title from proposal.md, body from spec.md + verify-report.md, runs gh pr create --base main.
   • GitHub sync: if github.sync: true, includes Closes #N in the PR body.
   • Saves URL: appends **PR:** <url> to status.md.
4. Update project context: After the PR URL is saved, rewrite .specclaw/context.md to incorporate decisions from this change:
   • Run specclaw-update-context .specclaw <change> — this outputs an LLM prompt.
   • Feed the prompt to a coding agent that rewrites context.md in place (architecture-doc style: replaces stale info, merges new decisions).
   • If context.md changed, commit it: git add .specclaw/context.md && git commit -m "docs(context): update project context after <change>" and push.
   • Errors here are non-blocking — warn and continue.
5. Report the PR URL to the user.

CI outer loop (if loop.ci_gate: true): once the PR branch is pushed, the CI tier of /specclaw:loop (Step 3 / specclaw-loop ci-poll) polls GitHub Actions checks and iterates fixes until they are green, or loop.ci_max_iterations / loop.ci_timeout_seconds halts and escalates. This is a cross-reference only — PR creation above is unchanged, and nothing extra runs when loop.ci_gate is false.