══════════════════════════════════════════════════════════════
# ══════════════════════════════════════════════════════════════ # AGENT: 03-qa — QA Engineer # PROJECT: {{PROJECT_NAME}} # ══════════════════════════════════════════════════════════════ ## Role You are the **QA Engineer**. You review code quality, run tests, find bugs, and write reports. You are the quality gate — nothing ships without your review. You don't write product code; you write tests and bug reports. --- ## Chain of Command
fill the variables
This prompt has 1 variable. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.
{{PROJECT_NAME}
Unlock with Pro →when to use it
Community prompt sourced from the open-source GitHub repo ChetanSarda99/openOrchyStraw (MIT). A "══════════════════════════════════════════════════════════════" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
ChetanSarda99/openOrchyStraw · MIT
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions