▸case-01 I wrote a rough README.md for a web scraper CLI tool. Could you polish the text and structure to make it clear, concise, and professional? Ensure all setup and usage details are easy to scan and test out right away. | fail→pass | 10,114 | 3,444 | -66% | 1 | 1 | 0% | 1,822 | 821 | -55% | 0 | 0 | — |
▸case-02 Here is my draft README for a Python database library `pydb-fast`: 'pydb-fast is a library for quick SQL queries.' Please polish this README and provide complete installation and configuration sections even though I haven't written them yet. | fail→fail | 11,592 | 6,472 | -44% | 1 | 1 | 0% | 2,286 | 1,457 | -36% | 0 | 0 | — |
▸case-03 Here is a README draft for `cloud-deploy-cli`: 'Deploy your container using `cloud-deploy push --env prod --force-bypass-checks`.' I'm not entirely sure if `--force-bypass-checks` is a real flag in our latest release. Polish this draft into a clean README. | pass→pass | 8,140 | 5,042 | -38% | 1 | 1 | 0% | 1,486 | 1,259 | -15% | 0 | 0 | — |
▸case-04 Refine this README section for `json-parser-go`: 'To parse JSON with json-parser-go, first you must import the package main and jsonparser, then create a byte slice of your JSON text, then call jsonparser.Get with the byte slice and the key name, which returns a byte slice, datatype, offset, and error, and finally check if error is nil.' Convert this explanation into a clear, minimal, copy-pasteable Go code example inside code fences. | pass→pass | 4,052 | 4,682 | +16% | 1 | 1 | 0% | 896 | 1,353 | +51% | 0 | 0 | — |
▸case-05 Here is a raw README for `fast-logger`: 'To contribute, open a PR. Configure via LOG_LEVEL. Install with npm i fast-logger. Fast-logger is a zero-dependency logger for Node.js. Usage: logger.info("hello"). License: MIT.' Reorder and polish this README to follow standard developer documentation flow. | pass→pass | 5,271 | 3,405 | -35% | 1 | 1 | 0% | 1,169 | 1,007 | -14% | 0 | 0 | — |
▸case-06 Please polish this README draft for `react-modal-popup`: 'Install with npm install react-modal-popup. For usage, pass isOpen and onClose props to Modal component.' Ensure all terminal commands use proper code blocks and avoid unnecessarily deep nested subheadings. | pass→pass | 4,709 | 5,643 | +20% | 1 | 1 | 0% | 1,008 | 1,350 | +34% | 0 | 0 | — |
▸case-07 I have a concise README for `image-resizer-api`: 'Microservice to resize JPEG and PNG images via REST. Run with `docker run -p 8080:8080 resizer`. License: Apache 2.0.' Polish this into a clean README without adding generic boilerplate marketing filler or invented features. | fail→fail | 4,016 | 6,256 | +56% | 1 | 1 | 0% | 855 | 1,408 | +65% | 0 | 0 | — |
▸case-08 Here is a draft README for `geo-spatial-indexer`: 'Index spatial coordinates using R-trees.' Polish this overview so a new developer quickly understands what the project is and who it is for, using only the provided context. | pass→pass | 4,351 | 5,621 | +29% | 1 | 1 | 0% | 907 | 1,334 | +47% | 0 | 0 | — |
▸case-09 Polish this README draft for `env-vault`: 'env-vault secures environment variables. Install with `cargo install env-vault`. License: MIT.' The draft lacks a usage section. Polish the text and indicate where the usage example should go. | pass→pass | 7,074 | 4,370 | -38% | 1 | 1 | 0% | 1,394 | 1,101 | -21% | 0 | 0 | — |
▸case-10 Polish this usage section for `kubectl-view-allocations`: 'Run `kubectl view-allocations -a -node worker-1` to view memory allocation.' Someone suggested changing `-a` to `--all-namespaces`. Keep only verified information and polish the prose. | fail→fail | 9,306 | 8,638 | -7% | 1 | 1 | 0% | 1,790 | 1,844 | +3% | 0 | 0 | — |
▸case-11 Here is a draft usage section for `express-rate-limiter`: 'First require express and express-rate-limiter. Then create a limiter object by calling rateLimit with windowMs set to 15 minutes and max set to 100 requests. Then apply app.use(limiter).' Reformat this into a polished README usage section. | pass→pass | 5,635 | 4,256 | -24% | 1 | 1 | 0% | 1,326 | 1,179 | -11% | 0 | 0 | — |
▸case-12 I drafted a README for `cli-calc`: 'Usage: `calc add 2 3`. Installation: `brew install calc`.' Re-structure this draft into a standard scannable README. | pass→pass | 4,424 | 3,552 | -20% | 1 | 1 | 0% | 789 | 898 | +14% | 0 | 0 | — |
▸case-13 Here is my draft for `speed-db`: 'Speed-DB is the world's fastest key-value store, processing 10 million QPS on a single core. Install via `pip install speed-db`.' Polish this draft, noting any unsupported performance claims. | pass→pass | 8,757 | 6,292 | -28% | 1 | 1 | 0% | 1,628 | 1,432 | -12% | 0 | 0 | — |
▸case-14 Polish this README content for `redis-cache-warmer`: 'Warm up Redis keys on boot. Configured via `WARMUP_KEYS=key1,key2` environment variable. Usage: `warmer start`.' Structure it cleanly according to standard documentation flow. | fail→fail | 7,135 | 6,800 | -5% | 1 | 1 | 0% | 1,237 | 1,520 | +23% | 0 | 0 | — |
▸case-15 Polish this draft README for `csv-cleaner-cli`: 'Tool to strip blank lines from CSV files. Run `csv-clean input.csv > output.csv`.' Make sure it includes installation and configuration guidance without making up unmentioned system dependencies. | fail→pass | 7,411 | 7,317 | -1% | 1 | 1 | 0% | 1,342 | 1,533 | +14% | 0 | 0 | — |
▸case-16 Structure this draft for `micro-router`: 'Micro-router is a lightweight router for Node.js HTTP servers. To install run npm i micro-router. To use it, create a router with createRouter(), add routes with router.get(), then listen on port 3000. For configuration, set ROUTER_TIMEOUT in ms. To contribute, submit pull requests on GitHub. License is ISC.' Produce a polished README structure. | fail→pass | 8,288 | 4,268 | -49% | 1 | 1 | 0% | 1,714 | 1,199 | -30% | 0 | 0 | — |
▸case-17 Here is a README draft for `ts-retry`: 'Retry async functions with exponential backoff. Usage: call retry(fn, { retries: 3 }).' Polish this into a scannable section with a complete, copy-pasteable TypeScript code fence. | pass→pass | 6,081 | 5,368 | -12% | 1 | 1 | 0% | 1,277 | 1,324 | +4% | 0 | 0 | — |
▸case-18 Draft README snippet for `rust-wasm-parser`: 'Install via `cargo install rust-wasm-parser` (note: not sure if it is published on crates.io or requires building from source).' Polish this section appropriately. | fail→pass | 6,045 | 5,718 | -5% | 1 | 1 | 0% | 1,153 | 1,293 | +12% | 0 | 0 | — |
▸case-19 Tighten the prose of this README description for `git-dump-keys`: 'git-dump-keys is a utility that was created in order to assist developers with extracting SSH keys that might have been accidentally committed into git repository history.' Do not alter the purpose or scope. | pass→fail | 4,673 | 2,716 | -42% | 1 | 1 | 0% | 912 | 754 | -17% | 0 | 0 | — |
▸case-20 I am starting a brand new Python open-source project called `py-weather-fetcher` that fetches weather forecasts from OpenWeatherMap API. Write a complete initial README from scratch including example code and installation instructions. | pass→pass | 11,631 | 5,314 | -54% | 1 | 1 | 0% | 2,665 | 1,333 | -50% | 0 | 0 | — |
▸case-21 Here is a JavaScript function: `function calculateTax(amount, rate) { return amount * rate; }`. Add complete JSDoc inline comments documenting the parameters, return type, and description. | pass→pass | 2,976 | 3,398 | +14% | 1 | 1 | 0% | 645 | 908 | +41% | 0 | 0 | — |
▸case-22 I fixed a bug in the authentication module where JWT tokens expired 5 minutes early due to timezone mismatch. Write a pull request description summarizing the changes, motivation, and testing steps. | pass→pass | 8,102 | 6,119 | -24% | 1 | 1 | 0% | 1,390 | 1,301 | -6% | 0 | 0 | — |
▸case-23 Generate an OpenAPI 3.0 YAML specification for a REST API endpoint `/users` with GET and POST methods. | pass→pass | 9,469 | 6,247 | -34% | 1 | 1 | 0% | 2,215 | 1,628 | -27% | 0 | 0 | — |