Compressed caveman-style prose for AI coding agents — cuts ~65% output tokens while keeping full technical accuracy
96
100%
Does it follow best practices?
Impact
96%
1.00xAverage score across 38 eval scenarios
Passed
No known issues
{
"context": "Tests whether the response correctly explains the technical differences between git rebase and git merge with accurate tradeoffs.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Explains merge creates a merge commit",
"description": "States that git merge creates a merge commit that joins two branch histories",
"max_score": 12
},
{
"name": "Explains rebase replays commits",
"description": "States that git rebase replays/moves commits onto a new base, creating new commit hashes",
"max_score": 12
},
{
"name": "Mentions history linearity tradeoff",
"description": "Notes that rebase produces a linear history while merge preserves the branching structure",
"max_score": 12
},
{
"name": "Warns about rebase on shared branches",
"description": "Warns against rebasing commits that have been pushed/shared, as it rewrites history",
"max_score": 12
},
{
"name": "No incorrect information",
"description": "Response does not contain factually wrong statements about git internals or behavior",
"max_score": 12
}
]
}evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31
scenario-32
scenario-33
scenario-34
scenario-35
scenario-36
scenario-37