containers
- 4 skills
- 0 followers
- 11 hours ago last updated
- ▌ Toolset Design · containersDesign and validate new MCP toolsets, tools, and tool changes. Use when planning a new toolset, adding tools to an existing toolset, reviewing a toolset PR, or deciding whether a new tool is warranted. Covers the full lifecycle: eval-first validation, tool design methodology, consolidation patterns, and review criteria.
- ▌ Investigate Gh Run · containersDeep investigation of CI/CD test failures - identifies root causes by analyzing logs, artifacts, git history, and source code
- ▌ Playwright Trace Analysis · containers bundleAnalyzes Playwright trace archives (`trace.zip`) to diagnose test failures, flaky behavior, and unexpected UI states using trace steps, console output, network activity, and screenshots. Use when the user provides a trace path or trace artifact, asks why a Playwright or E2E test failed, wants root-cause analysis from CI artifacts, mentions the trace viewer, or asks whether a failure is flaky or an application bug.
- ▌ Test Failure Analysis Unattended Correction · containersUse when a Playwright E2E test fails and you have a trace archive to investigate. Optionally accepts a GitHub Actions pipeline link for additional CI context. Runs non-interactively.