Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Ship reliable tests in every pipeline — CI-specific patterns for speed, stability, and actionable reports.
9 guides covering CI/CD setup, parallel execution, containerized runs, reporting, and infrastructure patterns for all major CI providers.
retries: 2 in CI only — surface flakiness in pipelines, not locallytraces: 'on-first-retry' — capture rich debugging artifacts without slowing every run--shard=N/M splits tests evenly; scale horizontally, not vertically~/.cache/ms-playwright keyed on Playwright versionmcr.microsoft.com/playwright:v* has all OS deps pre-installedglobalSetup, reuse storageState across workers| Provider | Guide |
|---|---|
| GitHub Actions | ci-github-actions.md |
| GitLab CI | ci-gitlab.md |
| CircleCI / Azure DevOps / Jenkins | ci-other.md |
| Topic | Guide |
|---|---|
| Parallel execution & sharding | parallel-and-sharding.md |
| Docker & containers | docker-and-containers.md |
| Multi-project config | projects-and-dependencies.md |
| Topic | Guide |
|---|---|
| Reports & artifacts | reporting-and-artifacts.md |
| Code coverage | test-coverage.md |
| Global setup/teardown | global-setup-teardown.md |
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Simulates academic peer review, evaluating papers across Originality, Methodology, Results, and Writing to provide Major/Minor Revision recommendations with actionable feedback. Triggers when a user asks to "review my paper," "simulate peer review," or "give my paper a peer review.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration", "Golden Ticket", "Silver Ticket", "AS-REP roasting", "NTLM relay", or needs guidance on Windows domain penetration testing.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API penetration testing", "bug bounty API testing", or needs guidance on API security assessment techniques.
日本語の概要は準備中です。原文の説明を表示しています。
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
日本語の概要は準備中です。原文の説明を表示しています。
Interactive system flow tracing across CODE, API, AUTH, DATA, NETWORK layers with SQLite persistence and Mermaid export. Use for security audits, compliance documentation, flow tracing, feature ideation, brainstorming, debugging, architecture reviews, or incident post-mortems. Triggers on audit, trace flow, document flow, security review, debug flow, brainstorm, architecture review, post-mortem, incident review.
日本語の概要は準備中です。原文の説明を表示しています。
Authentication patterns: session vs JWT vs OAuth comparison, provider selection (NextAuth, Clerk, Supabase Auth), security checklist, and common mistakes. Use when implementing auth, reviewing auth flows, or choosing auth providers.
日本語の概要は準備中です。原文の説明を表示しています。