sqlew-pr-adr

REQUIRED: Enrich PRs with Decision Context

When creating a pull request, reviewers need WHY context, not just what changed. MUST query sqlew for decisions related to the actual code changes and group the PR description by decision.

---

Step 1: Get the Diff

# Get changed files and content vs base branch
git diff <base-branch>...HEAD --stat    # File list
git diff <base-branch>...HEAD           # Full diff

Extract keywords from the diff:

• File paths: directory names, module names (e.g., auth, migration, database)
• Function/struct names: key identifiers added or modified
• Package/import changes: new dependencies or module references

---

Step 2: Reverse-Lookup Decisions via Suggest

For each extracted keyword, query sqlew to find related decisions:

suggest { action: "by_context", key: "<keyword>" }
suggest { action: "by_context", key: "<module-name>", tags: ["<relevant-tag>"] }

For each matched decision key, fetch full context:

decision { action: "get", key: "<matched-key>", include_context: true }

This retrieves: Rationale, Alternatives Considered, Tradeoffs.

Selection rules:

• Include decisions with score >= 35 from suggest results
• Deduplicate across keyword searches
• Cap at 5 decisions (keep PR readable)
• Skip deprecated decisions

---

Step 3: Group Files Under Decisions

Organize the PR body so each decision/constraint lists its related files directly.

REQUIRED markers (hook-enforced): The sqlew pr-adr PreToolUse hook blocks gh pr create unless the body contains the literal heading ## Architecture Decisions or ## Other Changes. Put every decision/constraint under ## Architecture Decisions as ### subsections, and unattributed changes under ## Other Changes. A PR whose changes are all tied to ADRs still needs the ## Architecture Decisions heading present.

## Summary

<!-- 1-3 bullet points: what this PR does overall -->

## Architecture Decisions

### Decision: <title> (<reason>)

- `path/to/file1.ts`: what changed and why
- `path/to/file2.ts`: what changed and why

### Decision: <another title> (<reason>)

- `path/to/file3.ts`: what changed and why

### Constraint: <rule description>

- `path/to/file4.ts`: what changed to comply

## Other Changes

<!-- Changes not tied to any Decision/Constraint -->
- `path/to/file5.ts`: minor cleanup

## Test Plan

- [ ] Test step 1
- [ ] Test step 2