gtest-tdd-loop
Skill17 starsChanged 7 months agoMITView on GitHub
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.
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read ../../references/gtest-cheatsheet.md, ../../references/sails-gtest-and-local-validation.md, and …
- Very specific: line 16
Use ../../assets/gtest-report-template.md as the output shape.
- Very specific: line 18
Write the result to docs/plans/YYYY-MM-DD-<topic>-gtest.md.
- Very specific: line 20
Use ../../scripts/run_gtest.sh to execute the loop and ../../scripts/parse_test_output.py to summarize failures.
- Distinctive: line 24
Write or update the smallest failing gtest case for the current task.
- Distinctive: line 25
Verify the test fails for the expected reason.
- Very specific: line 27
Run the local loop through ../../scripts/run_gtest.sh.
- Distinctive: line 32
Do not skip the failing-test step.
- Distinctive: line 33
Do not claim success from compile output alone.
- Distinctive: line 34
Keep gtest evidence tied to the current task, not a generic workspace run.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- vara-skillsSkill
- vara-skillsSkill
- awesome-sails-vftSkill
- gear-architecture-plannerSkill
- gear-builtin-actorsSkill
- gear-gstd-api-mapSkill
- gear-message-executionSkill
- idea-to-specSkill
- sails-architectureSkill
- sails-dev-envSkill
- sails-ethexe-architectureSkill
- sails-ethexe-implementerSkill
- sails-feature-workflowSkill
- sails-frontendSkill
- sails-gtestSkill
- sails-idl-clientSkill
- sails-indexerSkill
- sails-local-smokeSkill
- sails-new-appSkill
- sails-program-evolutionSkill
- sails-rust-implementerSkill
- ship-sails-appSkill
- task-decomposerSkill
- vara-skills-upgradeSkill
- vara-walletSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.