PR Summary

What it is

/pr-summary is a slash command installed by waypoint init that generates a pull request description from Waypoint session history. Instead of boilerplate, it produces a description based on what actually happened — the intent, the decisions made, the approaches that didn't work, and the test outcomes.

Currently installed as a Claude Code slash command (.claude/commands/pr-summary.md). Any agent that supports custom slash commands or prompt files from this directory can use it directly; other agents can run waypoint pr-context manually and feed the output to the agent.

How to use it

Open your agent in the repo and type:

/pr-summary

Waypoint reads the session history for the current branch plus recent git context, then writes a PR description as markdown.

What it includes

The generated description covers:

• What was built or changed — drawn from user messages in recorded sessions
• Why — the intent and motivation, not just a list of diffs
• Key decisions — specific choices made during implementation
• What was tried but didn't work — failed approaches that reviewers should know about (this is often the most valuable part)
• Test commands run — commands executed during the session and their outcomes
• Files changed — organised from git context

How it works

/pr-summary runs waypoint pr-context internally, which emits the session history for the current branch. The agent then reads that history and writes the description — no extra API call, no separate model invocation.

You can customise the prompt template at .claude/commands/pr-summary.md to match your team's PR format.

Example output

## Summary

- Replaced the session token middleware with a JWT-based approach
- The previous implementation stored full session objects in Redis, which
  caused latency spikes under load
- Decision: 30-day token expiry, refresh on each authenticated request

## What was tried

- Attempted to use the existing `express-session` setup with a custom store —
  abandoned because it didn't support the multi-region deployment
- Tried `passport-jwt` before switching to `jose` directly for smaller bundle size

## Test commands

- `pnpm test auth` — 47 tests passing
- `curl` smoke tests against staging: login, refresh, and logout all working

## Files changed

- `lib/auth-edge.ts` — JWT verify/sign helpers (Edge-compatible)
- `lib/auth.ts` — server-side key verification
- `middleware.ts` — auth enforcement, session redirect logic
- `app/api/auth/login/route.ts` — login endpoint

Tips

• The more expressive your user messages during a session, the better the PR description. Saying "we're replacing Redis sessions because of latency issues" gives Waypoint more to work with than "fix auth".
• The description is a starting point — edit it before opening the PR. The goal is accurate first-draft, not perfect final-draft.
• If you work across multiple sessions on the same branch, Waypoint pulls history from all of them.