# PR creation — template and command

Phase 3 of the PR workflow: push the branch and create a PR with a structured description. Load this when ready to open the PR.

## Required sections in the PR description

| Section | Required | Purpose |
|---------|----------|---------|
| Summary | Yes | What and why in 2-3 bullets |
| Feature Manifest | Yes | Link to manifest for traceability |
| Requirements Traceability | Yes | Which requirements this PR satisfies |
| Changes | Yes | Key files changed with brief description |
| Test Plan | Yes | How to verify the PR works |
| Checklist | Yes | Verification items |

## Creating the PR

```bash
# 1. Verify all tests pass
npm test

# 2. Push branch
git push -u origin <branch-name>

# 3. Create PR with structured description
gh pr create --title "<type>(scope): description" --body "$(cat <<'PREOF'
## Summary

- What this PR does (2-3 bullets)
- Why it is needed

## Feature Manifest

Links to: `.forge/work/{type}/{name}/manifest.yaml` (manifest), slice IDs from `slice_graph` (prototype-driven flow) OR REQ-IDs (non-prototype fallback flow).

## Requirements Traceability

- Implements: [REQ-001] User can create account
- Satisfies acceptance criteria: [AC-001.1], [AC-001.2]

## Changes

- `src/auth/service.ts` -- New authentication service
- `src/auth/middleware.ts` -- JWT validation middleware
- `tests/auth/` -- Unit and integration tests

## Test Plan

- [ ] Unit tests pass (`npm test`)
- [ ] Integration tests pass
- [ ] Manual verification: [describe steps]

## Checklist

- [ ] Tests written and passing
- [ ] No skipped tests
- [ ] API contract validated
- [ ] No secrets in code
- [ ] Conventional commit messages
PREOF
)"
```