golden-case
Skill1 starsChanged 2 days agoApache-2.0View on GitHub
Author a golden test case for a Fairmark method with expected values from an independent source. Use when adding coverage for a method or an acceptance criterion.
In this repository39 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- add-methodSkill
- adr-newSkill
- commitSkill
- explain-changesSkill
- fix-ciSkill
- implement-specSkill
- onboardingSkill
- plan-sprintSkill
- pre-prSkill
- pr-triageSkill
- releaseSkill
- roadmap-updateSkill
- run-sprintSkill
- session-endSkill
- session-startSkill
- spec-newSkill
- translateSkill
- add-methodSkill
- adr-newSkill
- commitSkill
- explain-changesSkill
- fix-ciSkill
- golden-caseSkill
- implement-specSkill
- onboardingSkill
- plan-sprintSkill
- pre-prSkill
- pr-triageSkill
- releaseSkill
- roadmap-updateSkill
- run-sprintSkill
- session-endSkill
- session-startSkill
- spec-newSkill
- translateSkill
- fairmarkSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
Use only anonymised or synthetic data.
- Very specific: line 31
Run cargo test -p fairmark-core --test golden and uv run pytest python/tests/test_golden.py.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
- Choose the source of truth, in order of preference: a practitioner model supplied by the
maintainer; a published worked example re-derived by hand; an independent reference
implementation in
scripts/reference_values.py(Pythondecimal, precision 50, written from the formula, not from the Rust code). - Create
tests/golden/<method>/<kebab-case-name>.yaml:
Keys of# Source: <where the expected values come from> method: <method id> description: <one line> input: { ... } # amounts and rates as strings, e.g. "0.085" expect: { field: "value" } tolerance: "0.000000001"expectare top-level fields or JSON Pointers (/years/0/total) into the resultvalue. To assert documented defaults, addexpect_metawith JSON Pointers intometa, for example/defaults_applied/0/field; it is compared likeexpectand protected like it. To assert that a list has no entry beyond those asserted, addexpect_lengthwith JSON Pointers intovalueand the expected count, for example/not_computed: "3". An error case (expect_error) may addexpect_error_reportwith JSON Pointers into the error report (ADR 0014 G5), for example/pointer,/reason,/pointers/1or/errors/2/pointer; values are compared exactly (nullfor a null field) and protected likeexpect. In an error case,expect_lengthcounts arrays of the error report, for example/errors: "3", so that no error beyond those asserted is reported. Do not assert/fix: its wording is not part of the contract. - Use only anonymised or synthetic data.
- Run
cargo test -p fairmark-core --test goldenanduv run pytest python/tests/test_golden.py. - Existing golden files are protected by a hook: never edit them; propose a
numerical-changeto the maintainer instead.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

