// Commit and pull request conventions for divine-web. Load when creating commits, writing PR descriptions, or preparing branches for review.
Coding style and naming conventions for divine-web. Load when writing or editing TypeScript, React components, hooks, or styles.
Project structure and file organization for divine-web. Load when creating new files, moving code, or navigating the codebase.
Testing conventions for divine-web. Load when writing or modifying tests, or when verifying changes with Vitest or Playwright.
| name | pr-conventions |
| description | Commit and pull request conventions for divine-web. Load when creating commits, writing PR descriptions, or preparing branches for review. |
Use Conventional Commit format:
type(scope): summary
type: summary
Allowed types: feat, fix, docs, style, refactor, test, chore,
perf.
Set the correct title when opening the PR. Editing the title afterward may not
retrigger semantic_pr.yml, leaving the check stale or failed.
Fill out .github/pull_request_template.md completely. Every section:
One PR per concern. Do not bundle:
If you spot something worth fixing, file an issue and address it separately.
Do not mention corporate partners, customers, brands, campaign names, or other sensitive external identities in:
Use generic descriptors instead: "partner subdomain", "brand account", "external partner". Maintainer approval is required before naming any external entity.
Any temporary or transitional code must include a tracking reference:
// TODO(#123): remove after migration complete
No TODO without an issue number.
Before opening a PR:
origin/main.npm run test passes locally.git status (no unstaged or untracked files).Stop exploratory UI work if maintainer alignment on scope or UX is missing. Do not continue speculative feature implementation past the point of uncertainty. Open a discussion or draft PR to align before proceeding.