| name | eweser-create-pr |
| description | Use this skill to create a GitHub pull request for completed EweserDB work. Summarizes commits since main, writes a clear title and body, and opens the PR. Use after QA has passed.
|
Role: EweserDB Create PR
You create a GitHub pull request summarizing completed work on the EweserDB monorepo.
Before opening the PR
- Confirm QA has passed.
- Ensure the working tree state is understood with
git status.
- Confirm with the user before pushing or publishing a branch unless they already asked for PR creation.
Workflow
git --no-pager log --oneline main..HEAD
- Summarize commits since
main.
- Read the relevant plan file from
docs/ai/plans/.
- Open a PR against
main using the available GitHub workflow.
PR body template
## What
<One-paragraph summary of the feature/fix>
## Changes
- `packages/...` - <what changed>
- `packages/...` - <what changed>
## Review Evidence
- Screenshots: <links/paths for UI-visible changes, or Not applicable>
- Visual assessment: <pass/fail notes from inspecting UI screenshots>
- Diagrams: <Mermaid diagram or Not applicable>
## Testing
- [ ] Unit tests pass (`npm test`)
- [ ] Types clean (`npm run type-check` or relevant equivalent)
- [ ] Build succeeds (`npm run build`)
## Checklist
- [ ] Changeset added if a published package API changed
- [ ] No secrets committed
- [ ] No direct Yjs mutations introduced
- [ ] Database migrations added, not modified, if schema changed
- [ ] UI-visible changes include screenshots, or the PR explains why not
- [ ] UI screenshots have been inspected for spacing, alignment, balance, wrapping, overflow, density, and responsive fit
- [ ] Backend/data-flow changes include a concise diagram, or the PR explains why not
Rules
- Base branch is always
main.
- Draft the PR if any checklist item is unresolved.
- Never push directly to
main.
