qa-orchestra
Checks a pull request against its acceptance criteria, suggests the test scenarios you need, and flags which existing tests the change may break. Each check writes a Markdown report you can paste into GitHub or Jira.
13
@anasssPlugins
1@anasssAgents
10automation-writer
AgentConverts test scenarios into executable Playwright, Cypress, or Gherkin test code
@anasssbrowser-validator
AgentValidates test scenarios against a running application using Chrome MCP — navigates, interacts, and verifies in a real browser
@anasssbug-reporter
AgentUse this agent when qa-output/functional-review.md or qa-output/browser-validation.md reports any gap, failed scenario, or…
@anasssenvironment-manager
AgentChecks out PR branches, runs setup commands, and starts the application locally for live testing
@anasssfunctional-reviewer
AgentCompares code diff against acceptance criteria to find functional gaps, regression risks, and missing edge cases
@anasssmanual-validator
AgentGuides manual test execution scenario by scenario and produces a structured validation report
@anasssorchestrator
AgentRoutes QA tickets to the right agents in the right order — including environment setup and live browser validation
@anasssrelease-analyzer
AgentAnalyzes a multi-repo release diff to map cross-repo impact, AC compliance, and deployment risks
@anassssmart-test-selector
AgentMaps code changes to existing tests — finds which tests to run, which may break, and where coverage gaps exist
@anassstest-scenario-designer
AgentGenerates comprehensive test scenarios from acceptance criteria (happy path, negative, boundary, edge cases)
@anasssIs this you? Claim your profilePut a plugin at the top of Plugins, from $9