qa-pr
Skill8 starsChanged 5 months agoMITView on GitHub
Automated QA testing for Prose PRs using Circuit Electron. Use when testing pull requests before merge.
In this repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accelerateSkill
- implement-issueSkill
- pipeline-engSkill
- pipeline-orchestrateSkill
- pipeline-peSkill
- pipeline-scorerSkill
- qa-acceleratedSkill
- qa-webSkill
- releaseSkill
- review-feedbackSkill
- roadmap-prioritizationSkill
- roadmap-refinementSkill
- security-auditSkill
- accelerateSkill
- implement-issueSkill
- pipeline-engSkill
- pipeline-orchestrateSkill
- pipeline-peSkill
- pipeline-scorerSkill
- qa-acceleratedSkill
- qa-hitlSkill
- qa-prSkill
- qa-webSkill
- releaseSkill
- review-feedbackSkill
- roadmap-prioritizationSkill
- roadmap-refinementSkill
- screenshotsSkill
- security-auditSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 10 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Use the GitHub MCP to get PR information:
- Distinctive: line 32
Look for a comment containing "## QA Instructions" or similar test plan.
- Distinctive: line 36
CRITICAL: Always checkout the PR branch before testing to ensure you're testing the correct code:
- Very specific: line 67
Note: Use includeSnapshots: false to avoid snapshot-related errors with keyboard tools.
- Distinctive: line 131
Create test state (content, settings, etc.)
- Distinctive: line 136
Wait for user confirmation: "Let me know when done"
- Very specific: line 139
Use text_content to check result
- Distinctive: line 161
When testing app restart persistence:
- Distinctive: line 163
Ask user to close app if needed: "Close the app with Cmd+Q"
- Distinctive: line 169
Use GitHub MCP to comment:
- Very specific: line 226
Snapshot errors: Use includeSnapshots: false when launching, use evaluate with text_content instead of snapshot
- Very specific: line 228
Click not working: Use evaluate to click via JavaScript
- Very specific: line 238
Synthetic JS KeyboardEvents: don't trigger React's event handlers properly - metaKey is often stripped
- Distinctive: line 245
Always wait for content to save before closing (brief pause or verify via evaluate)
- Distinctive: line 248
Stale preload scripts: Always kill existing electron/vite processes and checkout the correct branch before testing
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
QA Pull Request
Automated QA testing for Prose PRs using Circuit Electron.
Usage
/qa-pr <pr-number>Workflow
1. Fetch PR Details
Use the GitHub MCP to get PR information:
mcp__github__pull_request_read (method: "get", owner: "solo-ist", repo: "prose", pullNumber: <pr-number>)Then fetch comments to find QA instructions:
mcp__github__pull_request_read (method: "get_comments", owner: "solo-ist", repo: "prose", pullNumber: <pr-number>)Look for a comment containing "## QA Instructions" or similar test plan.
2. Checkout PR Branch
CRITICAL: Always checkout the PR branch before testing to ensure you're testing the correct code:
git fetch origin <branch-name>
git checkout <branch-name>The branch name is in the PR details under head.ref.
3. Fresh Build (Kill Stale Processes)
CRITICAL: Kill any existing Electron/Vite processes to ensure a fresh build. Stale processes can use cached preload scripts and miss PR changes:
pkill -f "electron" 2>/dev/null
pkill -f "vite" 2>/dev/nullThis is especially important when:
- Testing changes to preload scripts (
src/preload/) - Testing changes to main process (
src/main/) - Switching between PR branches
4. Launch with Circuit Electron
Launch in development mode (rebuilds all code fresh):
mcp__circuit-electron__app_launch (app: "/Users/angelmarino/Code/prose", mode: "development", startScript: "dev", includeSnapshots: false)Note: Use includeSnapshots: false to avoid snapshot-related errors with keyboard tools.
Save the returned sessionId for subsequent commands.
5. Execute Test Scenarios
For each test in the QA instructions:
- Use
evaluatefor DOM interactions (more reliable than click/type):mcp__circuit-electron__evaluate (sessionId: <id>, script: "...") - Use
text_contentto verify state:mcp__circuit-electron__text_content (sessionId: <id>) - Use
closeandapp_launchto test persistence across app restarts
Common Patterns
Click a button by aria-label:
const btn = document.querySelector('[aria-label="Button Name"]');
btn?.click();Click a button by text:
const btn = Array.from(document.querySelectorAll('button')).find(b => b.innerText === 'Text');
btn?.click();Get editor content:
document.querySelector('.ProseMirror')?.innerTextSet editor content:
const editor = document.querySelector('.ProseMirror');
editor.innerHTML = '<p>New content</p>';
editor.dispatchEvent(new Event('input', { bubbles: true }));Open settings (Cmd+,):
document.dispatchEvent(new KeyboardEvent('keydown', { key: ',', metaKey: true, bubbles: true }));6. Collaborative Manual Testing
Some things cannot be automated:
- Native file dialogs (Cmd+O, Cmd+S, Cmd+Shift+S)
- Menu keyboard shortcuts (Cmd+N, Cmd+W)
- System-level interactions
For these, use a collaborative workflow:
Pattern: Setup → Handoff → Verify
- Setup (Codex does this):
- Launch app via Circuit Electron
- Create test state (content, settings, etc.)
- Announce timestamp/content for later verification
- Handoff (User does this):
- Clear instruction: "Press Cmd+O and open AGENTS.md"
- Wait for user confirmation: "Let me know when done"
- Verify (Codex does this):
- Use
text_contentto check result - Compare against expected state
- Report pass/fail
- Use
Example Handoff Message
**Your turn - Manual Step:**
The app should show:
- Title: "Untitled *"
- Content: "Test content" with timestamp `2025-12-27T17:23:13.351Z`
**Do this now:**
1. Press **Cmd+O**
2. Select **AGENTS.md** from the project root
Let me know when done.Closing/Reopening for Persistence Tests
When testing app restart persistence:
- Close session:
mcp__circuit-electron__close - Ask user to close app if needed: "Close the app with Cmd+Q"
- Relaunch:
mcp__circuit-electron__app_launch - Or ask user: "Reopen for me" (Codex relaunches)
7. Post Results to PR
Use GitHub MCP to comment:
mcp__github__add_issue_comment (owner: "solo-ist", repo: "prose", issue_number: <pr-number>, body: "...")Result Format
## QA Test Results - Automated Testing
### ✅ Test Name - PASSED
- What was tested
- Verification details
### ❌ Test Name - FAILED
- What was tested
- What went wrong
- Steps to reproduce
### ⚠️ Test Name - PARTIAL
- What was automated
- What needs manual verification
---
## Manual Testing Required
### Test Name (Manual Steps)
**Setup:** [prerequisites]
1. Step one
2. Step two
**Verify:**
- [ ] Checkbox item
- [ ] Another checkbox
**Why manual:** [explanation]
---
## Summary
| Test | Status | Notes |
|------|--------|-------|
| Test 1 | ✅ PASSED | Details |
| Test 2 | ❌ FAILED | Details |
**Recommendation:** [merge/fix/needs work]Troubleshooting
Circuit Electron Issues
- Snapshot errors: Use
includeSnapshots: falsewhen launching, useevaluatewithtext_contentinstead ofsnapshot - Keyboard tools broken: The
key,keyboard_press, andkeyboard_typetools often fail with "Cannot read properties of undefined (reading 'snapshot')". Usetypetool with selector instead, orevaluateto dispatch KeyboardEvents - Click not working: Use
evaluateto click via JavaScript - Keyboard shortcuts via JS don't work: Synthetic KeyboardEvents don't properly trigger React state updates. Some shortcuts (like Cmd+F) are intercepted by Electron/macOS before reaching the renderer. For these, use collaborative manual testing
- App won't launch: Try
mode: "development"withstartScript: "dev" - "Not connected" errors: Circuit Electron MCP may disconnect. Try relaunching or use bash to start dev server directly
Keyboard Shortcut Testing
Keyboard shortcuts in Electron are tricky to test:
- Electron menu shortcuts (registered in
src/main/menu.ts) intercept keys before they reach the renderer - Synthetic JS KeyboardEvents don't trigger React's event handlers properly -
metaKeyis often stripped - System shortcuts (like Cmd+F) may be intercepted by macOS
Workaround: For keyboard shortcut testing, use collaborative manual testing where the user presses the keys and Codex verifies the results.
Common Gotchas
- Always wait for content to save before closing (brief pause or verify via evaluate)
- Radix UI dropdowns need actual clicks, not just setting values
- Recovery dialogs appear on app restart if there's unsaved content
- Stale preload scripts: Always kill existing electron/vite processes and checkout the correct branch before testing
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

