expo-docs-prlisted

# Expo Docs PR Description ## Default length: terse Always default to the shortest credible description. Aman almost always wants "short / tiny / concise" output; treat that as the baseline rather than a modifier the user has to add. Expand beyond the terse defaults only when ONE of these holds: - The PR touches 5+ unrelated areas. - The user explicitly says "longer", "detailed", "with context", or asks follow-up questions. - The diff genuinely needs context a reviewer cannot infer from the title. If Why + How + Test Plan together exceed ~6 sentences, cut. ## Short mode (`--short`) When the user passes `--short` or asks for the "short version", output only the `# How` section and nothing else. Skip the title, Why, Test Plan, and Checklist. ## PR Title Format ``` [docs] Short description of the change ``` - Always prefix with `[docs]` - Keep it under 70 characters - Use imperative mood (e.g., "Fix", "Add", "Remove", "Update") ## PR Description Format The description must use these exact sections in this order, each as an H1 (`#`): ### Why Default: 1 sentence stating the motivation. Add a second sentence only when the problem cannot be understood without it (e.g., quoting an error message or linking an issue). Do not restate the solution. ### How Default: 1-2 sentences in prose describing the technical approach. Use inline code formatting for file names, function names, and config values. Keep it as one paragraph with no bullet lists, unless the PR spans 3+ unre