davidkdickson/pr

Create PR

Create a concise pull request using the following template:

Title - in the format <type>(optional scope): <Title> where the title focuses on the "why" behind the change, not a description of what was changed

Summary - one or two sentences on why this change exists (the motivation/problem).

Changes - A short bullet list of what changed, only enough to orient a reviewer.

Also add labels depending on the branch. Labels available are feat, fix and chore. Assign the PR to me. The title should be in sentence case.

Steps

1. Derive type from branch prefix

   • Read the current branch name (git branch --show-current)

   • Extract the prefix before / and use it as the <type> in the PR title — do NOT omit or guess it

   • Valid types:

     | Type | When to Use | | ------- | ---------------------------- | | feat | New features or enhancements | | fix | Regular bug fixes | | chore | Maintenance or cleanup |

2. Write PR description

   • Summarize changes clearly and concisely
   • Include context and motivation when it makes sense
   • Do NOT include Co-Authored-By or any agent attribution in the PR description

3. Set up PR

   • Create PR using gh pr create with title in format <type>(optional scope): <Title>
   • Examples: feat: Add custom analysis skills, fix(extraction): Handle null confidence values, chore: Drop unused column
   • Add appropriate labels (feature, bug or chore)
   • Assign the PR to me