メニュー
Guidance for creating, running, fixing, and promoting behavioral evaluations. Use when verifying agent decision logic, debugging failures, debugging prompt steering, or adding workspace regression tests.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Trigger this skill when the user wants to start an asynchronous PR review, run background checks on a PR, or check the status of a previously started async PR review.
A specialized skill for Jiminy CLI that provides high-performance, fail-fast monitoring of GitHub Actions workflows and automated local verification of CI failures. It handles run discovery automatically—simply provide the branch name.
Generates and formats changelog files for a new release based on provided version and raw changelog data.
Always use this skill when the task involves writing, reviewing, or editing files in the `/docs` directory or any `.md` files in the repository.
Use this skill when asked to create a GitHub issue. It handles different issue types (bug, feature, etc.) using repository templates and ensures proper labeling.
Use this skill if the user asks you to help them address GitHub PR comments for their current branch of the Jiminy CLI. Requires `gh` CLI tool.
| name | behavioral-evals |
| description | Guidance for creating, running, fixing, and promoting behavioral evaluations. Use when verifying agent decision logic, debugging failures, debugging prompt steering, or adding workspace regression tests. |
Behavioral evaluations (evals) are tests that validate the agent's decision-making (e.g., tool choice) rather than pure functionality. They are critical for verifying prompt changes, debugging steerability, and preventing regressions.
[!NOTE] Single Source of Truth: For core concepts, policies, running tests, and general best practices, always refer to evals/README.md.
appEvalTest (AppRig). See creating.md.evalTest (TestRig). See creating.md.USUALLY_PASSES.ALWAYS_PASSES (locks in regression).Seed the workspace with necessary files using the files object to simulate a realistic scenario (e.g., NodeJS project with package.json).
Audit agent decisions using rig.setBreakpoint() (AppRig only) or index verification on rig.readToolLogs().
Run single tests locally with Vitest. Confirm stability locally before relying on CI workflows.
Detailed procedural guides: