Menu
Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Multi-perspective academic paper review with dynamic reviewer personas. Simulates 5 independent reviewers (EIC + 3 peer reviewers + Devil's Advocate) with field-specific expertise. Supports full review, re-review (verification), quick assessment, methodology focus, Socratic guided, and calibration modes. Triggers on: review paper, peer review, manuscript review, referee report, review my paper, critique paper, simulate review, editorial review, calibrate reviewer, reviewer calibration, measure reviewer accuracy.
12-agent academic paper writing pipeline. 10 modes (full/plan/outline/revision/revision-coach/abstract/lit-review/format-convert/citation-check/disclosure). 6 paper types, 5 citation formats, bilingual abstracts, LaTeX/DOCX-via-Pandoc/PDF output. Style Calibration + Writing Quality Check + Anti-Patterns with IRON RULE markers. Triggers: write paper, academic paper, guide my paper, parse reviews, AI disclosure, 寫論文, 學術論文, 引導我寫論文, 審查意見.
Orchestrator for the full academic research pipeline: research -> write -> integrity check -> review -> revise -> re-review -> re-revise -> final integrity check -> finalize. Coordinates deep-research, academic-paper, and academic-paper-reviewer into a seamless 10-stage workflow with mandatory integrity verification, two-stage peer review, and reproducible quality gates. Triggers on: academic pipeline, research to paper, full paper workflow, paper pipeline, end-to-end paper, research-to-publication, complete paper workflow.
Universal deep research agent team. 13-agent pipeline for rigorous academic research on any topic. 7 modes: full research, quick brief, paper review, lit-review, fact-check, Socratic guided research dialogue, and systematic review with optional meta-analysis. Covers research question formulation, Socratic mentoring, methodology design, systematic literature search, source verification, cross-source synthesis, risk of bias assessment, meta-analysis, APA 7.0 report compilation, editorial review, devil's advocate challenges, ethics review, and post-research literature monitoring. Triggers on: research, deep research, literature review, systematic review, meta-analysis, PRISMA, evidence synthesis, fact-check, guide my research, help me think through, 研究, 深度研究, 文獻回顧, 文獻探討, 系統性回顧, 後設分析, 事實查核, 引導我的研究, 幫我釐清, 幫我想想, 我不確定要研究什麼, 研究方向, 研究主題.
Helps an AI assistant work with the Miraheze wiki farm — writing wiki requests that get approved, navigating ManageWiki, doing common how-to tasks (templates, skins, permissions, custom domains, backups), writing regex for MediaWiki search-and-replace, AND writing actual article and page content for Miraheze-hosted wikis. Miraheze does NOT ban generative AI; AI-written content is permitted (subject to per-wiki rules). MADE BY SQERSTERS
Helps an AI assistant write, structure, and edit articles in the encyclopedic style of Wikipedia — neutral tone, lead section, summary style, inline citations, no peacock/weasel/persuasive language, and the stub→FA quality ladder. Also covers Simple English Wikipedia rules. MADE BY SQERSTERS
| name | testing-qa |
| description | Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance. |
| category | workflow-bundle |
| risk | safe |
| source | personal |
| date_added | 2026-02-27 |
Comprehensive testing and quality assurance workflow covering unit tests, integration tests, E2E tests, browser automation, and quality gates for production-ready software.
Use this workflow when:
test-automator - Test automationtest-driven-development - TDDUse @test-automator to design testing strategy
Use @test-driven-development to implement TDD workflow
javascript-testing-patterns - Jest/Vitestpython-testing-patterns - pytestunit-testing-test-generate - Test generationtdd-orchestrator - TDD orchestrationUse @javascript-testing-patterns to write Jest tests
Use @python-testing-patterns to write pytest tests
Use @unit-testing-test-generate to generate unit tests
api-testing-observability-api-mock - API testinge2e-testing-patterns - Integration patternsUse @api-testing-observability-api-mock to test APIs
playwright-skill - Playwright testinge2e-testing-patterns - E2E patternswebapp-testing - Web app testingUse @playwright-skill to create E2E tests
Use @e2e-testing-patterns to design E2E strategy
browser-automation - Browser automationwebapp-testing - Browser testingscreenshots - Screenshot automationUse @browser-automation to automate browser tasks
Use @screenshots to capture marketing screenshots
performance-engineer - Performance engineeringperformance-profiling - Performance profilingweb-performance-optimization - Web performanceUse @performance-engineer to test application performance
code-reviewer - AI code reviewcode-review-excellence - Review best practicesfind-bugs - Bug detectionsecurity-scanning-security-sast - Security scanningUse @code-reviewer to review pull requests
Use @find-bugs to detect bugs in code
lint-and-validate - Lintingverification-before-completion - VerificationUse @lint-and-validate to check code quality
Use @verification-before-completion to verify changes
/ / \ E2E Tests (10%)
/---- / \ Integration Tests (20%)
/-------- / \ Unit Tests (70%)
/------------```
## Quality Gates Checklist
- [ ] Unit test coverage > 80%
- [ ] All tests passing
- [ ] E2E tests for critical paths
- [ ] Performance benchmarks met
- [ ] Security scan passed
- [ ] Code review approved
- [ ] Linting clean
## Related Workflow Bundles
- `development` - Development workflow
- `security-audit` - Security testing
- `cloud-devops` - CI/CD integration
- `ai-ml` - AI testing
## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.