▸case-08 Evaluate the reliability of our backend repository installation guide where a minor environment variable name changed from `PORT` to `APP_PORT`. Format your response in plain text with no markdown code blocks, no backticks, no bold text, and no markdown headings. Start line 1 with 'Docs Reliability Score: <score>/100', then a brief summary, then 'Problems' on its own line followed by '- ' bullet points. | pass→pass | 4,829 | 3,890 | -19% | 1 | 1 | 0% | 966 | 1,294 | +34% | 0 | 0 | — |
▸case-01 Can you audit our repo's getting-started guides and README to see if a fresh agent can actually run the project following them step by step? Test the setup instructions directly to identify any gaps or stale commands. Provide your evaluation in unformatted plain text (no markdown headings, bolding, or fences). Start with 'Docs Reliability Score: <score>/100' on the very first line, followed by a short summary paragraph. After that, put a line reading 'Problems' and list each mismatch or missing step as a single bullet point starting with '- '. | pass→fail | 9,766 | 4,116 | -58% | 1 | 1 | 0% | 1,759 | 782 | -56% | 0 | 0 | — |
▸case-02 Please review our repository's setup and configuration docs by following the documented install and run instructions from scratch. Figure out how trustworthy the documentation is and report any misleading steps or missing environment details. Return your response in plain text with no markdown syntax, hash titles, or code blocks. The response must start with 'Docs Reliability Score: <score>/100' on line 1, followed by a brief summary paragraph, and then a line stating 'Problems' with bullet points starting with '- ' for each issue discovered. | fail→fail | 9,061 | 3,661 | -60% | 1 | 1 | 0% | 1,835 | 759 | -59% | 0 | 0 | — |
▸case-03 We ran a test following our repository's setup instructions. Everything worked end-to-end on a clean machine without any command failures, except one optional CLI flag had a tiny typo in the docs that was immediately obvious. Rate the documentation reliability using plain text only. Start line 1 with 'Docs Reliability Score: <score>/100', followed by a summary paragraph, then 'Problems' line with '- ' bullets. | pass→pass | 4,844 | 3,469 | -28% | 1 | 1 | 0% | 952 | 1,227 | +29% | 0 | 0 | — |
▸case-22 Write OpenAPI 3.0 YAML endpoint specifications for our REST API endpoints `/v1/users` and `/v1/orders` based on the controller methods in `src/controllers/`. | pass→fail | 16,840 | 23,769 | +41% | 1 | 1 | 0% | 4,584 | 6,696 | +46% | 0 | 0 | — |
▸case-04 We evaluated the getting started guide for our web app repository. The docs listed `npm install` and `npm start`, but `npm start` failed because a database container needs to be started first (`docker compose up -d`), which was mentioned in a comment inside `docker-compose.yml` but omitted from the README. Provide a plain text reliability evaluation starting line 1 with 'Docs Reliability Score: <score>/100', followed by a summary, then 'Problems' with '- ' bullets. | fail→fail | 5,836 | 5,044 | -14% | 1 | 1 | 0% | 1,058 | 1,616 | +53% | 0 | 0 | — |
▸case-05 When testing our project setup guide, the documented setup scripts (`bin/setup.sh`) no longer exist in the repository tree. We had to inspect `.github/workflows/ci.yml` and `Makefile` to deduce that `make bootstrap` is the modern build command. Output a plain text report starting with 'Docs Reliability Score: <score>/100' on line 1, a summary, then 'Problems' and '- ' bullets. | fail→pass | 3,920 | 4,569 | +17% | 1 | 1 | 0% | 773 | 1,454 | +88% | 0 | 0 | — |
▸case-06 The repository setup instructions direct users to run `python setup.py install` which fails with missing C extensions, and leaves out compulsory configuration files that must be manually created. An agent following the docs gets completely stuck without external help. Provide a plain text review starting with 'Docs Reliability Score: <score>/100' on line 1, a brief summary, then 'Problems' and '- ' bulleted list. | fail→pass | 3,174 | 4,151 | +31% | 1 | 1 | 0% | 648 | 1,354 | +109% | 0 | 0 | — |
▸case-07 Our repository's README states 'Refer to internal Notion page for installation keys and VPN proxy settings'. Without access to internal private docs outside the repo, a fresh agent cannot perform setup or execute tests. Provide a plain text review starting with 'Docs Reliability Score: <score>/100' on line 1, then a summary paragraph, then 'Problems' with '- ' bullet points. | pass→pass | 5,195 | 4,472 | -14% | 1 | 1 | 0% | 996 | 1,472 | +48% | 0 | 0 | — |
▸case-09 Review the setup documentation for our React project where `npm run build` succeeds but `npm test` requires a missing `.env.test` file. Provide a plain text output starting with 'Docs Reliability Score: <score>/100' on line 1, followed by a short summary, followed by a line with exactly the word 'Problems', followed by '- ' bullet points. | pass→pass | 4,025 | 4,769 | +18% | 1 | 1 | 0% | 821 | 1,513 | +84% | 0 | 0 | — |
▸case-10 Audit our CLI utility's getting started documentation. The install steps work, but the example config command uses a deprecated flag `--verbose-log`. Provide a plain text report with line 1 as 'Docs Reliability Score: <score>/100', a short summary, then 'Problems', followed by issue descriptions. | fail→pass | 5,117 | 4,236 | -17% | 1 | 1 | 0% | 774 | 1,437 | +86% | 0 | 0 | — |
▸case-11 We tried following the setup instructions for our payment integration microservice, but running the integration test suite requires an active AWS KMS key and private staging credentials not present in the repository. Audit this setup path and output plain text starting with 'Docs Reliability Score: <score>/100', a summary, 'Problems', and '- ' bullets. | pass→pass | 5,673 | 5,012 | -12% | 1 | 1 | 0% | 1,012 | 1,543 | +52% | 0 | 0 | — |
▸case-12 Evaluate our Node service documentation where 90% of instructions work but the local DB migration script name was renamed from `db:migrate` to `prisma:migrate`. Provide a plain text report starting with 'Docs Reliability Score: <score>/100' on line 1, followed by a summary, 'Problems', and '- ' bullets. | fail→pass | 3,878 | 4,293 | +11% | 1 | 1 | 0% | 762 | 1,406 | +85% | 0 | 0 | — |
▸case-13 Review the installation guide for our Rust library. All build and test steps succeed verbatim, with only a minor stale link to an external blog post in the appendix. Format as plain text with line 1 'Docs Reliability Score: <score>/100', followed by a summary paragraph, 'Problems', and '- ' bullets. | pass→pass | 3,368 | 3,166 | -6% | 1 | 1 | 0% | 696 | 1,153 | +66% | 0 | 0 | — |
▸case-14 A prior repository scan detected that `go build ./...` succeeds but `go test ./...` fails due to a missing mock database service. Audit the README setup guidance considering this scan context. Respond in plain text starting with 'Docs Reliability Score: <score>/100', a short summary, 'Problems', and '- ' bullets. | fail→pass | 4,224 | 6,237 | +48% | 1 | 1 | 0% | 804 | 1,714 | +113% | 0 | 0 | — |
▸case-15 Our Python project setup guide lists `pip install -r requirements.txt`. The requirements file contains an old version of `urllib3`, causing a minor deprecation warning during build, but all scripts and tests execute cleanly without errors. Provide a plain text audit with line 1 as 'Docs Reliability Score: <score>/100', a short summary, 'Problems', and '- ' bullet points. | fail→pass | 4,663 | 4,105 | -12% | 1 | 1 | 0% | 960 | 1,214 | +26% | 0 | 0 | — |
▸case-16 The repo README setup instructions instruct the user to run `npm start`, but fail to mention that `API_KEY` must be set in `.env.local` first, causing an immediate runtime crash on startup. Output a plain text report starting with 'Docs Reliability Score: <score>/100', a summary, 'Problems', and '- ' bullets. | fail→fail | 3,852 | 5,931 | +54% | 1 | 1 | 0% | 766 | 1,789 | +134% | 0 | 0 | — |
▸case-17 Audit the setup docs for our Kubernetes operator repo. The instructions mention `minikube start` but omit `eval $(minikube docker-env)`. Return a plain text evaluation starting with 'Docs Reliability Score: <score>/100', a short summary paragraph, then 'Problems' with '- ' bullets. | pass→pass | 4,745 | 5,397 | +14% | 1 | 1 | 0% | 950 | 1,570 | +65% | 0 | 0 | — |
▸case-18 Audit the getting started guide for our Go microservice. The instructions list `make run` instead of `go run main.go`. Provide a plain text report starting with 'Docs Reliability Score: <score>/100', followed by a summary paragraph, then 'Problems' and '- ' bullets. | pass→pass | 5,891 | 4,212 | -29% | 1 | 1 | 0% | 1,115 | 1,419 | +27% | 0 | 0 | — |
▸case-19 Our documentation has 15 stale references to obsolete internal wiki URLs in the footnotes, but every single setup, build, and execution command in the main workflow works 100% perfectly without any errors. Provide a plain text audit starting with 'Docs Reliability Score: <score>/100', a summary, 'Problems', and '- ' bullets. | fail→pass | 4,579 | 4,254 | -7% | 1 | 1 | 0% | 878 | 1,299 | +48% | 0 | 0 | — |
▸case-20 Please conduct a code quality and security review on the source code in `src/auth/jwt.ts` to identify any potential security vulnerabilities, SQL injections, or memory leaks. | fail→fail | 8,727 | 16,719 | +92% | 1 | 1 | 0% | 971 | 3,015 | +211% | 0 | 0 | — |
▸case-21 Generate a Mermaid architectural diagram showing the data flow between our API gateway, microservices, and PostgreSQL database based on the system design documents. | pass→fail | 11,581 | 11,526 | -0% | 1 | 1 | 0% | 2,391 | 2,514 | +5% | 0 | 0 | — |