メニュー
Fix flaky tests by repeatedly running the suite, collecting intermittent failures, and proving stability. Use when asked to fix flaky tests or require repeated/consecutive green test runs.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Guides agents through isolated Git worktree setup, lifecycle commands, process cleanup, and per-worktree local development state. Use when creating, starting, stopping, inspecting, cleaning up, or troubleshooting Git worktree development environments or when a repository includes a worktree lifecycle CLI.
Continuously watch and fix release main CI until the branch is fully green and verified working. Use when asked to babysit CI, babysit CI release, monitor release main, run /loop for CI, run /goal until checks pass, or keep iterating until release main is green.
Manage LinkedIn messaging, profiles, posts, connections, and company pages via Unipile. Use for networking, content publishing, and lead engagement.
Scoped commit workflow with a bundled committer script that prevents accidental broad staging. Use when the user asks to commit, commit all, create a git commit, or handle commit-time staging in this repository.
Systematically QA a web application like a real user, triage issues by severity, fix scoped bugs when asked, verify fixes with evidence, and report ship readiness. Use when asked to QA, test a site or app, find bugs, test and fix, or check whether a feature works.
Debug Bap end-to-end across coworker/chat workflows, MCP state, Daytona sandboxes, observability, and UI QA. Use when debugging Bap, a Bap coworker or chat flow, sandbox behavior, Daytona build issues, production-like regressions, or any issue where local fixes are not enough and the full loop must work.
| name | fix-flaky-tests |
| description | Fix flaky tests by repeatedly running the suite, collecting intermittent failures, and proving stability. Use when asked to fix flaky tests or require repeated/consecutive green test runs. |
Use a goal. Run the relevant test suite 20 times, log every intermittent failure, fix root causes, and reset the green counter after each failure or code change.
Do not stop until all observed flakes are fixed and the suite has passed 5 consecutive full runs.
