Pull Requests

​

PR Workflow

Task assigned → Agent builds in sandbox → Verification passes → Feature branch created → PR opened

​

What Each PR Contains

 # predev/dtc-913 → main · 631a912 · PR #1
 # feat(Setup): Write concise design aesthetic/rules
 # workspace/package.json (+251)

+ "private": true,
  "name": "mobile",
  "sideEffects": false,
  "scripts": {
+   "build": "react-router build",
    "clean": "node scripts/clean.js",
+   "dev": "react-router dev",
    "test": "vitest run",

• Feature branch — Named after the task (e.g., predev/setup-user-auth)
• Implementation code — All files created or modified for the task
• Tests — Unit tests covering the new functionality
• Diff summary — Clear view of what changed and why
• Verification status — All acceptance criteria results

​

Branch Strategy

​

Reviewing PRs

1. Check the diff — Verify the implementation matches what you expected
2. Review acceptance results — All automated checks should show PASSED
3. Test locally (optional) — Pull the branch and run it yourself
4. Merge or request changes — If something’s off, the agent can iterate

​

Merge Strategies

• Merge immediately — For tasks you’re confident about
• Batch merge — Let several PRs accumulate, review them together, merge in order
• Cherry-pick — Merge only specific PRs while skipping or reworking others

​

Code Quality

• Types compile cleanly
• Linting rules pass
• Tests pass
• UI renders correctly (for frontend tasks)

​

PR History

• Each PR maps to a specific task in the spec
• PRs are opened in milestone order
• The commit history tells the story of the project’s construction

​

What’s next?