Select and run the maintained event-store regression fixtures against known-good and controlled-bad behavior when changing append preconditions, payloads, conflict refetch or concurrent stream creation.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Use the recipe records to find an existing independently specified assertion for the changed contract. The maintained Regression test module supplies service-record wrappers and barriers. Keep that implementation and its Hspec tests in the framework test library.
Run python3 .agents/skills/event-store-regression/scripts/smoke.py check to verify recipe locations. This checks metadata only. Run python3 .agents/skills/event-store-regression/scripts/smoke.py run --recipe <name> to execute the same selected examples against normal behavior and their controlled fault. Omit --recipe for all recipes. Provide the services required by the selected test suite. Missing prerequisites are failures, not successful proofs.
The fault changes the exercised behavior. It must not merely throw a sentinel before reaching the implementation. Require the named assertion failure in the expected example, with the expected nonempty selection. The runner rejects setup failures, compiler failures, timeouts and unrelated assertions.
Keep before and after logs and source hashes under .agents-state/event-store-regression/. A passing sensitivity run proves these selected tests can detect their controlled violations. Preserve the broader event-store tests for event identity, ordering, payloads, replay and historical integrity. These recipes do not replace that coverage.
For a new regression, follow TDD and Regression evidence. Use barriers and the owning NeoHaskell concurrency primitives for coordination, with meaningful examples or properties and independent expected outcomes.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
日本語の概要は準備中です。原文の説明を表示しています。
Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect or supervise a PR or stack through review and CI to merge-ready, using current GitHub evidence and the requested mode.
日本語の概要は準備中です。原文の説明を表示しています。
Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you benchmark or report a measured speedup or regression, including complete framework flows and compilation of projects that consume the framework.
日本語の概要は準備中です。原文の説明を表示しています。
Restate the last message in plain human language, with no jargon.
日本語の概要は準備中です。原文の説明を表示しています。
Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services. Use for CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, or terminal demos.
日本語の概要は準備中です。原文の説明を表示しています。