{"slug":"config","title":"JSON and TOML","extensions":[".json",".toml"],"entry_languages":["Json","Toml"],"prompts":251,"repos":8,"sample":[{"repository":"home-assistant/core","slug":"home-assistant-core","checks":12},{"repository":"zed-industries/zed","slug":"zed-industries-zed","checks":9},{"repository":"appwrite/appwrite","slug":"appwrite-appwrite","checks":7},{"repository":"juspay/hyperswitch","slug":"juspay-hyperswitch","checks":8},{"repository":"bytedance/UI-TARS-desktop","slug":"bytedance-ui-tars-desktop","checks":5},{"repository":"Azure/azure-quickstart-templates","slug":"azure-azure-quickstart-templates","checks":0},{"repository":"the-pr-agent/pr-agent","slug":"the-pr-agent-pr-agent","checks":7},{"repository":"Azure/Azure-Sentinel","slug":"azure-azure-sentinel","checks":6}],"tools":[{"id":"prettier","method":"formatting","kind":"formatting","languages":["javascript","typescript","yaml","config","docs"],"upstream":"https://github.com/prettier/prettier","docs":"https://prettier.io/docs/cli#exit-codes","autofix":true,"exit_codes":{"0":"everything formatted","1":"something was not formatted (--check)","2":"prettier error"},"repos":6,"share":75,"commands":["prettier --check docker-compose.yml docker-compose.override.yml","prettier --config .prettierrc . --check","prettier --config .prettierrc . --write"],"run":"prettier --check docker-compose.yml docker-compose.override.yml","via":"pre-commit hook prettier","triggers":["pre_commit","local"],"examples":[{"repository":"home-assistant/core","slug":"home-assistant-core"},{"repository":"zed-industries/zed","slug":"zed-industries-zed"},{"repository":"appwrite/appwrite","slug":"appwrite-appwrite"},{"repository":"juspay/hyperswitch","slug":"juspay-hyperswitch"},{"repository":"bytedance/UI-TARS-desktop","slug":"bytedance-ui-tars-desktop"},{"repository":"Azure/Azure-Sentinel","slug":"azure-azure-sentinel"}]},{"id":"codeql","method":"static_analysis","kind":"security-scanning","languages":["*"],"upstream":"https://github.com/github/codeql","docs":null,"autofix":false,"exit_codes":{},"repos":4,"share":50,"commands":["uses github/codeql-action/analyze"],"run":null,"via":"GitHub Action github/codeql-action/analyze","triggers":["ci"],"examples":[{"repository":"home-assistant/core","slug":"home-assistant-core"},{"repository":"appwrite/appwrite","slug":"appwrite-appwrite"},{"repository":"the-pr-agent/pr-agent","slug":"the-pr-agent-pr-agent"},{"repository":"Azure/Azure-Sentinel","slug":"azure-azure-sentinel"}]},{"id":"ci-matrix","method":"testing","kind":"version-matrix","languages":["*"],"upstream":"https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/run-job-variations","docs":null,"autofix":false,"exit_codes":{},"repos":3,"share":38,"commands":["analyze (include: 1)","analyze (language: 1)","analyze (language: 5)"],"run":"analyze (language: 1)","via":null,"triggers":["ci"],"examples":[{"repository":"appwrite/appwrite","slug":"appwrite-appwrite"},{"repository":"the-pr-agent/pr-agent","slug":"the-pr-agent-pr-agent"},{"repository":"Azure/Azure-Sentinel","slug":"azure-azure-sentinel"}]},{"id":"dependency-review","method":"supply_chain","kind":"dependency-audit","languages":["*"],"upstream":"https://github.com/actions/dependency-review-action","docs":null,"autofix":false,"exit_codes":{},"repos":2,"share":25,"commands":["uses actions/dependency-review-action"],"run":null,"via":"GitHub Action actions/dependency-review-action","triggers":["ci"],"examples":[{"repository":"home-assistant/core","slug":"home-assistant-core"},{"repository":"zed-industries/zed","slug":"zed-industries-zed"}]},{"id":"pre-commit-hooks","method":"formatting","kind":"file-hygiene","languages":["*"],"upstream":"https://github.com/pre-commit/pre-commit-hooks","docs":null,"autofix":true,"exit_codes":{},"repos":2,"share":25,"commands":["pre-commit hook check-json","pre-commit hook check-added-large-files","pre-commit hook check-ast"],"run":null,"via":"pre-commit hook check-json","triggers":["pre_commit","ci"],"examples":[{"repository":"home-assistant/core","slug":"home-assistant-core"},{"repository":"the-pr-agent/pr-agent","slug":"the-pr-agent-pr-agent"}]},{"id":"codespell","method":"formatting","kind":"spelling","languages":["*"],"upstream":"https://github.com/codespell-project/codespell","docs":null,"autofix":false,"exit_codes":{},"repos":1,"share":12,"commands":["pre-commit hook codespell"],"run":null,"via":"pre-commit hook codespell","triggers":["pre_commit"],"examples":[{"repository":"home-assistant/core","slug":"home-assistant-core"}]},{"id":"semgrep","method":"static_analysis","kind":"security-scanning","languages":["*"],"upstream":"https://github.com/semgrep/semgrep","docs":null,"autofix":false,"exit_codes":{},"repos":1,"share":12,"commands":["semgrep scan --config .semgrep --metrics=off --exclude .semgrep --json --output semgrep.json src/Appwrite app/controllers app/init","semgrep scan --config .semgrep --metrics=off --exclude .semgrep --sarif --output semgrep.sarif src/Appwrite app/controllers app/init","semgrep test .semgrep"],"run":"semgrep scan --config .semgrep --metrics=off --exclude .semgrep --json --output semgrep.json src/Appwrite app/controllers app/init","via":null,"triggers":["ci"],"examples":[{"repository":"appwrite/appwrite","slug":"appwrite-appwrite"}]}],"headline":["prettier"],"raw_md":"https://awesomereviewers.com/raw/verify/config.md","raw_json":"https://awesomereviewers.com/raw/verify/config.json","url":"https://awesomereviewers.com/verify/config/","baseline":{"slug":"every-change","title":"Any change","topics":["Code Style","Naming Conventions"],"checks":[{"kind":"formatting","title":"Formatting","method":"formatting","method_slug":"formatting","catches":"Layout drift that buries the real change in the diff.","tool":{"id":"prettier","method":"formatting","kind":"formatting","languages":["javascript","typescript","yaml","config","docs"],"upstream":"https://github.com/prettier/prettier","docs":"https://prettier.io/docs/cli#exit-codes","autofix":true,"exit_codes":{"0":"everything formatted","1":"something was not formatted (--check)","2":"prettier error"},"repos":6,"share":75,"commands":["prettier --check docker-compose.yml docker-compose.override.yml","prettier --config .prettierrc . --check","prettier --config .prettierrc . --write"],"run":"prettier --check docker-compose.yml docker-compose.override.yml","via":"pre-commit hook prettier","triggers":["pre_commit","local"],"examples":[{"repository":"home-assistant/core","slug":"home-assistant-core"},{"repository":"zed-industries/zed","slug":"zed-industries-zed"},{"repository":"appwrite/appwrite","slug":"appwrite-appwrite"},{"repository":"juspay/hyperswitch","slug":"juspay-hyperswitch"},{"repository":"bytedance/UI-TARS-desktop","slug":"bytedance-ui-tars-desktop"},{"repository":"Azure/Azure-Sentinel","slug":"azure-azure-sentinel"}]},"alternatives":[],"note":null},{"kind":"linting","title":"Linting","method":"static_analysis","method_slug":"static-analysis","catches":"Bug-prone patterns, unused code and conventions the formatter does not cover.","tool":null,"alternatives":[],"note":null},{"kind":"type-checking","title":"Type checking","method":"static_analysis","method_slug":"static-analysis","catches":"Wrong types, unhandled null or None, call signatures broken across modules.","tool":null,"alternatives":[],"note":null},{"kind":"unit-tests","title":"Unit and integration tests","method":"testing","method_slug":"testing","catches":"Behaviour regressions on the paths the tests exercise.","tool":null,"alternatives":[],"note":null}],"prompts":[{"slug":"core-consistent-naming-standards","title":"Consistent naming standards","description":"Ensure all user-facing strings follow Home Assistant's naming conventions for consistency and proper internationalization. This includes using sentence-case for translatable strings, proper spelling and capitalization of technical terms, and leveraging common string references where available.","repository":"home-assistant/core","domain":"app-frameworks","topic":"Naming Conventions","language":"Json","updated":"2025-07-27","comments":14,"stars":80450,"raw":"https://awesomereviewers.com/raw/core-consistent-naming-standards.md"},{"slug":"azure-sentinel-identifier-naming-rules","title":"Identifier Naming Rules","description":"Use a single, deterministic naming scheme for every content identifier, and follow the validator’s allowed formats. Apply these rules: 1) Follow exact format/allowed-value rules for metadata/ids","repository":"Azure/Azure-Sentinel","domain":"cloud-infra","topic":"Naming Conventions","language":"Json","updated":"2026-07-28","comments":11,"stars":6042,"raw":"https://awesomereviewers.com/raw/azure-sentinel-identifier-naming-rules.md"},{"slug":"roo-code-maintain-consistent-terminology-patterns","title":"Maintain consistent terminology patterns","description":"Ensure consistent terminology usage across the codebase, especially in localization files and technical documentation. When a term is established (whether in translation or technical context), maintain that same term throughout related files and contexts.","repository":"RooCodeInc/Roo-Code","domain":"ai-agents","topic":"Naming Conventions","language":"Json","updated":"2025-07-23","comments":7,"stars":17288,"raw":"https://awesomereviewers.com/raw/roo-code-maintain-consistent-terminology-patterns.md"},{"slug":"appwrite-consistent-placeholder-conventions","title":"Consistent placeholder conventions","description":"Ensure all placeholders in localization files follow consistent naming conventions to prevent runtime errors and text leakage in the UI. This applies to both sprintf-style placeholders (`%s`) and template variables (`{% raw %}{{name}}{% endraw %}`).","repository":"appwrite/appwrite","domain":"app-frameworks","topic":"Naming Conventions","language":"Json","updated":"2025-07-21","comments":7,"stars":51959,"raw":"https://awesomereviewers.com/raw/appwrite-consistent-placeholder-conventions.md"},{"slug":"roo-code-consistent-localization-formatting","title":"Consistent localization formatting","description":"Ensure all localization strings maintain consistent formatting patterns within each locale file. This includes: 1. **Terminal punctuation**: All similar messages should consistently end with appropriate punctuation marks for the locale (periods in English/French, \"।\" in Hindi, etc.).","repository":"RooCodeInc/Roo-Code","domain":"ai-agents","topic":"Code Style","language":"Json","updated":"2025-07-10","comments":7,"stars":17288,"raw":"https://awesomereviewers.com/raw/roo-code-consistent-localization-formatting.md"},{"slug":"azure-quickstart-templates-deterministic-resource-naming","title":"Deterministic Resource Naming","description":"Use deterministic, semantically correct identifiers for ARM template parameters and resource names—especially where idempotency and uniqueness are required.","repository":"Azure/azure-quickstart-templates","domain":"cloud-infra","topic":"Naming Conventions","language":"Json","updated":"2024-05-07","comments":7,"stars":14846,"raw":"https://awesomereviewers.com/raw/azure-quickstart-templates-deterministic-resource-naming.md"},{"slug":"azure-sentinel-arm-escaping-and-diff-hygiene","title":"arm escaping and diff hygiene","description":"When editing Azure Sentinel solution artifacts (ARM templates + nested CCF connector templates), treat ARM escaping and packaging output as correctness-critical formatting:","repository":"Azure/Azure-Sentinel","domain":"cloud-infra","topic":"Code Style","language":"Json","updated":"2026-07-13","comments":6,"stars":6042,"raw":"https://awesomereviewers.com/raw/azure-sentinel-arm-escaping-and-diff-hygiene.md"},{"slug":"helix-follow-established-conventions","title":"Follow established conventions","description":"Configuration settings should align with official language documentation and established community standards rather than arbitrary personal preferences. This applies to indentation styles, formatter configurations, and syntax requirements.","repository":"helix-editor/helix","domain":"devtools","topic":"Code Style","language":"Toml","updated":"2025-03-12","comments":5,"stars":39026,"raw":"https://awesomereviewers.com/raw/helix-follow-established-conventions.md"},{"slug":"n8n-consistent-naming-patterns","title":"Consistent naming patterns","description":"Maintain consistent naming conventions throughout the codebase to improve readability and maintainability. This applies to translation keys, command names, variables, and terminology.","repository":"n8n-io/n8n","domain":"ai-agents","topic":"Naming Conventions","language":"Json","updated":"2025-07-23","comments":4,"stars":122978,"raw":"https://awesomereviewers.com/raw/n8n-consistent-naming-patterns.md"},{"slug":"airflow-consistent-technical-term-translation","title":"Consistent technical term translation","description":"When localizing an application, maintain consistent conventions for technical terms while respecting language-specific rules: 1. For acronyms, follow the target language''s capitalization conventions:","repository":"apache/airflow","domain":"orchestration","topic":"Naming Conventions","language":"Json","updated":"2025-06-29","comments":4,"stars":40858,"raw":"https://awesomereviewers.com/raw/airflow-consistent-technical-term-translation.md"},{"slug":"azure-quickstart-templates-consistent-arm-json-formatting","title":"Consistent ARM Json Formatting","description":"For ARM templates, enforce deterministic JSON formatting and standardized property ordering to keep diffs small and templates readable. **Rules** 1. **Keep property order consistent**: follow the Azure “sort order of properties” guidance (move keys to the expected order).","repository":"Azure/azure-quickstart-templates","domain":"cloud-infra","topic":"Code Style","language":"Json","updated":"2025-05-09","comments":4,"stars":14846,"raw":"https://awesomereviewers.com/raw/azure-quickstart-templates-consistent-arm-json-formatting.md"},{"slug":"helix-consistent-naming-conventions","title":"consistent naming conventions","description":"Maintain consistent naming patterns throughout your codebase, following established conventions and ensuring uniformity within the same context. This includes using correct syntax for configuration values, matching case conventions for related identifiers, organizing entries systematically (like alphabetically), and choosing descriptive names that clearly...","repository":"helix-editor/helix","domain":"devtools","topic":"Naming Conventions","language":"Toml","updated":"2025-02-26","comments":4,"stars":39026,"raw":"https://awesomereviewers.com/raw/helix-consistent-naming-conventions.md"}],"prompt_count":37},"changes":[{"slug":"security","title":"Authentication, input handling, secrets, permissions","topics":["Security"],"checks":[{"kind":"security-scanning","title":"Security scanning","method":"static_analysis","method_slug":"static-analysis","catches":"Injection, unsafe APIs and tainted data reaching a sink.","tool":{"id":"codeql","method":"static_analysis","kind":"security-scanning","languages":["*"],"upstream":"https://github.com/github/codeql","docs":null,"autofix":false,"exit_codes":{},"repos":4,"share":50,"commands":["uses github/codeql-action/analyze"],"run":null,"via":"GitHub Action github/codeql-action/analyze","triggers":["ci"],"examples":[{"repository":"home-assistant/core","slug":"home-assistant-core"},{"repository":"appwrite/appwrite","slug":"appwrite-appwrite"},{"repository":"the-pr-agent/pr-agent","slug":"the-pr-agent-pr-agent"},{"repository":"Azure/Azure-Sentinel","slug":"azure-azure-sentinel"}]},"alternatives":[{"id":"semgrep","repos":1,"share":12}],"note":null},{"kind":"secret-scanning","title":"Secret scanning","method":"static_analysis","method_slug":"static-analysis","catches":"Credentials and tokens committed to the repository.","tool":null,"alternatives":[],"note":null},{"kind":"dependency-audit","title":"Dependency audit","method":"supply_chain","method_slug":"supply-chain","catches":"Known-vulnerable or disallowed dependencies and licenses.","tool":{"id":"dependency-review","method":"supply_chain","kind":"dependency-audit","languages":["*"],"upstream":"https://github.com/actions/dependency-review-action","docs":null,"autofix":false,"exit_codes":{},"repos":2,"share":25,"commands":["uses actions/dependency-review-action"],"run":null,"via":"GitHub Action actions/dependency-review-action","triggers":["ci"],"examples":[{"repository":"home-assistant/core","slug":"home-assistant-core"},{"repository":"zed-industries/zed","slug":"zed-industries-zed"}]},"alternatives":[],"note":null}],"prompts":[{"slug":"prowler-parameterize-security-commands","title":"Parameterize security commands","description":"When writing security-related CLI commands or remediation steps, always use standardized parameter placeholders (e.g., `<REGION>`, `<RESOURCE_NAME>`) instead of hardcoded values. This practice ensures commands are adaptable across different environments, prevents implementation errors, and makes security remediation steps more reliable. Properly...","repository":"prowler-cloud/prowler","domain":"security","topic":"Security","language":"Json","updated":"2025-03-11","comments":4,"stars":11834,"raw":"https://awesomereviewers.com/raw/prowler-parameterize-security-commands.md"},{"slug":"azure-sentinel-align-rbac-and-identity","title":"Align RBAC and Identity","description":"When defining permissions or identities in IaC (ARM/CloudFormation/templates), ensure the security configuration matches the actual runtime auth path and the provider’s supported identity types—avoid “declared-but-unused” privileges and avoid “wrong-scope” resources that create authorization or authentication drift.","repository":"Azure/Azure-Sentinel","domain":"cloud-infra","topic":"Security","language":"Json","updated":"2026-06-26","comments":3,"stars":6042,"raw":"https://awesomereviewers.com/raw/azure-sentinel-align-rbac-and-identity.md"},{"slug":"bifrost-strict-auth-schema-validation","title":"Strict auth schema validation","description":"Security-related Helm/config schemas should fail fast on invalid or unintended authentication settings. Apply: - Close security-sensitive objects with `additionalProperties: false` so typos/mistyped fields are rejected at `helm template`/validation time (instead of silently producing insecure runtime behavior).","repository":"maximhq/bifrost","domain":"llm-infra","topic":"Security","language":"Json","updated":"2026-07-21","comments":2,"stars":6862,"raw":"https://awesomereviewers.com/raw/bifrost-strict-auth-schema-validation.md"},{"slug":"checkov-azure-encryption-property-names","title":"Azure encryption property names","description":"When configuring encryption settings for Azure resources in ARM templates, always use the correct property names as documented in the Azure API specifications. Specifically for Azure Compute disks, use `enableDoubleEncryption` instead of `doubleEncryptionEnabled` to configure double encryption. Using incorrect property names can result in security...","repository":"bridgecrewio/checkov","domain":"security","topic":"Security","language":"Json","updated":"2024-07-15","comments":2,"stars":7667,"raw":"https://awesomereviewers.com/raw/checkov-azure-encryption-property-names.md"},{"slug":"checkov-use-correct-encryption-properties","title":"Use correct encryption properties","description":"When configuring security features in Azure ARM templates, always use the correct property names as specified in the Azure documentation. For double encryption of Azure Compute disks, use \"enableDoubleEncryption\" rather than \"doubleEncryptionEnabled\". Using incorrect property names may result in security features not being properly applied, potentially...","repository":"bridgecrewio/checkov","domain":"security","topic":"Security","language":"Json","updated":"2024-07-15","comments":2,"stars":7668,"raw":"https://awesomereviewers.com/raw/checkov-use-correct-encryption-properties.md"},{"slug":"oh-my-pi-audit-dependency-lifecycle-scripts","title":"Audit dependency lifecycle scripts","description":"When restricting which dependencies may run lifecycle (install/postinstall) scripts, explicitly maintain and audit the `trustedDependencies` list, and verify that your CI pipeline actually enforces the intended security behavior rather than silently succeeding. Package managers like Bun will skip untrusted lifecycle scripts by default and still report a...","repository":"can1357/oh-my-pi","domain":"security","topic":"Security","language":"Json","updated":"2026-10-21","comments":1,"stars":37317,"raw":"https://awesomereviewers.com/raw/oh-my-pi-audit-dependency-lifecycle-scripts.md"},{"slug":"aidlc-workflows-secure-by-default-integrations","title":"Secure-by-default integrations","description":"When adding configurable external services/integrations (e.g., registries, MCP servers, plugins), apply security-by-default and supply-chain controls—especially when the integration can access credentials.","repository":"awslabs/aidlc-workflows","domain":"orchestration","topic":"Security","language":"Json","updated":"2026-08-04","comments":1,"stars":3849,"raw":"https://awesomereviewers.com/raw/aidlc-workflows-secure-by-default-integrations.md"},{"slug":"bmad-method-file-based-command-safety","title":"File-Based Command Safety","description":"When invoking CLI/shell or external tools, treat all generated/ingested content (LLM output, web research, imported facts) as untrusted and never embed it directly into command-line strings.","repository":"bmad-code-org/bmad-method","domain":"security","topic":"Security","language":"Toml","updated":"2026-07-22","comments":1,"stars":51859,"raw":"https://awesomereviewers.com/raw/bmad-method-file-based-command-safety.md"},{"slug":"goose-secure-extension-install","title":"Secure extension install","description":"When publishing extension/server install options (especially deep-links or Install buttons), default to a secure-by-default path: require explicit/manual installation for binary-first or otherwise security-sensitive extensions. Only enable an automated install/deeplink if the target is explicitly allowlisted.","repository":"aaif-goose/goose","domain":"ai-agents","topic":"Security","language":"Json","updated":"2026-07-10","comments":1,"stars":51876,"raw":"https://awesomereviewers.com/raw/goose-secure-extension-install.md"},{"slug":"cline-narrow-secret-allowlists","title":"Narrow secret allowlists","description":"When suppressing secret-scan findings (e.g., via gitleaks allowlists), keep exemptions narrowly scoped and verify the suppression boundaries. Use specific rule types and matching criteria (e.g., condition + regexTarget) rather than broad path-based ignores, and confirm that only the intended false positives are ignored while unrelated credentials at the...","repository":"CLINE/CLINE","domain":"ai-agents","topic":"Security","language":"Toml","updated":"2026-07-09","comments":1,"stars":70837,"raw":"https://awesomereviewers.com/raw/cline-narrow-secret-allowlists.md"},{"slug":"cline-scope-secret-scan-allowlists-narrowly","title":"Scope secret-scan allowlists narrowly","description":"When adding exemptions to secret-scanning tools (e.g., gitleaks), avoid broad allowlist patterns that could mask real credentials. Tie each exemption to a specific rule ID and combine match conditions (e.g., condition = AND, regexTarget = match) so only the exact known-safe values (such as synthetic model IDs used in tests) are excluded. After adding an...","repository":"cline/cline","domain":"ai-agents","topic":"Security","language":"Toml","updated":"2026-07-09","comments":1,"stars":70886,"raw":"https://awesomereviewers.com/raw/cline-scope-secret-scan-allowlists-narrowly.md"},{"slug":"core-trust-server-side-validation","title":"trust server-side validation","description":"When integrating with external APIs or services that implement their own input validation, avoid duplicating that validation logic on the client side. Trust the authoritative server's validation mechanisms rather than attempting to replicate them locally.","repository":"home-assistant/core","domain":"app-frameworks","topic":"Security","language":"Json","updated":"2025-07-27","comments":1,"stars":80450,"raw":"https://awesomereviewers.com/raw/core-trust-server-side-validation.md"}],"prompt_count":23},{"slug":"interfaces","title":"Public APIs, signatures, error paths, nullability","topics":["API","Error Handling","Null Handling"],"checks":[{"kind":"type-checking","title":"Type checking","method":"static_analysis","method_slug":"static-analysis","catches":"Wrong types, unhandled null or None, call signatures broken across modules.","tool":null,"alternatives":[],"note":null},{"kind":"unit-tests","title":"Unit and integration tests","method":"testing","method_slug":"testing","catches":"Behaviour regressions on the paths the tests exercise.","tool":null,"alternatives":[],"note":null},{"kind":"property-tests","title":"Property-based tests","method":"testing","method_slug":"testing","catches":"Edge-case inputs nobody wrote a test for; invariants over generated data.","tool":null,"alternatives":[],"note":null}],"prompts":[{"slug":"azure-sentinel-use-stable-api-versions","title":"Use Stable API Versions","description":"When defining or calling APIs (including Azure Sentinel/Microsoft Security connector artifacts), always use a stable, supported `apiVersion` and keep it consistent across all related files. Avoid “preview”/older `apiVersion` values unless there is an explicit, documented need.","repository":"Azure/Azure-Sentinel","domain":"cloud-infra","topic":"API","language":"Json","updated":"2026-07-31","comments":11,"stars":6042,"raw":"https://awesomereviewers.com/raw/azure-sentinel-use-stable-api-versions.md"},{"slug":"azure-sentinel-null-safety-patterns","title":"Null Safety Patterns","description":"When fields or parameters are optional (may be missing, null, or empty-string), code must be defensive so queries/playbooks/parsers don’t fail and so “unknown” stays unknown.","repository":"Azure/Azure-Sentinel","domain":"cloud-infra","topic":"Null Handling","language":"Json","updated":"2026-07-21","comments":7,"stars":6042,"raw":"https://awesomereviewers.com/raw/azure-sentinel-null-safety-patterns.md"},{"slug":"azure-quickstart-templates-explicit-api-contracts","title":"Explicit API Contracts","description":"When authoring templates or clients that call/describe APIs (Graph, resource providers, etc.), treat the “API contract” as a first-class design artifact:","repository":"Azure/azure-quickstart-templates","domain":"cloud-infra","topic":"API","language":"Json","updated":"2026-06-01","comments":7,"stars":14846,"raw":"https://awesomereviewers.com/raw/azure-quickstart-templates-explicit-api-contracts.md"},{"slug":"bifrost-null-and-omission-safety","title":"Null and Omission Safety","description":"When a config field is optional/nullable (or has multiple shapes), never rely on “default” or presence quirks. Make absence vs presence explicit, align schema rules with runtime parsing/normalization, and validate the structural inputs that runtime can actually interpret.","repository":"maximhq/bifrost","domain":"llm-infra","topic":"Null Handling","language":"Json","updated":"2026-07-27","comments":4,"stars":6862,"raw":"https://awesomereviewers.com/raw/bifrost-null-and-omission-safety.md"},{"slug":"core-api-documentation-consistency","title":"API documentation consistency","description":"Ensure all API-related descriptions, field names, and documentation accurately reflect the terminology and specifications used by external service providers. Descriptions should be consistent between code comments, user-facing strings, and external documentation.","repository":"home-assistant/core","domain":"app-frameworks","topic":"API","language":"Json","updated":"2025-07-26","comments":4,"stars":80450,"raw":"https://awesomereviewers.com/raw/core-api-documentation-consistency.md"},{"slug":"azure-quickstart-templates-avoid-empty-placeholders","title":"Avoid empty placeholders","description":"When a parameter/property is optional in an ARM template, don’t represent “missing” with empty objects or empty strings—these can be treated as real values and fail validation or downstream logic.","repository":"Azure/azure-quickstart-templates","domain":"cloud-infra","topic":"Null Handling","language":"Json","updated":"2023-02-09","comments":4,"stars":14846,"raw":"https://awesomereviewers.com/raw/azure-quickstart-templates-avoid-empty-placeholders.md"},{"slug":"hyperswitch-api-identifier-consistency","title":"API identifier consistency","description":"Maintain consistent naming conventions for API identifiers, configuration keys, and payment method types. Use snake_case for all API identifiers to ensure uniformity across the system. This includes payment method types, configuration field names, and connector specifications.","repository":"juspay/hyperswitch","domain":"app-frameworks","topic":"API","language":"Toml","updated":"2025-09-16","comments":3,"stars":34028,"raw":"https://awesomereviewers.com/raw/hyperswitch-api-identifier-consistency.md"},{"slug":"appwrite-openapi-spec-compliance","title":"OpenAPI spec compliance","description":"Ensure all API definitions strictly follow OpenAPI specification standards to maintain compatibility with tooling and clients. This includes: 1. Match default values with their defined types:","repository":"appwrite/appwrite","domain":"app-frameworks","topic":"API","language":"Json","updated":"2025-05-18","comments":3,"stars":51959,"raw":"https://awesomereviewers.com/raw/appwrite-openapi-spec-compliance.md"},{"slug":"goose-api-config-consistency","title":"API Config Consistency","description":"Declarative API/provider configurations must be internally consistent with (a) the canonical identifiers used by the model registry/discovery layer and (b) the request-building logic that actually emits fields for the selected engine/path. This prevents mismatches, silent capability drops, and confusing “it’s configured but doesn’t work” behavior.","repository":"aaif-goose/goose","domain":"ai-agents","topic":"API","language":"Json","updated":"2026-07-28","comments":2,"stars":51876,"raw":"https://awesomereviewers.com/raw/goose-api-config-consistency.md"},{"slug":"bifrost-graceful-config-validation","title":"Graceful config validation","description":"When configuration has conditional dependencies, make the system fail fast only for cases that break invariants (correctness/safety), but allow secure graceful degradation for “optional feature” toggles when prerequisites may be missing.","repository":"maximhq/bifrost","domain":"llm-infra","topic":"Error Handling","language":"Json","updated":"2026-07-21","comments":2,"stars":6862,"raw":"https://awesomereviewers.com/raw/bifrost-graceful-config-validation.md"},{"slug":"bifrost-config-contract-validation","title":"Config Contract Validation","description":"Ensure API configuration endpoints (e.g., `PUT /api/config`) define and enforce a precise request/response contract across schema shape, merge semantics, validation behavior, and persistence.","repository":"maximhq/bifrost","domain":"llm-infra","topic":"API","language":"Json","updated":"2026-07-09","comments":2,"stars":6862,"raw":"https://awesomereviewers.com/raw/bifrost-config-contract-validation.md"},{"slug":"ragflow-api-contract-verification","title":"API Contract Verification","description":"When adding/updating model-to-endpoint configuration, verify it against the provider’s official API docs and enforce the expected request/response contract.","repository":"infiniflow/ragflow","domain":"llm-infra","topic":"API","language":"Json","updated":"2026-05-09","comments":2,"stars":80174,"raw":"https://awesomereviewers.com/raw/ragflow-api-contract-verification.md"}],"prompt_count":17},{"slug":"services","title":"Service and framework code","topics":["Fastify","NestJS","Spring","Axum","Celery","Temporal"],"checks":[{"kind":"unit-tests","title":"Unit and integration tests","method":"testing","method_slug":"testing","catches":"Behaviour regressions on the paths the tests exercise.","tool":null,"alternatives":[],"note":null},{"kind":"version-matrix","title":"Version and platform matrix","method":"testing","method_slug":"testing","catches":"Breakage on a runtime version, OS or feature combination you did not run locally.","tool":{"id":"ci-matrix","method":"testing","kind":"version-matrix","languages":["*"],"upstream":"https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/run-job-variations","docs":null,"autofix":false,"exit_codes":{},"repos":3,"share":38,"commands":["analyze (include: 1)","analyze (language: 1)","analyze (language: 5)"],"run":"analyze (language: 1)","via":null,"triggers":["ci"],"examples":[{"repository":"appwrite/appwrite","slug":"appwrite-appwrite"},{"repository":"the-pr-agent/pr-agent","slug":"the-pr-agent-pr-agent"},{"repository":"Azure/Azure-Sentinel","slug":"azure-azure-sentinel"}]},"alternatives":[],"note":null}],"prompts":[],"prompt_count":0},{"slug":"algorithms","title":"Algorithms, parsers, data transforms","topics":["Algorithms"],"checks":[{"kind":"property-tests","title":"Property-based tests","method":"testing","method_slug":"testing","catches":"Edge-case inputs nobody wrote a test for; invariants over generated data.","tool":null,"alternatives":[],"note":null},{"kind":"fuzzing","title":"Fuzzing","method":"testing","method_slug":"testing","catches":"Crashes, panics and hangs on malformed input, especially in parsers and decoders.","tool":null,"alternatives":[],"note":null},{"kind":"mutation-testing","title":"Mutation testing","method":"testing","method_slug":"testing","catches":"Tests that keep passing whatever the code does.","tool":null,"alternatives":[],"note":null},{"kind":"proofs","title":"Proofs and specifications","method":"formal","method_slug":"formal","catches":"Design-level bugs in protocols and algorithms, checked against a specification.","tool":null,"alternatives":[],"note":null}],"prompts":[{"slug":"herdr-constrain-ui-rule-matching","title":"Constrain UI Rule Matching","description":"When building text-based state detectors (e.g., parsing a live UI/pane), treat each rule like an algorithmic classifier: make matches precise by localizing the search, anchoring invariants, and gating multi-step prompts.","repository":"ogulcancelik/herdr","domain":"app-frameworks","topic":"Algorithms","language":"Toml","updated":"2026-08-09","comments":3,"stars":26924,"raw":"https://awesomereviewers.com/raw/herdr-constrain-ui-rule-matching.md"},{"slug":"omniroute-regex-guardrails-for-filters","title":"Regex Guardrails for Filters","description":"When implementing CLI output filters (regex/pattern matchers), make the match logic algorithmically safe: add explicit bypass guards for structured/machine-readable output and use precise patterns for command variants, then lock behavior with include/exclude regression tests.","repository":"diegosouzapw/OmniRoute","domain":"llm-infra","topic":"Algorithms","language":"Json","updated":"2026-05-28","comments":3,"stars":33162,"raw":"https://awesomereviewers.com/raw/omniroute-regex-guardrails-for-filters.md"}],"prompt_count":2},{"slug":"concurrency","title":"Threads, async code, locks, shared state","topics":["Concurrency"],"checks":[{"kind":"concurrency-model-checking","title":"Concurrency model checking","method":"formal","method_slug":"formal","catches":"Races and orderings that fail only under specific interleavings.","tool":null,"alternatives":[],"note":null},{"kind":"ub-detection","title":"Undefined-behaviour detection","method":"formal","method_slug":"formal","catches":"Memory-safety and aliasing violations in unsafe code.","tool":null,"alternatives":[],"note":null},{"kind":"property-tests","title":"Property-based tests","method":"testing","method_slug":"testing","catches":"Edge-case inputs nobody wrote a test for; invariants over generated data.","tool":null,"alternatives":[],"note":null}],"prompts":[],"prompt_count":0},{"slug":"networking","title":"Network calls, retries, timeouts, protocols","topics":["Networking","Axios"],"checks":[{"kind":"unit-tests","title":"Unit and integration tests","method":"testing","method_slug":"testing","catches":"Behaviour regressions on the paths the tests exercise.","tool":null,"alternatives":[],"note":null},{"kind":"fuzzing","title":"Fuzzing","method":"testing","method_slug":"testing","catches":"Crashes, panics and hangs on malformed input, especially in parsers and decoders.","tool":null,"alternatives":[],"note":null}],"prompts":[{"slug":"azure-quickstart-templates-single-source-network-definitions","title":"Single Source Network Definitions","description":"When authoring ARM/Bicep templates, model networking topology as a single source of truth and avoid redundant resources/dependencies. Apply these rules:","repository":"Azure/azure-quickstart-templates","domain":"cloud-infra","topic":"Networking","language":"Json","updated":"2025-06-05","comments":4,"stars":14846,"raw":"https://awesomereviewers.com/raw/azure-quickstart-templates-single-source-network-definitions.md"}],"prompt_count":1},{"slug":"ui","title":"UI components and pages","topics":["React","Next","Next.js","Vue","Angular"],"checks":[{"kind":"browser-tests","title":"End-to-end browser tests","method":"testing","method_slug":"testing","catches":"User flows broken across components, routing and the network.","tool":null,"alternatives":[],"note":null},{"kind":"linting","title":"Linting","method":"static_analysis","method_slug":"static-analysis","catches":"Bug-prone patterns, unused code and conventions the formatter does not cover.","tool":null,"alternatives":[],"note":null}],"prompts":[{"slug":"query-use-angular-v19-strictness","title":"Use Angular v19+ Strictness","description":"When targeting Angular v19+ (or modernizing to it), align your package peer/dependency baselines and update tsconfig to the corresponding strict compiler settings—then apply the same policy across all Angular examples.","repository":"tanstack/query","domain":"app-frameworks","topic":"Angular","language":"Json","updated":"2026-02-09","comments":5,"stars":49380,"raw":"https://awesomereviewers.com/raw/query-use-angular-v19-strictness.md"}],"prompt_count":1},{"slug":"data","title":"Databases, migrations, caching","topics":["Database","Migrations","Caching"],"checks":[{"kind":"unit-tests","title":"Unit and integration tests","method":"testing","method_slug":"testing","catches":"Behaviour regressions on the paths the tests exercise.","tool":null,"alternatives":[],"note":null},{"kind":"version-matrix","title":"Version and platform matrix","method":"testing","method_slug":"testing","catches":"Breakage on a runtime version, OS or feature combination you did not run locally.","tool":{"id":"ci-matrix","method":"testing","kind":"version-matrix","languages":["*"],"upstream":"https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/run-job-variations","docs":null,"autofix":false,"exit_codes":{},"repos":3,"share":38,"commands":["analyze (include: 1)","analyze (language: 1)","analyze (language: 5)"],"run":"analyze (language: 1)","via":null,"triggers":["ci"],"examples":[{"repository":"appwrite/appwrite","slug":"appwrite-appwrite"},{"repository":"the-pr-agent/pr-agent","slug":"the-pr-agent-pr-agent"},{"repository":"Azure/Azure-Sentinel","slug":"azure-azure-sentinel"}]},"alternatives":[],"note":null}],"prompts":[{"slug":"azure-sentinel-schema-first-dcr-kql","title":"Schema-First DCR KQL","description":"For data connector definitions (DCR + KQL transforms), treat the DCR `streamDeclarations.columns` as the schema contract and ensure KQL transforms match that contract:","repository":"Azure/Azure-Sentinel","domain":"cloud-infra","topic":"Database","language":"Json","updated":"2026-07-29","comments":6,"stars":6042,"raw":"https://awesomereviewers.com/raw/azure-sentinel-schema-first-dcr-kql.md"},{"slug":"azure-sentinel-backcompatible-migration-contract","title":"Backcompatible Migration Contract","description":"When making schema/connector changes that can affect existing customer deployments (e.g., new CCF/CL tables, changed table generation behavior), you must preserve backward compatibility as an explicit migration contract: (1) keep stable customer-facing identifiers, (2) provide a compatibility access layer for both old and new schemas, and (3) validate the...","repository":"Azure/Azure-Sentinel","domain":"cloud-infra","topic":"Migrations","language":"Json","updated":"2026-06-26","comments":4,"stars":6042,"raw":"https://awesomereviewers.com/raw/azure-sentinel-backcompatible-migration-contract.md"},{"slug":"appwrite-version-migration-dependencies-carefully","title":"Version migration dependencies carefully","description":"When updating dependencies for migration-related components or making schema changes, verify compatibility and ensure backward compatibility: 1. For dependency updates:","repository":"appwrite/appwrite","domain":"app-frameworks","topic":"Migrations","language":"Json","updated":"2025-07-21","comments":3,"stars":51959,"raw":"https://awesomereviewers.com/raw/appwrite-version-migration-dependencies-carefully.md"},{"slug":"nanochat-cache-keys-drive-rebuilds","title":"Cache keys drive rebuilds","description":"When using uv to build Python extensions via PEP 517 (e.g., maturin), ensure cache invalidation is keyed to the actual build inputs. Configure `tool.uv.cache-keys` so builds rerun only when the underlying sources for the compiled artifact change—especially Rust sources and Cargo manifests—rather than rebuilding whatever project owns the root...","repository":"karpathy/nanochat","domain":"ml-systems","topic":"Caching","language":"Toml","updated":"2025-10-30","comments":2,"stars":53189,"raw":"https://awesomereviewers.com/raw/nanochat-cache-keys-drive-rebuilds.md"},{"slug":"prowler-enable-database-resilience","title":"Enable database resilience","description":"Always configure appropriate resilience features for database services to ensure data durability and high availability. This includes: 1. **Enable regular backups with sufficient retention periods** for all database clusters to prevent data loss","repository":"prowler-cloud/prowler","domain":"security","topic":"Database","language":"Json","updated":"2025-03-11","comments":2,"stars":11834,"raw":"https://awesomereviewers.com/raw/prowler-enable-database-resilience.md"}],"prompt_count":5},{"slug":"performance","title":"Hot paths and performance","topics":["Performance Optimization"],"checks":[],"prompts":[],"prompt_count":0},{"slug":"ai","title":"Model, prompt and LLM code","topics":["AI","Pytorch"],"checks":[{"kind":"unit-tests","title":"Unit and integration tests","method":"testing","method_slug":"testing","catches":"Behaviour regressions on the paths the tests exercise.","tool":null,"alternatives":[],"note":null}],"prompts":[{"slug":"litellm-ai-model-data-validation","title":"AI model data validation","description":"All AI model configuration parameters must be verified against official provider documentation before merging. This includes token limits, pricing values, provider assignments, model names, and supported features. Incorrect configuration data leads to runtime errors, cost miscalculations, and integration failures.","repository":"BerriAI/litellm","domain":"llm-infra","topic":"AI","language":"Json","updated":"2025-08-10","comments":11,"stars":28310,"raw":"https://awesomereviewers.com/raw/litellm-ai-model-data-validation.md"},{"slug":"pr-agent-bound-llm-budgets","title":"Bound LLM Budgets","description":"When configuring generative AI for code-review workflows, keep prompts and model behaviors tightly bounded to control latency/cost while preserving quality.","repository":"the-pr-agent/pr-agent","domain":"ai-agents","topic":"AI","language":"Toml","updated":"2025-06-18","comments":4,"stars":12523,"raw":"https://awesomereviewers.com/raw/pr-agent-bound-llm-budgets.md"},{"slug":"jan-model-description-accuracy","title":"model description accuracy","description":"Ensure AI model descriptions are specific, capability-focused, and avoid marketing language or temporal references like \"latest\". Descriptions should clearly communicate what the model excels at and its intended use cases to help users make informed selection decisions.","repository":"menloresearch/jan","domain":"llm-infra","topic":"AI","language":"Json","updated":"2024-04-22","comments":4,"stars":37620,"raw":"https://awesomereviewers.com/raw/jan-model-description-accuracy.md"},{"slug":"langchainjs-ai-dependency-management","title":"AI dependency management","description":"When integrating AI models and language processing libraries, follow these dependency management best practices: 1. Use specific model integration packages instead of general-purpose AI SDKs. For example:","repository":"langchain-ai/langchainjs","domain":"ai-agents","topic":"AI","language":"Json","updated":"2024-11-21","comments":3,"stars":15004,"raw":"https://awesomereviewers.com/raw/langchainjs-ai-dependency-management.md"},{"slug":"goose-validate-model-limits","title":"Validate model limits","description":"When integrating LLM providers, don’t assume the provider’s model spec equals what the specific API endpoint will actually accept. Enforce two checks in your model configuration: (1) set `context_limit` to a safe upper bound that matches the endpoint’s effective cap, and (2) restrict model selection to a curated allowlist of chat-capable models instead of...","repository":"aaif-goose/goose","domain":"ai-agents","topic":"AI","language":"Json","updated":"2026-07-14","comments":2,"stars":51876,"raw":"https://awesomereviewers.com/raw/goose-validate-model-limits.md"},{"slug":"sdk-python-ai-dependency-management","title":"AI dependency management","description":"When integrating AI libraries and SDKs, carefully manage dependencies by pinning versions with upper bounds to prevent breaking changes and minimize scope by implementing simple types locally when possible.","repository":"strands-agents/sdk-python","domain":"ai-agents","topic":"AI","language":"Toml","updated":"2025-09-12","comments":2,"stars":4044,"raw":"https://awesomereviewers.com/raw/sdk-python-ai-dependency-management.md"},{"slug":"sglang-ai-dependency-justification","title":"AI dependency justification","description":"When modifying AI library dependencies, always provide clear justification for version choices, especially when using non-standard sources like git commits or release candidates. This is critical for AI projects where library compatibility and stability directly impact model performance and inference reliability.","repository":"sgl-project/sglang","domain":"llm-infra","topic":"AI","language":"Toml","updated":"2025-07-24","comments":2,"stars":17245,"raw":"https://awesomereviewers.com/raw/sglang-ai-dependency-justification.md"},{"slug":"stagehand-ai-dependency-classification","title":"AI dependency classification","description":"When adding AI/ML libraries to a project, carefully consider whether they belong in `dependencies` or `devDependencies`. Libraries used for examples, experimentation, or development tooling should be classified as `devDependencies` to avoid bloating production bundles. Maintain consistency by avoiding install scripts in package.json for dev-only AI...","repository":"browserbase/stagehand","domain":"ai-agents","topic":"AI","language":"Json","updated":"2025-02-12","comments":2,"stars":16443,"raw":"https://awesomereviewers.com/raw/stagehand-ai-dependency-classification.md"},{"slug":"tokenizers-version-ai-dependencies-appropriately","title":"Version AI dependencies appropriately","description":"When adding or updating dependencies for AI/ML libraries in your project, follow these two key practices: 1. **Set appropriate version constraints** that balance stability with access to improvements. For rapidly evolving AI libraries like HuggingFace Hub, avoid overly restrictive upper bounds that prevent compatible updates, but also avoid excessively...","repository":"huggingface/tokenizers","domain":"ml-systems","topic":"AI","language":"Toml","updated":"2024-06-07","comments":2,"stars":9868,"raw":"https://awesomereviewers.com/raw/tokenizers-version-ai-dependencies-appropriately.md"}],"prompt_count":9},{"slug":"observability","title":"Logging, metrics, tracing","topics":["Logging","Observability"],"checks":[],"prompts":[],"prompt_count":0},{"slug":"ci-config","title":"CI workflows and configuration files","topics":["CI/CD","Configurations"],"checks":[{"kind":"workflow-linting","title":"CI workflow linting","method":"static_analysis","method_slug":"static-analysis","catches":"Broken GitHub Actions syntax, script injection, over-broad token permissions.","tool":null,"alternatives":[],"note":null},{"kind":"file-hygiene","title":"File hygiene","method":"formatting","method_slug":"formatting","catches":"Invalid JSON, YAML or TOML, merge markers, trailing whitespace, oversized files.","tool":{"id":"pre-commit-hooks","method":"formatting","kind":"file-hygiene","languages":["*"],"upstream":"https://github.com/pre-commit/pre-commit-hooks","docs":null,"autofix":true,"exit_codes":{},"repos":2,"share":25,"commands":["pre-commit hook check-json","pre-commit hook check-added-large-files","pre-commit hook check-ast"],"run":null,"via":"pre-commit hook check-json","triggers":["pre_commit","ci"],"examples":[{"repository":"home-assistant/core","slug":"home-assistant-core"},{"repository":"the-pr-agent/pr-agent","slug":"the-pr-agent-pr-agent"}]},"alternatives":[],"note":null}],"prompts":[{"slug":"express-dependency-version-ranges","title":"Dependency version ranges","description":"When editing dependency versions in package.json, follow the team's agreed semver range convention rather than mixing styles ad hoc. Unless there is a specific compatibility reason, prefer caret (`^`) ranges for both dependencies and devDependencies, and update version specifiers in their own dedicated commits/PRs rather than bundling them with unrelated...","repository":"Expressjs/Express","domain":"app-frameworks","topic":"Configurations","language":"Json","updated":"2025-03-10","comments":14,"stars":69580,"raw":"https://awesomereviewers.com/raw/express-dependency-version-ranges.md"},{"slug":"query-consistent-dependency-config","title":"Consistent dependency config","description":"Maintain configuration consistency and compatibility by using a single, intentional strategy for dependency declarations, peer ranges, and script runtimes.","repository":"tanstack/query","domain":"app-frameworks","topic":"Configurations","language":"Json","updated":"2026-04-26","comments":12,"stars":49380,"raw":"https://awesomereviewers.com/raw/query-consistent-dependency-config.md"},{"slug":"freecodecamp-validate-block-json","title":"Validate Block JSON","description":"Ensure every `curriculum/structure/blocks/*.json` file matches the CI-validated schema and constraints. - Remove deprecated/unused fields (e.g., `name`)—CI may reject these.","repository":"freeCodeCamp/freeCodeCamp","domain":"docs","topic":"CI/CD","language":"Json","updated":"2026-04-07","comments":10,"stars":444449,"raw":"https://awesomereviewers.com/raw/freecodecamp-validate-block-json.md"},{"slug":"azure-quickstart-templates-environment-driven-parameters","title":"Environment-Driven Parameters","description":"When a template needs configuration that varies by environment/cloud/region or depends on real resource identifiers, do not hardcode endpoints/locations or fabricate subscription/RG paths. Instead:","repository":"Azure/azure-quickstart-templates","domain":"cloud-infra","topic":"Configurations","language":"Json","updated":"2026-05-13","comments":8,"stars":14846,"raw":"https://awesomereviewers.com/raw/azure-quickstart-templates-environment-driven-parameters.md"},{"slug":"heretic-config-schema-conventions","title":"Config schema conventions","description":"Provide a clear, stable, and discoverable configuration schema. Apply the following rules to all TOML/environment configs: 1) Use self-documenting values","repository":"p-e-w/heretic","domain":"ml-systems","topic":"Configurations","language":"Toml","updated":"2026-01-26","comments":8,"stars":5002,"raw":"https://awesomereviewers.com/raw/heretic-config-schema-conventions.md"},{"slug":"router-dependency-version-specification","title":"Dependency version specification","description":"Ensure proper dependency version specification and compatibility management in package.json files. Use explicit version ranges for peer dependencies to express compatibility constraints, avoid workspace references in examples and published packages, and properly classify dependencies based on usage patterns.","repository":"TanStack/router","domain":"app-frameworks","topic":"Configurations","language":"Json","updated":"2025-08-05","comments":8,"stars":11590,"raw":"https://awesomereviewers.com/raw/router-dependency-version-specification.md"},{"slug":"prisma-dependency-classification-standards","title":"dependency classification standards","description":"Ensure proper classification and versioning of package dependencies in package.json files. Dependencies should be classified based on their usage pattern: use regular `dependencies` for hard requirements that the package cannot function without, and `peerDependencies` for packages that consumers are expected to provide. When specifying version ranges, use...","repository":"prisma/prisma","domain":"data-systems","topic":"Configurations","language":"Json","updated":"2025-06-16","comments":8,"stars":42967,"raw":"https://awesomereviewers.com/raw/prisma-dependency-classification-standards.md"},{"slug":"workers-sdk-dependency-version-constraints","title":"dependency version constraints","description":"Ensure consistent and appropriate dependency version constraints across all package.json files. Use flexible version ranges for peer dependencies to avoid forcing unnecessary upgrades, maintain minimum supported versions that align with project requirements, and keep template dependencies up-to-date for consistency.","repository":"cloudflare/workers-sdk","domain":"cloud-infra","topic":"Configurations","language":"Json","updated":"2025-04-24","comments":8,"stars":3379,"raw":"https://awesomereviewers.com/raw/workers-sdk-dependency-version-constraints.md"},{"slug":"pr-agent-config-scope-and-hygiene","title":"Config Scope And Hygiene","description":"Treat configuration as a product surface: make it correct, discoverable, and safe. Practical rules: 1) Document scope/precedence explicitly: If an override is ineffective for certain commands due to caching/initialization order, state that clearly and point users to the effective setting (global config or env var).","repository":"the-pr-agent/pr-agent","domain":"ai-agents","topic":"Configurations","language":"Toml","updated":"2026-08-10","comments":7,"stars":12523,"raw":"https://awesomereviewers.com/raw/pr-agent-config-scope-and-hygiene.md"},{"slug":"appwrite-stable-dependency-version-management","title":"Stable dependency version management","description":"Always use stable, well-defined version constraints in configuration files to ensure reproducible builds and prevent unexpected behavior. Avoid using development branches for production dependencies.","repository":"appwrite/appwrite","domain":"app-frameworks","topic":"Configurations","language":"Json","updated":"2025-07-20","comments":7,"stars":51959,"raw":"https://awesomereviewers.com/raw/appwrite-stable-dependency-version-management.md"},{"slug":"express-standardize-dependency-version-notation","title":"Standardize dependency version notation","description":"When specifying dependencies in package.json, follow consistent version notation patterns that align with your project''s stability and compatibility requirements:","repository":"expressjs/express","domain":"app-frameworks","topic":"Configurations","language":"Json","updated":"2025-01-15","comments":7,"stars":67300,"raw":"https://awesomereviewers.com/raw/express-standardize-dependency-version-notation.md"},{"slug":"poetry-dependency-constraint-consistency","title":"dependency constraint consistency","description":"Maintain consistent formatting and rationale for dependency version constraints in configuration files. Use caret notation (`^1.0.0`) instead of range notation (`>=1,<2`) for cleaner syntax when specifying compatible version ranges. When constraining to specific Python versions, choose between explicit version strings (`\"3.7\"`) and comparison operators...","repository":"python-poetry/poetry","domain":"devtools","topic":"Configurations","language":"Toml","updated":"2025-01-09","comments":7,"stars":33496,"raw":"https://awesomereviewers.com/raw/poetry-dependency-constraint-consistency.md"}],"prompt_count":135},{"slug":"dependencies","title":"Dependencies and lockfiles","topics":[],"checks":[{"kind":"dependency-audit","title":"Dependency audit","method":"supply_chain","method_slug":"supply-chain","catches":"Known-vulnerable or disallowed dependencies and licenses.","tool":{"id":"dependency-review","method":"supply_chain","kind":"dependency-audit","languages":["*"],"upstream":"https://github.com/actions/dependency-review-action","docs":null,"autofix":false,"exit_codes":{},"repos":2,"share":25,"commands":["uses actions/dependency-review-action"],"run":null,"via":"GitHub Action actions/dependency-review-action","triggers":["ci"],"examples":[{"repository":"home-assistant/core","slug":"home-assistant-core"},{"repository":"zed-industries/zed","slug":"zed-industries-zed"}]},"alternatives":[],"note":null},{"kind":"lockfile-check","title":"Lockfile consistency","method":"supply_chain","method_slug":"supply-chain","catches":"A lockfile that no longer matches its manifest.","tool":null,"alternatives":[],"note":null},{"kind":"version-matrix","title":"Version and platform matrix","method":"testing","method_slug":"testing","catches":"Breakage on a runtime version, OS or feature combination you did not run locally.","tool":{"id":"ci-matrix","method":"testing","kind":"version-matrix","languages":["*"],"upstream":"https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/run-job-variations","docs":null,"autofix":false,"exit_codes":{},"repos":3,"share":38,"commands":["analyze (include: 1)","analyze (language: 1)","analyze (language: 5)"],"run":"analyze (language: 1)","via":null,"triggers":["ci"],"examples":[{"repository":"appwrite/appwrite","slug":"appwrite-appwrite"},{"repository":"the-pr-agent/pr-agent","slug":"the-pr-agent-pr-agent"},{"repository":"Azure/Azure-Sentinel","slug":"azure-azure-sentinel"}]},"alternatives":[],"note":null}],"prompts":[],"prompt_count":0},{"slug":"tests","title":"The tests themselves","topics":["Testing"],"checks":[{"kind":"mutation-testing","title":"Mutation testing","method":"testing","method_slug":"testing","catches":"Tests that keep passing whatever the code does.","tool":null,"alternatives":[],"note":null},{"kind":"version-matrix","title":"Version and platform matrix","method":"testing","method_slug":"testing","catches":"Breakage on a runtime version, OS or feature combination you did not run locally.","tool":{"id":"ci-matrix","method":"testing","kind":"version-matrix","languages":["*"],"upstream":"https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/run-job-variations","docs":null,"autofix":false,"exit_codes":{},"repos":3,"share":38,"commands":["analyze (include: 1)","analyze (language: 1)","analyze (language: 5)"],"run":"analyze (language: 1)","via":null,"triggers":["ci"],"examples":[{"repository":"appwrite/appwrite","slug":"appwrite-appwrite"},{"repository":"the-pr-agent/pr-agent","slug":"the-pr-agent-pr-agent"},{"repository":"Azure/Azure-Sentinel","slug":"azure-azure-sentinel"}]},"alternatives":[],"note":null}],"prompts":[{"slug":"query-type-safe-scripted-tests","title":"Type-Safe, Scripted Tests","description":"Ensure your testing approach covers both runtime behavior and public API types, and that the test scripts you expose are correct, documented, and preserve any packaging-specific smoke checks.","repository":"tanstack/query","domain":"app-frameworks","topic":"Testing","language":"Json","updated":"2026-04-23","comments":3,"stars":49380,"raw":"https://awesomereviewers.com/raw/query-type-safe-scripted-tests.md"},{"slug":"poetry-manage-testing-dependencies","title":"manage testing dependencies","description":"Ensure testing dependencies are properly organized, avoid redundancy, and proactively manage unmaintained packages. Place testing-specific dependencies in the correct dependency groups (e.g., `group.test.dependencies` rather than `group.dev.dependencies`). Before adding new testing libraries, verify that existing dependencies don't already provide the same...","repository":"python-poetry/poetry","domain":"devtools","topic":"Testing","language":"Toml","updated":"2025-01-12","comments":3,"stars":33496,"raw":"https://awesomereviewers.com/raw/poetry-manage-testing-dependencies.md"},{"slug":"jj-document-test-configurations","title":"document test configurations","description":"When modifying test configurations or tooling settings, provide clear explanations of what the changes actually do and why specific options were chosen. Test configuration changes can be confusing without proper context.","repository":"jj-vcs/jj","domain":"devtools","topic":"Testing","language":"Toml","updated":"2025-09-24","comments":2,"stars":21171,"raw":"https://awesomereviewers.com/raw/jj-document-test-configurations.md"},{"slug":"vitess-avoid-skipping-e2e-tests","title":"Avoid skipping e2e tests","description":"Do not use the `skip_e2e` flag to bypass end-to-end tests that fail. Instead, fix the test implementation by providing appropriate test data or modifying the test to make it pass correctly. This maintains the integrity of the test suite and ensures that code changes are properly validated.","repository":"vitessio/vitess","domain":"data-systems","topic":"Testing","language":"Json","updated":"2025-03-20","comments":2,"stars":19815,"raw":"https://awesomereviewers.com/raw/vitess-avoid-skipping-e2e-tests.md"},{"slug":"framework-precise-testing-dependency-versioning","title":"Precise testing dependency versioning","description":"When specifying testing library dependencies, always use explicit minimum patch versions rather than development branches or broad version constraints. This practice ensures consistent and reproducible test environments across development, CI systems, and production builds.","repository":"laravel/framework","domain":"app-frameworks","topic":"Testing","language":"Json","updated":"2025-02-07","comments":2,"stars":33763,"raw":"https://awesomereviewers.com/raw/framework-precise-testing-dependency-versioning.md"},{"slug":"router-comprehensive-test-validation","title":"comprehensive test validation","description":"Tests should validate all relevant aspects of the system to ensure comprehensive coverage. This includes incorporating type checking into test execution, validating file operations and generation processes, and ensuring end-to-end functionality works correctly. Different types of tests serve different validation purposes and should be used strategically.","repository":"TanStack/router","domain":"app-frameworks","topic":"Testing","language":"Json","updated":"2024-12-06","comments":2,"stars":11590,"raw":"https://awesomereviewers.com/raw/router-comprehensive-test-validation.md"},{"slug":"react-router-organize-test-scripts-properly","title":"organize test scripts properly","description":"Keep base test scripts generic and create specialized variants for specific workflows. Base scripts like \"test\" should remain simple and flexible, allowing developers to pass additional arguments via CLI. For specialized workflows, create separate scripts with descriptive names.","repository":"remix-run/react-router","domain":"app-frameworks","topic":"Testing","language":"Json","updated":"2024-11-29","comments":2,"stars":55270,"raw":"https://awesomereviewers.com/raw/react-router-organize-test-scripts-properly.md"},{"slug":"maplibre-native-cross-platform-test-management","title":"Cross-platform test management","description":"When working with tests that run across multiple platforms (iOS, Android, etc.), ensure proper configuration and handling of platform-specific issues:","repository":"maplibre/maplibre-native","domain":"app-frameworks","topic":"Testing","language":"Json","updated":"2024-09-12","comments":2,"stars":1411,"raw":"https://awesomereviewers.com/raw/maplibre-native-cross-platform-test-management.md"},{"slug":"cypress-use-descriptive-testing-names","title":"Use descriptive testing names","description":"Ensure all testing-related identifiers, scripts, and messages use clear, descriptive names rather than abbreviations or overly specific terminology. This improves maintainability and reduces confusion for both developers and users.","repository":"cypress-io/cypress","domain":"devtools","topic":"Testing","language":"Json","updated":"2022-04-14","comments":2,"stars":48850,"raw":"https://awesomereviewers.com/raw/cypress-use-descriptive-testing-names.md"},{"slug":"azure-quickstart-templates-test-template-defaults","title":"Test template defaults","description":"When testing a template’s behavior, avoid overriding it with explicit parameter values. Remove parameter values from the parameters file so the template’s `defaultValue(s)` are used, ensuring the default-path is actually exercised.","repository":"Azure/azure-quickstart-templates","domain":"cloud-infra","topic":"Testing","language":"Json","updated":"2022-03-28","comments":2,"stars":14846,"raw":"https://awesomereviewers.com/raw/azure-quickstart-templates-test-template-defaults.md"},{"slug":"nest-manage-testing-dependencies","title":"Manage testing dependencies","description":"Properly manage testing-related dependencies by placing them in devDependencies and regularly auditing them to remove redundant tools. Test-only packages should never appear in regular dependencies, and outdated testing libraries should be removed when newer alternatives are already present in the project.","repository":"nestjs/nest","domain":"app-frameworks","topic":"Testing","language":"Json","updated":"2020-11-22","comments":2,"stars":71766,"raw":"https://awesomereviewers.com/raw/nest-manage-testing-dependencies.md"},{"slug":"nest-test-dependency-management","title":"Test dependency management","description":"Testing tools and libraries should be placed in `devDependencies` rather than regular dependencies in package.json. Regularly review testing dependencies to identify and remove outdated or redundant packages. For example, if a newer testing tool now includes functionality previously provided by a separate package (like 'nyc' now depending on...","repository":"nestjs/nest","domain":"app-frameworks","topic":"Testing","language":"Json","updated":"2020-11-22","comments":2,"stars":71767,"raw":"https://awesomereviewers.com/raw/nest-test-dependency-management.md"}],"prompt_count":13},{"slug":"docs","title":"Documentation and comments","topics":["Documentation"],"checks":[{"kind":"docs-build","title":"Docs build","method":"static_analysis","method_slug":"static-analysis","catches":"Broken cross-references, links and markup in documentation.","tool":null,"alternatives":[],"note":null},{"kind":"spelling","title":"Spelling","method":"formatting","method_slug":"formatting","catches":"Typos in identifiers, comments and docs.","tool":{"id":"codespell","method":"formatting","kind":"spelling","languages":["*"],"upstream":"https://github.com/codespell-project/codespell","docs":null,"autofix":false,"exit_codes":{},"repos":1,"share":12,"commands":["pre-commit hook codespell"],"run":null,"via":"pre-commit hook codespell","triggers":["pre_commit"],"examples":[{"repository":"home-assistant/core","slug":"home-assistant-core"}]},"alternatives":[],"note":null}],"prompts":[{"slug":"roo-code-complete-locale-translations","title":"Complete locale translations","description":"Ensure that all text strings in locale-specific files are properly translated into their respective languages. Leaving untranslated English text in non-English locale files creates an inconsistent user experience and reduces the effectiveness of localization efforts.","repository":"RooCodeInc/Roo-Code","domain":"ai-agents","topic":"Documentation","language":"Json","updated":"2025-07-22","comments":25,"stars":17288,"raw":"https://awesomereviewers.com/raw/roo-code-complete-locale-translations.md"},{"slug":"azure-sentinel-document-packaging-conventions","title":"Document Packaging Conventions","description":"When updating Sentinel solution documentation artifacts (workbooks metadata, UI definitions, and connector table schemas), treat them as schema- and regeneration-driven. Ensure values match platform conventions and that any generated text will be correct after regeneration.","repository":"Azure/Azure-Sentinel","domain":"cloud-infra","topic":"Documentation","language":"Json","updated":"2026-07-21","comments":7,"stars":6042,"raw":"https://awesomereviewers.com/raw/azure-sentinel-document-packaging-conventions.md"},{"slug":"azure-quickstart-templates-in-code-documentation-consistency","title":"In-code Documentation Consistency","description":"Ensure any developer-facing documentation embedded in the codebase (template metadata, links, and sample deployment instructions) is complete, unambiguous, portable, and consistent with the repository layout.","repository":"Azure/azure-quickstart-templates","domain":"cloud-infra","topic":"Documentation","language":"Json","updated":"2023-02-22","comments":5,"stars":14846,"raw":"https://awesomereviewers.com/raw/azure-quickstart-templates-in-code-documentation-consistency.md"},{"slug":"core-consistent-documentation-language","title":"Consistent documentation language","description":"Maintain consistency in wording, formatting, and specificity across all documentation strings to improve readability and translation quality. Key practices:","repository":"home-assistant/core","domain":"app-frameworks","topic":"Documentation","language":"Json","updated":"2025-07-26","comments":4,"stars":80450,"raw":"https://awesomereviewers.com/raw/core-consistent-documentation-language.md"},{"slug":"react-router-complete-accurate-documentation","title":"Complete accurate documentation","description":"Documentation should provide complete, accurate guidance that doesn't mislead developers about correct usage patterns. Avoid documentation structures that suggest incorrect import paths or API usage, and ensure that configuration examples are accompanied by practical usage demonstrations.","repository":"remix-run/react-router","domain":"app-frameworks","topic":"Documentation","language":"Json","updated":"2025-07-22","comments":2,"stars":55270,"raw":"https://awesomereviewers.com/raw/react-router-complete-accurate-documentation.md"},{"slug":"airflow-natural-language-translations","title":"Natural language translations","description":"When providing translations for user interface elements and documentation, prioritize natural and idiomatic expressions in the target language rather than literal translations. Consider the grammatical rules and cultural context of each language to ensure the translated text sounds native to users.","repository":"apache/airflow","domain":"orchestration","topic":"Documentation","language":"Json","updated":"2025-06-28","comments":2,"stars":40858,"raw":"https://awesomereviewers.com/raw/airflow-natural-language-translations.md"},{"slug":"appwrite-prevent-api-documentation-duplication","title":"Prevent API documentation duplication","description":"When maintaining API specification files (like OpenAPI or Swagger), ensure consistency and avoid duplication that can confuse documentation generators and API consumers:","repository":"appwrite/appwrite","domain":"app-frameworks","topic":"Documentation","language":"Json","updated":"2025-05-18","comments":2,"stars":51959,"raw":"https://awesomereviewers.com/raw/appwrite-prevent-api-documentation-duplication.md"},{"slug":"langchainjs-update-documentation-configuration","title":"Update documentation configuration","description":"When adding new files or components to the project, ensure that documentation configuration is updated accordingly. This includes adding new files to TypeDoc options in tsconfig.json to maintain complete API documentation coverage. Additionally, clearly mark deprecated components and direct developers to use the recommended alternatives instead of extending...","repository":"langchain-ai/langchainjs","domain":"ai-agents","topic":"Documentation","language":"Json","updated":"2024-05-17","comments":2,"stars":15004,"raw":"https://awesomereviewers.com/raw/langchainjs-update-documentation-configuration.md"}],"prompt_count":8}]}