​
Overview

Blink follows your conventions: branches like blink/{feature}, draft PRs by default, Prettier before commit, and co-author credit. Use Blink to keep PRs small, focused, and responsive to review.

​
Workflow

  1. Open a draft PR with a clear, scannable description
  2. Tag reviewers and call out risks, screenshots, and test notes
  3. Address feedback promptly; prefer follow-up PRs for non-blockers
  4. Keep CI green; Blink can fix lint/tests on request

​
Prompt Templates

Open a PR:
- Branch name: blink/profile-avatar-upload
- Title: feat(profile): allow avatar upload with optimistic update
- Description: problem, approach, screenshots, test plan, risks
- Reviewers: @team-frontend; Labels: feature, web

Respond to review:
- Apply requested changes from PR #123 comments
- Update tests and docs accordingly
- Re-request review when CI is green

​
Anti‑Patterns and Recovery

  • Mega-PRs: split into smaller stacked PRs
  • Vague descriptions: include problem, approach, and test plan
  • Drifting scope: follow up with separate PRs for refactors
  • Prettier run before committing
  • Draft PRs with links and co-author credit
  • Iterations until checks pass and reviewers approve