Skip to content

Kartik-Doye/Ravengard-AI-Recruiter / .agents/skills/proof

Chooses and implements the cheapest trustworthy test boundary for a behavior or invariant, including regression, property, contract, integration, and end-to-end tests. Use when adding tests, protecting a bug fix, or proving changed behavior without optimizing for coverage counts.

FileKindSize
SKILL.mdskill md9.6 KB
references/boundary-picker.mdmarkdown3.8 KB
references/research.mdmarkdown2.3 KB

references/research.md

View on GitHub
# proof research ledger

## Source 1

Title: Test sizes

Author / Organization: Google Testing Blog

Publication date: 2010-12-13

Version: Web article

URL: https://testing.googleblog.com/2010/12/test-sizes.html

Source type: official docs

What it establishes:
Tests trade scope, fidelity, speed, and isolation; larger is not automatically better.

What this skill adopts:
Choose the cheapest boundary that can faithfully fail for the target behavior or invariant.

What it does NOT establish:
It does not prescribe an arbitrary coverage percentage or require every bug to be reproduced at unit level.

Numbers taken from source:
No numerical coverage target is adopted.

Reverify when:
Project risk or stronger testing evidence changes.

## Test behavior and implementation detail

Title: Testing on the Toilet: Know Your Test Doubles

Author / Organization: Google Testing Blog

Publication date: 2018

Version: Web article

URL: https://testing.googleblog.com/2018/07/testing-on-toilet-know-your-test-doubles.html

Source type: official docs

What it establishes:
Test doubles differ in how they replace collaborators and can make tests depend
on details that are not the behavior under test.

What this skill adopts:
Use doubles at non-owned or impractical boundaries and prefer outcome assertions
over mock interaction choreography.

What it does NOT establish:
It does not ban all mocks or determine the right test boundary for a specific
repository.

Numbers taken from source:
None.

Reverify when:
The project test architecture or relevant testing guidance changes.

## Deterministic test design

Title: Testing on the Toilet: Avoid Sleep

Author / Organization: Google Testing Blog

Publication date: 2015

Version: Web article

URL: https://testing.googleblog.com/2015/04/testing-on-toilet-dont-sleep-on-it.html

Source type: official docs

What it establishes:
Timing sleeps make tests slower and less reliable than waiting for a specific
condition or using deterministic synchronization.

What this skill adopts:
Prefer condition-based waiting and controlled clocks/scheduling over arbitrary
sleep in asynchronous and concurrent tests.

What it does NOT establish:
It does not guarantee a test is race-free or prescribe a universal timeout.

Numbers taken from source:
No timeout value is adopted.

Reverify when:
The asynchronous runtime, synchronization primitive, or test runner changes.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 323kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 323kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 323kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall