Creating Pull Requests

Validate readiness:

git branch --show-current
git status
git branch -r | grep $(git branch --show-current)

Confirm with user, then proceed to Step 3.

Mode B: Automated

Assumes user has already staged changes with git add.

git status
git checkout develop
git checkout -b {type}/{descriptive-name}
git commit -m "{imperative-verb} {what} {where}"
git push --set-upstream origin $(git branch --show-current)

Branch naming: {type}/{brief-description} in kebab-case. Types: feature, fix, refactor, chore, docs. Examples: feature/add-height-plotly-charts, fix/dataframe-memory-leak-scrolling.

Commit message: <imperative verb> <what> <where>, ≤50 chars, no period. Examples: Add height parameter to plotly charts, Fix memory leak in dataframe scrolling.

Step 3: Compose and create PR

3.1 Determine labels

All PRs require these labels:

Note: PRs labeled change:spec (for spec/design documents only) are exempt from the impact:* requirement. Do not use change:spec for PRs with code changes.

3.2 Generate PR title

Format: [type] Description of change, ≤63 chars (fits squash-merge commit subjects).

Examples: [feature] Add height parameter to plotly charts, [fix] Extra padding on button.

3.3 Compose PR description

Read .github/pull_request_template.md for the required sections, then fill them in.

Writing rules:

• Highlight what matters. Omit the obvious.
• 2-4 bullets maximum for listing changes.
• No meta-commentary ("This PR...", "We have...", "I added..."). State what changed directly.
• Don't list: added tests, updated types, added validation, fixed linting (all obvious).
• DO explain non-obvious decisions (deprecations, unit choices, fallback behavior).

Good:

Adds height parameter to st.plotly_chart() using Height type system.

• Deprecates use_container_height (removed after 2025-12-31)

Bad (lists every change):

• Added height parameter to signature
• Updated layout config dataclass
• Added validation for height values
• Added unit tests

Testing section — detect from changed files:

Check the matching boxes in the PR template. If no test files changed, explain why. Leave "manual testing" unchecked (user fills in).

3.4 Write PR for user review

Write complete PR details to work-tmp/pr_description.md:

---