When creating Prisma database migrations, run from the repository root:
yarn dev:prisma:migrate:dev --name <migration_name>Do NOT use npx prisma migrate dev directly from packages/db.
To build a specific package:
yarn workspace @sourcebot/<package-name> buildUse Tailwind color classes directly instead of CSS variable syntax:
// Correct
className="border-border bg-card text-foreground text-muted-foreground bg-muted bg-secondary"
// Incorrect
className="border-[var(--border)] bg-[var(--card)] text-[var(--foreground)]"When creating a branch or opening a PR, ask the user for:
- The Linear issue ID (if available)
- The GitHub issue number (if available)
Branch naming convention:
- General:
<username>/<branch_name>-<linear_issue_id> - Bug fixes:
<username>/fix-<linear_issue_id> - If no Linear issue ID is available, omit it from the branch name
PR description:
- If a GitHub issue number was provided, include
Fixes #<github_issue_number>in the PR description
After the PR is created:
- Update CHANGELOG.md with an entry under
[Unreleased]linking to the new PR. New entries should be placed at the bottom of their section. - If the change touches
packages/mcp, updatepackages/mcp/CHANGELOG.mdinstead