Gtest tdd loop

Skill gear-foundation/vara-skills/skills/gtest-tdd-loop

Use when Gear or Vara behavior changes need a deterministic local gtest loop before the work can be considered complete. Do not use for deploy-only work, live-node-only smoke checks, or features without a local test target.From its SKILL.md

Install

npx -y skills add gear-foundation/vara-skills --skill gtest-tdd-loop

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

17 stars17 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.4 KB, as published. Nobody here has run it

Gtest Tdd Loop

Overview

Drive local verification through a red-green loop and summarize failures in a machine-readable form.

Start Here

Read ../../references/gtest-cheatsheet.md, ../../references/sails-gtest-and-local-validation.md, and ../../references/gear-gas-reservations-and-waitlist.md.

Use ../../assets/gtest-report-template.md as the output shape.

Write the result to docs/plans/YYYY-MM-DD-<topic>-gtest.md.

Use ../../scripts/run_gtest.sh to execute the loop and ../../scripts/parse_test_output.py to summarize failures.

Workflow

Write or update the smallest failing gtest case for the current task.
Verify the test fails for the expected reason.
Apply the minimal implementation change.
Run the local loop through ../../scripts/run_gtest.sh.
Capture the parser output and record the final green or remaining gap state.

Guardrails

Do not skip the failing-test step.
Do not claim success from compile output alone.
Keep gtest evidence tied to the current task, not a generic workspace run.
Escalate if the workspace cannot produce a stable local gtest target.