Verifying JSON and TOML changes
Files: .json, .toml. Derived from 8 scanned source repositories and 251 review prompts on https://awesomereviewers.com. Page: https://awesomereviewers.com/verify/config/
How to use this: run every check under Run on every change. Then, for each section under Add when the change touches that describes your diff, run its checks too. Checks catch what a tool can find; then apply the listed review prompts for what tools miss (fetch each prompt’s raw URL).
Usage is the share of scanned repositories in this language that run the tool. A missing tool means no scanned repository runs one the scanner recognises: fall back to the prompts.
Run on every change
- Formatting:
prettier (75% of repos). Command seen: prettier --check docker-compose.yml docker-compose.override.yml. Autofixes. Exit codes: 0 everything formatted; 1 something was not formatted (–check); 2 prettier error. Docs: https://prettier.io/docs/cli#exit-codes
- Linting — no tool detected in the sample. Catches: Bug-prone patterns, unused code and conventions the formatter does not cover.
- Type checking — no tool detected in the sample. Catches: Wrong types, unhandled null or None, call signatures broken across modules.
- Unit and integration tests — no tool detected in the sample. Catches: Behaviour regressions on the paths the tests exercise.
Review prompts (37 in total, most discussed first):
- Consistent naming standards — home-assistant/core, Naming Conventions
- Identifier Naming Rules — Azure/Azure-Sentinel, Naming Conventions
- Maintain consistent terminology patterns — RooCodeInc/Roo-Code, Naming Conventions
- Consistent placeholder conventions — appwrite/appwrite, Naming Conventions
- Consistent localization formatting — RooCodeInc/Roo-Code, Code Style
- Deterministic Resource Naming — Azure/azure-quickstart-templates, Naming Conventions
- arm escaping and diff hygiene — Azure/Azure-Sentinel, Code Style
- Follow established conventions — helix-editor/helix, Code Style
- Consistent naming patterns — n8n-io/n8n, Naming Conventions
- Consistent technical term translation — apache/airflow, Naming Conventions
- Consistent ARM Json Formatting — Azure/azure-quickstart-templates, Code Style
- consistent naming conventions — helix-editor/helix, Naming Conventions
Add when the change touches
- Security scanning:
codeql (50% of repos). Runs via GitHub Action github/codeql-action/analyze. Alternatives: semgrep (12%). Docs: https://github.com/github/codeql
- Secret scanning — no tool detected in the sample. Catches: Credentials and tokens committed to the repository.
- Dependency audit:
dependency-review (25% of repos). Runs via GitHub Action actions/dependency-review-action. Docs: https://github.com/actions/dependency-review-action
Review prompts (23 in total, most discussed first):
- Parameterize security commands — prowler-cloud/prowler, Security
- Align RBAC and Identity — Azure/Azure-Sentinel, Security
- Strict auth schema validation — maximhq/bifrost, Security
- Azure encryption property names — bridgecrewio/checkov, Security
- Use correct encryption properties — bridgecrewio/checkov, Security
- Audit dependency lifecycle scripts — can1357/oh-my-pi, Security
- Secure-by-default integrations — awslabs/aidlc-workflows, Security
- File-Based Command Safety — bmad-code-org/bmad-method, Security
- Secure extension install — aaif-goose/goose, Security
- Narrow secret allowlists — CLINE/CLINE, Security
- Scope secret-scan allowlists narrowly — cline/cline, Security
- trust server-side validation — home-assistant/core, Security
Public APIs, signatures, error paths, nullability
- Type checking — no tool detected in the sample. Catches: Wrong types, unhandled null or None, call signatures broken across modules.
- Unit and integration tests — no tool detected in the sample. Catches: Behaviour regressions on the paths the tests exercise.
- Property-based tests — no tool detected in the sample. Catches: Edge-case inputs nobody wrote a test for; invariants over generated data.
Review prompts (17 in total, most discussed first):
- Use Stable API Versions — Azure/Azure-Sentinel, API
- Null Safety Patterns — Azure/Azure-Sentinel, Null Handling
- Explicit API Contracts — Azure/azure-quickstart-templates, API
- Null and Omission Safety — maximhq/bifrost, Null Handling
- API documentation consistency — home-assistant/core, API
- Avoid empty placeholders — Azure/azure-quickstart-templates, Null Handling
- API identifier consistency — juspay/hyperswitch, API
- OpenAPI spec compliance — appwrite/appwrite, API
- API Config Consistency — aaif-goose/goose, API
- Graceful config validation — maximhq/bifrost, Error Handling
- Config Contract Validation — maximhq/bifrost, API
- API Contract Verification — infiniflow/ragflow, API
Service and framework code
- Unit and integration tests — no tool detected in the sample. Catches: Behaviour regressions on the paths the tests exercise.
- Version and platform matrix:
ci-matrix (38% of repos). Command seen: analyze (language: 1). Docs: https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/run-job-variations
- Property-based tests — no tool detected in the sample. Catches: Edge-case inputs nobody wrote a test for; invariants over generated data.
- Fuzzing — no tool detected in the sample. Catches: Crashes, panics and hangs on malformed input, especially in parsers and decoders.
- Mutation testing — no tool detected in the sample. Catches: Tests that keep passing whatever the code does.
- Proofs and specifications — no tool detected in the sample. Catches: Design-level bugs in protocols and algorithms, checked against a specification.
Review prompts (2 in total, most discussed first):
Threads, async code, locks, shared state
- Concurrency model checking — no tool detected in the sample. Catches: Races and orderings that fail only under specific interleavings.
- Undefined-behaviour detection — no tool detected in the sample. Catches: Memory-safety and aliasing violations in unsafe code.
- Property-based tests — no tool detected in the sample. Catches: Edge-case inputs nobody wrote a test for; invariants over generated data.
Network calls, retries, timeouts, protocols
- Unit and integration tests — no tool detected in the sample. Catches: Behaviour regressions on the paths the tests exercise.
- Fuzzing — no tool detected in the sample. Catches: Crashes, panics and hangs on malformed input, especially in parsers and decoders.
Review prompts (1 in total, most discussed first):
UI components and pages
- End-to-end browser tests — no tool detected in the sample. Catches: User flows broken across components, routing and the network.
- Linting — no tool detected in the sample. Catches: Bug-prone patterns, unused code and conventions the formatter does not cover.
Review prompts (1 in total, most discussed first):
Databases, migrations, caching
- Unit and integration tests — no tool detected in the sample. Catches: Behaviour regressions on the paths the tests exercise.
- Version and platform matrix:
ci-matrix (38% of repos). Command seen: analyze (language: 1). Docs: https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/run-job-variations
Review prompts (5 in total, most discussed first):
Model, prompt and LLM code
- Unit and integration tests — no tool detected in the sample. Catches: Behaviour regressions on the paths the tests exercise.
Review prompts (9 in total, most discussed first):
CI workflows and configuration files
- CI workflow linting — no tool detected in the sample. Catches: Broken GitHub Actions syntax, script injection, over-broad token permissions.
- File hygiene:
pre-commit-hooks (25% of repos). Runs via pre-commit hook check-json. Autofixes. Docs: https://github.com/pre-commit/pre-commit-hooks
Review prompts (135 in total, most discussed first):
- Dependency version ranges — Expressjs/Express, Configurations
- Consistent dependency config — tanstack/query, Configurations
- Validate Block JSON — freeCodeCamp/freeCodeCamp, CI/CD
- Environment-Driven Parameters — Azure/azure-quickstart-templates, Configurations
- Config schema conventions — p-e-w/heretic, Configurations
- Dependency version specification — TanStack/router, Configurations
- dependency classification standards — prisma/prisma, Configurations
- dependency version constraints — cloudflare/workers-sdk, Configurations
- Config Scope And Hygiene — the-pr-agent/pr-agent, Configurations
- Stable dependency version management — appwrite/appwrite, Configurations
- Standardize dependency version notation — expressjs/express, Configurations
- dependency constraint consistency — python-poetry/poetry, Configurations
Dependencies and lockfiles
- Dependency audit:
dependency-review (25% of repos). Runs via GitHub Action actions/dependency-review-action. Docs: https://github.com/actions/dependency-review-action
- Lockfile consistency — no tool detected in the sample. Catches: A lockfile that no longer matches its manifest.
- Version and platform matrix:
ci-matrix (38% of repos). Command seen: analyze (language: 1). Docs: https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/run-job-variations
The tests themselves
- Mutation testing — no tool detected in the sample. Catches: Tests that keep passing whatever the code does.
- Version and platform matrix:
ci-matrix (38% of repos). Command seen: analyze (language: 1). Docs: https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/run-job-variations
Review prompts (13 in total, most discussed first):
- Type-Safe, Scripted Tests — tanstack/query, Testing
- manage testing dependencies — python-poetry/poetry, Testing
- document test configurations — jj-vcs/jj, Testing
- Avoid skipping e2e tests — vitessio/vitess, Testing
- Precise testing dependency versioning — laravel/framework, Testing
- comprehensive test validation — TanStack/router, Testing
- organize test scripts properly — remix-run/react-router, Testing
- Cross-platform test management — maplibre/maplibre-native, Testing
- Use descriptive testing names — cypress-io/cypress, Testing
- Test template defaults — Azure/azure-quickstart-templates, Testing
- Manage testing dependencies — nestjs/nest, Testing
- Test dependency management — nestjs/nest, Testing
- Docs build — no tool detected in the sample. Catches: Broken cross-references, links and markup in documentation.
- Spelling:
codespell (12% of repos). Runs via pre-commit hook codespell. Docs: https://github.com/codespell-project/codespell
Review prompts (8 in total, most discussed first):
Source repositories
home-assistant/core, zed-industries/zed, appwrite/appwrite, juspay/hyperswitch, bytedance/UI-TARS-desktop, Azure/azure-quickstart-templates, the-pr-agent/pr-agent, Azure/Azure-Sentinel