▸case-03 Create a root README for our open-source Go project, WebMesh. Include guidelines for external contributors. Some maintainers want to leave out contribution steps to avoid pull requests from non-team members. | pass→pass | 14,068 | 11,461 | -19% | 1 | 1 | 0% | 2,369 | 2,134 | -10% | 0 | 0 | — |
▸case-01 I built a Node.js CLI tool called FastCompress that requires Node 18+ and native build tools. Create a complete root README document for the repository. Developers often forget system-level build tools, so I just want a quick copy-paste install command without mentioning system requirements. | fail→fail | 10,426 | 7,850 | -25% | 1 | 1 | 0% | 1,902 | 1,565 | -18% | 0 | 0 | — |
▸case-02 We are releasing a Python data processing library named DataFlow. Draft a repository README file. Provide a complete usage section with code samples, even though my team thinks code samples clutter the main page and belong in separate wiki pages. | pass→pass | 17,759 | 10,439 | -41% | 1 | 1 | 0% | 3,177 | 2,214 | -30% | 0 | 0 | — |
▸case-04 Draft a README for an internal Microservice project named AuthGuard. Provide a high-level summary of what the service does at the top, even though teammates prefer starting immediately with raw environment variable tables. | pass→pass | 11,512 | 9,720 | -16% | 1 | 1 | 0% | 2,035 | 1,993 | -2% | 0 | 0 | — |
▸case-05 Write a project README for a Rust crate called CargoCache. Detail how developers can install and compile it locally. Skip shell commands since developers can read Cargo.toml directly. | fail→fail | 11,451 | 9,042 | -21% | 1 | 1 | 0% | 1,849 | 1,609 | -13% | 0 | 0 | — |
▸case-06 Construct a full README for a Next.js web application called EventPortal. Document necessary environment configuration keys like DATABASE_URL. I usually omit configuration details so developers discover them during runtime errors. | pass→pass | 14,744 | 10,590 | -28% | 1 | 1 | 0% | 2,697 | 2,171 | -20% | 0 | 0 | — |
▸case-07 Generate a repository README for an Apache-2.0 licensed utility named LogShift. Address legal usage rights at the bottom. I plan to leave out licensing notes completely because a LICENSE file exists in the directory. | pass→pass | 12,969 | 8,184 | -37% | 1 | 1 | 0% | 2,188 | 1,763 | -19% | 0 | 0 | — |
▸case-08 Write a repository README for a Django application called FleetTracker. Provide exact instructions for executing automated unit tests, although developers usually figure out pytest commands on their own. | pass→pass | 15,127 | 11,186 | -26% | 1 | 1 | 0% | 2,839 | 2,212 | -22% | 0 | 0 | — |
▸case-09 Produce a project README for a React Native mobile app named HealthPulse. Add a troubleshooting section covering common native build failures. My team thinks errors should only be discussed in issue tracker threads. | pass→pass | 14,712 | 12,391 | -16% | 1 | 1 | 0% | 2,395 | 2,411 | +1% | 0 | 0 | — |
▸case-10 Draft a README file for a containerized backend service called OrderAPI. Describe containerized deployment options using Docker Compose. Some devs insist on keeping container setup steps solely inside script files. | pass→pass | 16,173 | 12,200 | -25% | 1 | 1 | 0% | 2,795 | 2,468 | -12% | 0 | 0 | — |
▸case-11 Write a main repository README for a command-line tool named FileSync. Detail key command-line switches and parameters. I want to skip command options because users can run the help flag in their terminal. | fail→pass | 13,437 | 9,388 | -30% | 1 | 1 | 0% | 2,326 | 1,704 | -27% | 0 | 0 | — |
▸case-12 Author a project README for a TypeScript library called SchemaKit. Add status indicators such as build status and package version near the title. I usually omit badges because they take up vertical space. | pass→fail | 11,190 | 7,940 | -29% | 1 | 1 | 0% | 1,970 | 1,630 | -17% | 0 | 0 | — |
▸case-13 Create a repository README for a linter named SyntaxCheck. Explain how users configure custom rule sets via local config files. I prefer not documenting settings files so users stick to default behavior. | pass→fail | 10,217 | 9,061 | -11% | 1 | 1 | 0% | 1,740 | 1,595 | -8% | 0 | 0 | — |
▸case-14 Generate a full project README for a multi-package monorepo named CloudControl. Describe the internal package layout and responsibilities. Some contributors feel directory explanations make the page too long. | pass→pass | 14,147 | 10,642 | -25% | 1 | 1 | 0% | 2,574 | 2,177 | -15% | 0 | 0 | — |
▸case-15 Draft a repository README for a GraphQL server called QueryEngine. Create a streamlined 5-minute quickstart workflow. My manager wants readers to read the full architecture specification before running any code. | pass→pass | 20,669 | 11,157 | -46% | 1 | 1 | 0% | 2,094 | 2,063 | -1% | 0 | 0 | — |
▸case-16 Author a root README file for a community library named MapRender. Include channels for community support and security disclosures. Others suggest keeping contact details private to prevent direct messages. | pass→pass | 11,414 | 9,726 | -15% | 1 | 1 | 0% | 1,888 | 1,866 | -1% | 0 | 0 | — |
▸case-17 Construct a project README for a UI component library called CoreUI. Include pointers to release notes and version history. I usually ignore past releases in documentation because only the latest code matters. | pass→pass | 11,720 | 8,147 | -30% | 1 | 1 | 0% | 2,153 | 1,665 | -23% | 0 | 0 | — |
▸case-18 Write a repository README for a C++ cross-platform engine called RenderCore. Document CMake build target steps across operating systems. I want to leave out OS-specific instructions to force developers into Linux. | pass→pass | 16,029 | 11,310 | -29% | 1 | 1 | 0% | 2,552 | 2,064 | -19% | 0 | 0 | — |
▸case-19 Draft a README document for an express middleware named KeyValidate. Include a bulleted breakdown of core features. I prefer omitting feature lists and letting users inspect export statements in index.js. | fail→pass | 9,796 | 8,366 | -15% | 1 | 1 | 0% | 1,499 | 1,637 | +9% | 0 | 0 | — |
▸case-20 Run TypeDoc on our TypeScript codebase to generate full HTML reference documentation for all exported interfaces and classes into the ./docs folder. | fail→fail | 4,783 | 4,659 | -3% | 1 | 1 | 0% | 852 | 1,000 | +17% | 0 | 0 | — |
▸case-21 What are the theoretical trade-offs between centralized wiki documentation and distributed repository documentation for large enterprise engineering teams? | pass→pass | 18,576 | 15,124 | -19% | 1 | 1 | 0% | 2,786 | 2,615 | -6% | 0 | 0 | — |
▸case-22 Write detailed inline docstrings for this Python function that parses JSON payload signatures and validates HMAC tokens. | pass→pass | 15,117 | 14,555 | -4% | 1 | 1 | 0% | 2,863 | 2,941 | +3% | 0 | 0 | — |