▸case-01 We are configuring Spectral for our REST API schemas. We want to strictly require that every HTTP operation (GET, POST, etc.) includes an explicit description field, but we keep getting warnings instead of build failures. How do we override this specific rule in .spectral.yaml to enforce it as an error? | pass→pass | 6,577 | 7,028 | +7% | 1 | 1 | 0% | 1,154 | 1,315 | +14% | 0 | 0 | — |
▸case-02 We use npm-package-json-lint in our CI workflow. We need to ensure that package.json always contains a non-empty description string, overriding the default optional setting. What exact rule configuration key should be added to .npmpackagejsonlintrc.json? | pass→pass | 3,830 | 3,561 | -7% | 1 | 1 | 0% | 804 | 656 | -18% | 0 | 0 | — |
▸case-03 Our codebase passes general flake8 checks, but developers keep committing public Python modules without docstring descriptions. Which specific pydocstyle error code corresponds to a missing docstring in a public module so we can enable it in setup.cfg? | pass→pass | 4,444 | 5,093 | +15% | 1 | 1 | 0% | 942 | 1,025 | +9% | 0 | 0 | — |
▸case-04 When building container images for our OCI-compliant registry, security audits flag that our Dockerfiles lack the standard annotation describing the container's purpose. What exact OCI annotation key should be added in a LABEL instruction in the Dockerfile? | pass→pass | 3,217 | 2,529 | -21% | 1 | 1 | 0% | 594 | 508 | -14% | 0 | 0 | — |
▸case-05 We are running TFlint on our infrastructure code. TFlint flags input variables defined in variables.tf that lack a description field. We want to enable this built-in rule in .tflint.hcl so CI fails if any variable lacks documentation. Which rule name in the terraform plugin enables this check? | pass→pass | 2,551 | 2,410 | -6% | 1 | 1 | 0% | 522 | 504 | -3% | 0 | 0 | — |
▸case-06 In our data engineering repository, we use pre-commit hooks with dbt-checkpoint to enforce documentation standards on schema.yml. We want pre-commit to block commits if any dbt model is missing its description entry. Which pre-commit hook ID from dbt-checkpoint performs this validation? | pass→pass | 3,358 | 2,530 | -25% | 1 | 1 | 0% | 660 | 469 | -29% | 0 | 0 | — |
▸case-07 When running cargo publish in our Rust workspace, Cargo raises a warning about missing metadata in Cargo.toml. Where in Cargo.toml must the description key be defined? | pass→pass | 4,686 | 4,674 | -0% | 1 | 1 | 0% | 896 | 995 | +11% | 0 | 0 | — |
▸case-08 We use @graphql-eslint/eslint-plugin to lint our GraphQL schema files. We want to enforce that all object types, interface fields, and enums have description comments or strings. Which ESLint rule provided by this plugin enforces required descriptions? | pass→pass | 4,406 | 3,514 | -20% | 1 | 1 | 0% | 907 | 724 | -20% | 0 | 0 | — |
▸case-09 Our team uses gh pr create in automated scripts, but PRs are being created without descriptions because developers omit the prompt interaction. We want the CLI command to supply text from a file without opening an editor. Which flag passed to gh pr create inputs the PR description from a file? | pass→pass | 2,721 | 3,102 | +14% | 1 | 1 | 0% | 493 | 548 | +11% | 0 | 0 | — |
▸case-10 Our protobuf repository uses Buf CLI to lint .proto files. We want buf lint to enforce that every protobuf service and field has comments documenting its purpose. Which standard lint rule category in buf.yaml enables required comment checks? | pass→pass | 4,642 | 3,908 | -16% | 1 | 1 | 0% | 864 | 859 | -1% | 0 | 0 | — |
▸case-11 Running helm lint on a custom Helm chart produces a warning that metadata is missing from Chart.yaml. What key in Chart.yaml stores the single-sentence human-readable description of the chart required by Helm standards? | pass→pass | 2,421 | 1,911 | -21% | 1 | 1 | 0% | 468 | 392 | -16% | 0 | 0 | — |
▸case-12 We want ESLint to report functions where JSDoc comments exist but lack a text description before parameter tags. Which rule in eslint-plugin-jsdoc enforces that JSDoc blocks include a description? | pass→pass | 3,955 | 3,257 | -18% | 1 | 1 | 0% | 713 | 700 | -2% | 0 | 0 | — |
▸case-13 When building Sphinx documentation using make html, Sphinx ignores missing target references and missing documentation warnings by default. What option in conf.py forces Sphinx to run in nit-picky mode, warning about all missing references? | pass→pass | 2,958 | 3,141 | +6% | 1 | 1 | 0% | 543 | 540 | -1% | 0 | 0 | — |
▸case-14 When defining a CustomResourceDefinition in Kubernetes under spec.versions[].schema.openAPIV3Schema, kubectl dry-run passes, but OpenAPI validators complain about missing property documentation. Where in the JSON schema tree for a spec property should the description string be attached? | pass→pass | 9,426 | 7,929 | -16% | 1 | 1 | 0% | 1,901 | 1,533 | -19% | 0 | 0 | — |
▸case-15 We use Checkstyle in our Java Maven build. We want Checkstyle to fail if a public method has a Javadoc block that lacks a main description text before @param tags. Which Checkstyle module checks for method Javadoc descriptions? | fail→fail | 16,195 | 12,135 | -25% | 1 | 1 | 0% | 3,030 | 2,305 | -24% | 0 | 0 | — |
▸case-16 In our OpenAPI 3.0 specification, the root info object contains title and version, but Spectral reports that high-level API documentation is missing. Which default Spectral rule checks for the description in the info object? | pass→pass | 3,391 | 3,020 | -11% | 1 | 1 | 0% | 657 | 629 | -4% | 0 | 0 | — |
▸case-17 We run sphinx-build in GitHub Actions to generate API docs from Python docstrings. We want the build step to fail with exit code 1 if Sphinx encounters any warnings about missing docstrings or broken references. Which command-line flag passed to sphinx-build turns all warnings into errors? | pass→pass | 2,385 | 2,866 | +20% | 1 | 1 | 0% | 426 | 605 | +42% | 0 | 0 | — |
▸case-18 When building Swift package documentation with swift package generate-documentation, we want compiler warnings about missing doc comments on public APIs to fail the CI build. Which option converts documentation build warnings into errors? | pass→pass | 6,180 | 4,523 | -27% | 1 | 1 | 0% | 1,196 | 899 | -25% | 0 | 0 | — |
▸case-19 In a Rust crate, we want cargo check to issue compiler warnings for any public struct, enum, or function missing a /// doc comment description. What inner attribute should be added to the top of src/lib.rs? | pass→pass | 2,838 | 2,927 | +3% | 1 | 1 | 0% | 524 | 535 | +2% | 0 | 0 | — |
▸case-20 We need to update the version number of our library in package.json from 1.2.0 to 1.3.0 following semantic versioning rules for a new feature addition. Which field in package.json should be updated? | pass→pass | 1,606 | 1,489 | -7% | 1 | 1 | 0% | 293 | 232 | -21% | 0 | 0 | — |
▸case-21 Our legal team requires us to declare our open-source software license as MIT in package.json. Which standard field name in package.json specifies the project license? | pass→pass | 2,051 | 1,649 | -20% | 1 | 1 | 0% | 314 | 307 | -2% | 0 | 0 | — |
▸case-22 Our OpenAPI spec file openapi.json has valid schema content but inconsistent indentation. We want to reformat openapi.json in place with standard formatting using Prettier. What command performs this formatting? | fail→pass | 2,362 | 1,554 | -34% | 1 | 1 | 0% | 441 | 281 | -36% | 0 | 0 | — |
▸case-23 We use pydocstyle to enforce Python docstrings. Which specific pydocstyle error code corresponds to a missing docstring in a public class definition? | pass→pass | 2,328 | 1,663 | -29% | 1 | 1 | 0% | 526 | 332 | -37% | 0 | 0 | — |
▸case-24 In npm-package-json-lint, we want to enforce that the description string in package.json ends with a period. Which rule name configures description punctuation? | pass→pass | 7,279 | 4,228 | -42% | 1 | 1 | 0% | 1,559 | 801 | -49% | 0 | 0 | — |
▸case-25 In Terraform, when declaring an output block in outputs.tf, we want to document what the output value represents for module consumers. Which attribute inside the output block provides this explanation? | pass→pass | 1,981 | 1,814 | -8% | 1 | 1 | 0% | 372 | 333 | -10% | 0 | 0 | — |