Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Triage an intermittent test from run history, environment, and failure pattern before naming a cause.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this when a test passes and fails on the same code.
Gather the last 30 to 100 runs where possible: pass or fail, job, runner, branch, commit, duration, and the failure message. Say how many runs you actually saw and over what dates.
Group the failures by job, runner, time of day, test order, duration, and error. Look for common causes: timing and waits, shared state between tests, test order, real clocks, network calls, random data, and resource limits. Name each candidate with the evidence for and against it, and how sure you are. Say when there are too few failures to tell.
Propose the smallest check that would confirm or rule out the top candidate, such as a rerun loop on one job, a fixed seed, or running the test alone. Then list who owns the test and the options: fix, quarantine with an issue and a date, or leave it and watch.
Never call a test flaky, or a cause found, without run history to show it. Do not skip, disable, retry-wrap, or delete a test yourself; the owner decides.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
日本語の概要は準備中です。原文の説明を表示しています。
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
日本語の概要は準備中です。原文の説明を表示しています。
Write ad variants that each test one idea, within platform limits and supported claims.
日本語の概要は準備中です。原文の説明を表示しています。
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
日本語の概要は準備中です。原文の説明を表示しています。