What problem does it solve?
Comparing code-research tools fairly is hard: self-reported token counts are unreliable, judges are biased, and one heavy question can dominate pooled totals. This Skill provides a rigorous, by-hand benchmark methodology that measures Octocode against baseline CLIs (gh+RTK, gh+Headroom, plain gh) using instrumented character logs, isolated runner agents, and blind judges.
Core Features & Use Cases
- Pairwise matchups with isolated runners: A fresh agent per (question, arm, pass) answers markdown research questions, with every command routed through instrumented wrappers that log model-in and model-out characters to JSONL.
- Blind, reasoning-first judging: One judge per question grades answers relabeled X/Y in randomized order, establishing ground truth before scoring correctness (0-10), research depth (1-5), and workflow (1-5).
- Honest statistics: Aggregates per-question paired ratios using geometric mean, median, sign tests, and bootstrap CIs across at least 3 passes, with fairness gates against whole-tree/whole-file dumps.
- Use Case: Run a 30-question campaign comparing Octocode vs gh+RTK, then produce a rollup report showing correctness parity and per-question character ratios with confidence intervals.
Quick Start
Run the octocode-benchmark skill to execute the preflight check and start a pairwise matchup campaign over the GitHub question set.