Agents now must include QA steps in PR descriptions and verify them during code review.

Changes

Updated .github/copilot-instructions.md to add:

• Pull Request Guidelines section

  • Mandates clear "How to QA" instructions in every PR description
  • Provides format template and specific guidance for UI changes, API changes, bug fixes, and refactoring
  • Defines required context (issue link, change explanation, prerequisites, screenshots, state/data setup)
  • Includes guidance for achieving specific app state or data shape when needed

• Verify QA Steps (CRITICAL) in Code Review Guidelines

  • Requires checking for QA instructions before proceeding with review
  • Instructs agents to attempt running QA steps whenever possible
  • Mandates documenting QA verification results

• Highlight Areas Needing Attention enhancements

  • Added flagging of missing/incomplete QA steps
  • Added highlighting of unclear QA instructions

Format Example

## How to QA
1. Start the app: `dotrun`
2. Navigate to: [specific URL or path]
3. [Specific action to take]
4. Verify: [Expected outcome]
5. [Additional steps as needed]

Aligns with existing PR template which already includes "How to QA" section. Template uses dotrun directly as it includes necessary build steps.

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.