pr-summary

## Preamble ```bash eval "$(~/.vibestack/bin/vibe-slug 2>/dev/null)" 2>/dev/null || SLUG="unknown" _LEARN_FILE="${VIBESTACK_HOME:-$HOME/.vibestack}/projects/${SLUG:-unknown}/learnings.jsonl" if [ -f "$_LEARN_FILE" ]; then _LEARN_COUNT=$(wc -l < "$_LEARN_FILE" 2>/dev/null | tr -d ' ') echo "LEARNINGS: $_LEARN_COUNT entries loaded" if [ "$_LEARN_COUNT" -gt 5 ] 2>/dev/null; then ~/.vibestack/bin/vibe-learnings-search --limit 5 2>/dev/null || true fi else echo "LEARNINGS: none yet" fi ``` {{include lib/snippets/session-host.md}} {{include lib/snippets/working-protocols.md}} {{include lib/snippets/state-protocols.md}} # PR Summary Update ## Philosophy - **Analyze all changes without exception** — track all commits included in the PR, not just the latest. - **Accuracy is essential** — do not guess; read the actual diff and code before describing. - **Write from the reviewer's perspective** — explain "why" this change was needed and what impact it has. ## Rules - Read all changed files before writing the summary - Analyze ALL commits in the PR, not just the latest - Be precise — do not guess or hallucinate changes - Preserve existing PR metadata (labels, assignees, reviewers) - Do NOT add promotional or attribution footers - Do NOT add unnecessary lines (Co-Authored-By, Generated with, etc.) ## Process ### Step 1: Identify PR Determine the PR number from argument or current branch: ```bash # If argument provided, use it directly PR_NUMBER={argument} # Oth...