pr-package

pr-package

Act as a senior engineer preparing a full delivery package for the active engineering task based on the real git diff.

Goal: Prepare a clean delivery package for GitHub using the actual implementation changes in the current branch compared against an explicit integration base branch, then persist the result in the task repository.

Mandatory context bootstrap (before any output):

• Read these sections in WORKFLOW_OPERATING_SYSTEM.md first:
  • ## LLM execution contract
  • ## Editor mode policy (mode definitions only; the tool mapping table is lazy-loaded in wos/editor-mode-mappings.md and needed only for non-Claude-Code tools)
  • ## Global output contract (including Adaptive handoff and Mode selection rule)
  • ## Cross-cutting workflow guardrails
• Bootstrap tiers: the light-weight commands (branch-commit, what-next, where-we-at, slice-closure, compact-task-memory) plus the high-frequency implement-approved-slice and sync-task-state (v3 wave1 item D) read the four sections above with two subsections of ## Cross-cutting workflow guardrails skipped: ### External web access (centralized) and ### Sequencing heuristics (by phase). Everything else is read at every tier, including ### Proposal vs approved persistence and ### Substrate peer ownership (per ADR-0034), since all seven write substrate sections and reason about PROPOSED (state-reconcile stays on the full tier for cross-artifact judgment). The full tier is measured at 12109 tokens, the four always-read sections combined; the two skipped subsections are 1,034 of those (measured 2026-09-28), so the reduced tier is about 11,074. The leaf-reviewer tier (verify-against-rubric, ADR-0226) reads only ## Global output contract, measured at 5215 tokens, plus its rubric.
• Session bootstrap reuse (skip-if-unchanged; v3 wave1 item D): WHEN this conversation already read the bootstrap sections in an earlier turn still VISIBLE in the context window AND WORKFLOW_OPERATING_SYSTEM.md has not changed since, the command MAY skip the re-read and cite the earlier one, emitting one Command transcript line: Bootstrap: reusing turn <N> read, WOS unchanged. Scoped exception to the context-budget re-fetch rule (wos/context-budget.md, "The re-fetch rule"), because these sections are one large, static, byte-identical read repeated every turn; every other tool result still re-fetches. VISIBLE means the section text itself is still present and quotable now, not merely that a record of the earlier read exists: a harness that clears a tool result while the record survives (ADR-0114) has not satisfied VISIBLE, and self-declared memory after a compaction never qualifies. A stateless-per-turn harness is excluded. The transcript line is mandatory; a silent skip is invalid output.
• Resolving the spec and wos/<topic>.md: canonical repository FIRST. Otherwise use active-adapter docs: ~/.claude/workflow-docs (CLAUDE_WORKFLOW_DOCS_DIR), ~/.cursor/workflow-docs (WORKFLOW_DOCS_DIR; project .cursor/workflow-docs on project installs), ~/.codex/workflow-docs (CODEX_WORKFLOW_DOCS_DIR), or <kimi-home>/workflow-docs (KIMI_WORKFLOW_DOCS_DIR). Nonempty overrides win. Kimi home: KIMI_CODE_HOME, else existing ~/.kimi-code, else existing ~/.kimi, default ~/.kimi-code. Use one root for both paths; try other adapters if absent or unknown. Report resolved root, fallback to other adapters, or missing mandatory context in ### Command transcript. Installed snapshots refresh and prune retired topics only on sync.
• Read additional sections only when relevant to this command's role.
• Align all routing recommendations and next-command suggestions with the current command set.
• Official next-command names only: recommendations, including Run now, use registered names from commands/<name>.md or commands/<name>/SKILL.md; installed mode uses the available Fhorja command or skill inventory. No invented aliases. Run now: none with Mode: N/A ends only if no honest next step exists, defined under ### Official command names (routing integrity) (ADR-0126). Required inputs:
• active task folder path
• TASK_STATE.md
• DECISIONS.md
• IMPLEMENTATION_PLAN.md
• target repo (only for multi-repo tasks where SOURCE_OF_TRUTH.md has a ## Repositories section): the repo identifier this invocation packages. Must match one entry in the ## Repositories section. Multi-repo tasks invoke pr-package once per repo, with one invocation producing one repo's PR. See the spec ## Multi-repo support (v1) for the schema.
• explicit git base branch to compare against (example: origin/main, origin/staging, or a named remote branch). WHEN an attended chain on a task branch reached this command from branch-commit --apply and no base was given, use the Base branch: line in TASK_STATE.md ## Resume notes (the branch the task branch was cut from), else the base recorded in SOURCE_OF_TRUTH.md (or TASK_PREFERENCES.md), else origin/HEAD, and cite which one supplied it instead of asking (ADR-0233). For multi-repo tasks, this is the base branch for the target repo (which may differ across repos and is recorded per-repo in ## Repositories).
• current local branch name (as shown by git branch --show-current)
• working tree context (as shown by git status --porcelain or an explicit statement that the working tree is clean)
• explicit diff commands used (at minimum):
  • git fetch <remote> <base> (run first; the diff is taken against the freshly fetched ref, never a stale local one)
  • git diff <base>...HEAD
  • optional: git diff --stat <base>...HEAD
  • git status --porcelain plus git diff and git diff --staged WHEN the committed diff is empty. Uncommitted work in the working tree is still the change under delivery: package it and say plainly that it is uncommitted, so the branch-and-commit steps come before the push step. An empty <base>...HEAD is NOT proof there is nothing to deliver, and reporting a healthy package over an empty diff is the silent-empty-scope failure this line exists to prevent.
• real git diff vs the explicit base branch, or the working-tree diff when the branch carries no commits yet
• latest validation/test evidence if available
• last completed step from TASK_STATE.md (command + summary)