Install any skill in seconds. Free to start, no credit card required.
Get Started Free →loulanyue/cpp-testing
C++ テストの作成/更新/修正、GoogleTest/CTest の設定、失敗またはフレーキーなテストの診断、カバレッジ/サニタイザーの追加時にのみ使用します。
Passed 18 of 22 test cases with the skill, and 18 of 22 without it.
3 fixed15 passed either way1 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
A function checks whether a user token has expired using std::chrono::system_clock::now(). How should we design this component and its test to avoid flaky time-dependent test failures?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends injecting a clock interface or fake time source into the function. | Passed | Passed |
| Advises against reading system wall clock time directly inside unit tests. | Missed | Passed |
The instructions your model reads when the skill loads.
Agent-focused testing workflow for modern C++ (C++17/20) using GoogleTest/GoogleMock with CMake/CTest.
tests/unit, tests/integration, tests/testdata.gtest_discover_tests() for stable test discovery.--output-on-failure.Follow the RED → GREEN → REFACTOR loop:
// tests/add_test.cpp
#include <gtest/gtest.h>
test cases passed, vs 18 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.