{"slug":"docs","title":"Markdown and docs","extensions":[".md",".mdx",".rst",".txt"],"entry_languages":["Markdown","Txt"],"prompts":694,"repos":61,"sample":[{"repository":"freeCodeCamp/freeCodeCamp","slug":"freecodecamp-freecodecamp","checks":6},{"repository":"EbookFoundation/free-programming-books","slug":"ebookfoundation-free-programming-books","checks":0},{"repository":"kamranahmedse/developer-roadmap","slug":"kamranahmedse-developer-roadmap","checks":2},{"repository":"ossu/computer-science","slug":"ossu-computer-science","checks":0},{"repository":"avelino/awesome-go","slug":"avelino-awesome-go","checks":1},{"repository":"iptv-org/iptv","slug":"iptv-org-iptv","checks":3},{"repository":"30-seconds/30-seconds-of-code","slug":"30-seconds-30-seconds-of-code","checks":4},{"repository":"electron/electron","slug":"electron-electron","checks":5},{"repository":"nodejs/node","slug":"nodejs-node","checks":8},{"repository":"langflow-ai/langflow","slug":"langflow-ai-langflow","checks":14},{"repository":"angular/angular","slug":"angular-angular","checks":4},{"repository":"mui/material-ui","slug":"mui-material-ui","checks":6},{"repository":"ant-design/ant-design","slug":"ant-design-ant-design","checks":6},{"repository":"neovim/neovim","slug":"neovim-neovim","checks":2},{"repository":"fastapi/fastapi","slug":"fastapi-fastapi","checks":7},{"repository":"django/django","slug":"django-django","checks":6},{"repository":"sveltejs/svelte","slug":"sveltejs-svelte","checks":5},{"repository":"microsoft/playwright","slug":"microsoft-playwright","checks":4},{"repository":"vitejs/vite","slug":"vitejs-vite","checks":5},{"repository":"elastic/elasticsearch","slug":"elastic-elasticsearch","checks":1},{"repository":"astral-sh/uv","slug":"astral-sh-uv","checks":11},{"repository":"prometheus/prometheus","slug":"prometheus-prometheus","checks":10},{"repository":"nuxt/nuxt","slug":"nuxt-nuxt","checks":8},{"repository":"rails/rails","slug":"rails-rails","checks":1},{"repository":"warpdotdev/warp","slug":"warpdotdev-warp","checks":6},{"repository":"traefik/traefik","slug":"traefik-traefik","checks":10},{"repository":"bmad-code-org/bmad-method","slug":"bmad-code-org-bmad-method","checks":7},{"repository":"prettier/prettier","slug":"prettier-prettier","checks":6},{"repository":"tanstack/query","slug":"tanstack-query","checks":4},{"repository":"serverless/serverless","slug":"serverless-serverless","checks":6},{"repository":"colinhacks/zod","slug":"colinhacks-zod","checks":4},{"repository":"astral-sh/ruff","slug":"astral-sh-ruff","checks":20},{"repository":"helix-editor/helix","slug":"helix-editor-helix","checks":7},{"repository":"logseq/logseq","slug":"logseq-logseq","checks":5},{"repository":"gofiber/fiber","slug":"gofiber-fiber","checks":6},{"repository":"vlang/v","slug":"vlang-v","checks":2},{"repository":"vadimdemedes/ink","slug":"vadimdemedes-ink","checks":3},{"repository":"BerriAI/litellm","slug":"berriai-litellm","checks":24},{"repository":"vercel-labs/agent-skills","slug":"vercel-labs-agent-skills","checks":0},{"repository":"opentofu/opentofu","slug":"opentofu-opentofu","checks":5},{"repository":"anthropics/claude-code","slug":"anthropics-claude-code","checks":1},{"repository":"pydantic/pydantic","slug":"pydantic-pydantic","checks":14},{"repository":"QwenLM/Qwen3","slug":"qwenlm-qwen3","checks":0},{"repository":"Tencent/ncnn","slug":"tencent-ncnn","checks":3},{"repository":"jj-vcs/jj","slug":"jj-vcs-jj","checks":9},{"repository":"github/docs","slug":"github-docs","checks":6},{"repository":"argoproj/argo-cd","slug":"argoproj-argo-cd","checks":11},{"repository":"apache/apisix","slug":"apache-apisix","checks":3},{"repository":"SWE-agent/SWE-agent","slug":"swe-agent-swe-agent","checks":6},{"repository":"astral-sh/ty","slug":"astral-sh-ty","checks":10},{"repository":"TanStack/router","slug":"tanstack-router","checks":6},{"repository":"awslabs/mcp","slug":"awslabs-mcp","checks":12},{"repository":"tensorflow/swift","slug":"tensorflow-swift","checks":0},{"repository":"Azure/azure-sdk-for-net","slug":"azure-azure-sdk-for-net","checks":4},{"repository":"volcano-sh/volcano","slug":"volcano-sh-volcano","checks":3},{"repository":"Azure/azure-powershell","slug":"azure-azure-powershell","checks":1},{"repository":"awslabs/aidlc-workflows","slug":"awslabs-aidlc-workflows","checks":6},{"repository":"google-gemini/gemini-skills","slug":"google-gemini-gemini-skills","checks":0},{"repository":"cloudflare/workers-sdk","slug":"cloudflare-workers-sdk","checks":5},{"repository":"open-telemetry/opentelemetry-python","slug":"open-telemetry-opentelemetry-python","checks":9},{"repository":"getsentry/sentry-php","slug":"getsentry-sentry-php","checks":0}],"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":27,"share":44,"commands":["prettier --write .","prettier --cache --check .","prettier --cache -w ."],"run":"prettier --write .","via":"pre-commit hook prettier","triggers":["pre_commit","ci","local"],"examples":[{"repository":"freeCodeCamp/freeCodeCamp","slug":"freecodecamp-freecodecamp"},{"repository":"kamranahmedse/developer-roadmap","slug":"kamranahmedse-developer-roadmap"},{"repository":"iptv-org/iptv","slug":"iptv-org-iptv"},{"repository":"30-seconds/30-seconds-of-code","slug":"30-seconds-30-seconds-of-code"},{"repository":"angular/angular","slug":"angular-angular"},{"repository":"mui/material-ui","slug":"mui-material-ui"}]},{"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":25,"share":41,"commands":["analyze (language: 2)","analyze (language: 1)","Tests (include: 5)"],"run":"analyze (language: 2)","via":null,"triggers":["ci"],"examples":[{"repository":"30-seconds/30-seconds-of-code","slug":"30-seconds-30-seconds-of-code"},{"repository":"nodejs/node","slug":"nodejs-node"},{"repository":"langflow-ai/langflow","slug":"langflow-ai-langflow"},{"repository":"sveltejs/svelte","slug":"sveltejs-svelte"},{"repository":"microsoft/playwright","slug":"microsoft-playwright"},{"repository":"vitejs/vite","slug":"vitejs-vite"}]},{"id":"codeql","method":"static_analysis","kind":"security-scanning","languages":["*"],"upstream":"https://github.com/github/codeql","docs":null,"autofix":false,"exit_codes":{},"repos":14,"share":23,"commands":["uses github/codeql-action/analyze"],"run":null,"via":"GitHub Action github/codeql-action/analyze","triggers":["ci"],"examples":[{"repository":"nodejs/node","slug":"nodejs-node"},{"repository":"langflow-ai/langflow","slug":"langflow-ai-langflow"},{"repository":"mui/material-ui","slug":"mui-material-ui"},{"repository":"neovim/neovim","slug":"neovim-neovim"},{"repository":"prometheus/prometheus","slug":"prometheus-prometheus"},{"repository":"nuxt/nuxt","slug":"nuxt-nuxt"}]},{"id":"mkdocs","method":"static_analysis","kind":"docs-build","languages":["python","docs"],"upstream":"https://github.com/mkdocs/mkdocs","docs":null,"autofix":false,"exit_codes":{},"repos":8,"share":13,"commands":["mkdocs build","mkdocs build --strict","mkdocs build --strict -f mkdocs.yml"],"run":"mkdocs build","via":null,"triggers":["ci","local"],"examples":[{"repository":"astral-sh/uv","slug":"astral-sh-uv"},{"repository":"traefik/traefik","slug":"traefik-traefik"},{"repository":"astral-sh/ruff","slug":"astral-sh-ruff"},{"repository":"pydantic/pydantic","slug":"pydantic-pydantic"},{"repository":"jj-vcs/jj","slug":"jj-vcs-jj"},{"repository":"argoproj/argo-cd","slug":"argoproj-argo-cd"}]},{"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":8,"share":13,"commands":["pre-commit hook end-of-file-fixer","pre-commit hook trailing-whitespace","pre-commit hook check-added-large-files"],"run":null,"via":"pre-commit hook end-of-file-fixer","triggers":["pre_commit","ci"],"examples":[{"repository":"langflow-ai/langflow","slug":"langflow-ai-langflow"},{"repository":"fastapi/fastapi","slug":"fastapi-fastapi"},{"repository":"bmad-code-org/bmad-method","slug":"bmad-code-org-bmad-method"},{"repository":"astral-sh/ruff","slug":"astral-sh-ruff"},{"repository":"pydantic/pydantic","slug":"pydantic-pydantic"},{"repository":"SWE-agent/SWE-agent","slug":"swe-agent-swe-agent"}]},{"id":"codespell","method":"formatting","kind":"spelling","languages":["*"],"upstream":"https://github.com/codespell-project/codespell","docs":null,"autofix":false,"exit_codes":{},"repos":5,"share":8,"commands":["codespell","codespell --toml pyproject.toml","codespell --toml pyproject.toml --write"],"run":"codespell","via":"GitHub Action codespell-project/actions-codespell","triggers":["pre_commit","ci","local"],"examples":[{"repository":"langflow-ai/langflow","slug":"langflow-ai-langflow"},{"repository":"gofiber/fiber","slug":"gofiber-fiber"},{"repository":"pydantic/pydantic","slug":"pydantic-pydantic"},{"repository":"jj-vcs/jj","slug":"jj-vcs-jj"},{"repository":"open-telemetry/opentelemetry-python","slug":"open-telemetry-opentelemetry-python"}]},{"id":"semgrep","method":"static_analysis","kind":"security-scanning","languages":["*"],"upstream":"https://github.com/semgrep/semgrep","docs":null,"autofix":false,"exit_codes":{},"repos":5,"share":8,"commands":["semgrep scan --config .semgrep/rules . --error","semgrep scan --config auto --sarif-output semgrep.sarif.json --no-error --dryrun --verbose","semgrep scan --config=auto"],"run":"semgrep scan --oss-only --metrics=off --config=p/typescript --severity=ERROR --error --sarif --output=semgrep.sarif core harness scripts plugins","via":null,"triggers":["ci"],"examples":[{"repository":"vitejs/vite","slug":"vitejs-vite"},{"repository":"BerriAI/litellm","slug":"berriai-litellm"},{"repository":"awslabs/mcp","slug":"awslabs-mcp"},{"repository":"awslabs/aidlc-workflows","slug":"awslabs-aidlc-workflows"},{"repository":"cloudflare/workers-sdk","slug":"cloudflare-workers-sdk"}]},{"id":"coq","method":"formal","kind":"proofs","languages":["*"],"upstream":"https://github.com/rocq-prover/rocq","docs":null,"autofix":false,"exit_codes":{},"repos":2,"share":3,"commands":[],"run":null,"via":null,"triggers":[],"examples":[{"repository":"helix-editor/helix","slug":"helix-editor-helix"},{"repository":"vlang/v","slug":"vlang-v"}]},{"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":3,"commands":["uses actions/dependency-review-action"],"run":null,"via":"GitHub Action actions/dependency-review-action","triggers":["ci"],"examples":[{"repository":"prettier/prettier","slug":"prettier-prettier"},{"repository":"awslabs/mcp","slug":"awslabs-mcp"}]},{"id":"gitleaks","method":"static_analysis","kind":"secret-scanning","languages":["*"],"upstream":"https://github.com/gitleaks/gitleaks","docs":null,"autofix":false,"exit_codes":{},"repos":2,"share":3,"commands":["gitleaks git --config=.gitleaks.toml --baseline-path=.gitleaks-baseline.json --log-opts=$SCAN_REF --report-format=sarif --report-path=gitleaks.sarif .","gitleaks version","pre-commit hook gitleaks"],"run":"gitleaks git --config=.gitleaks.toml --baseline-path=.gitleaks-baseline.json --log-opts=$SCAN_REF --report-format=sarif --report-path=gitleaks.sarif .","via":"pre-commit hook gitleaks","triggers":["pre_commit","ci"],"examples":[{"repository":"awslabs/mcp","slug":"awslabs-mcp"},{"repository":"awslabs/aidlc-workflows","slug":"awslabs-aidlc-workflows"}]},{"id":"sphinx","method":"static_analysis","kind":"docs-build","languages":["python","docs"],"upstream":"https://github.com/sphinx-doc/sphinx","docs":null,"autofix":false,"exit_codes":{},"repos":1,"share":2,"commands":["sphinx-build -E -a -W -b html -T . _build/html"],"run":"sphinx-build -E -a -W -b html -T . _build/html","via":null,"triggers":["ci","local"],"examples":[{"repository":"open-telemetry/opentelemetry-python","slug":"open-telemetry-opentelemetry-python"}]}],"headline":["prettier"],"raw_md":"https://awesomereviewers.com/raw/verify/docs.md","raw_json":"https://awesomereviewers.com/raw/verify/docs.json","url":"https://awesomereviewers.com/verify/docs/","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":27,"share":44,"commands":["prettier --write .","prettier --cache --check .","prettier --cache -w ."],"run":"prettier --write .","via":"pre-commit hook prettier","triggers":["pre_commit","ci","local"],"examples":[{"repository":"freeCodeCamp/freeCodeCamp","slug":"freecodecamp-freecodecamp"},{"repository":"kamranahmedse/developer-roadmap","slug":"kamranahmedse-developer-roadmap"},{"repository":"iptv-org/iptv","slug":"iptv-org-iptv"},{"repository":"30-seconds/30-seconds-of-code","slug":"30-seconds-30-seconds-of-code"},{"repository":"angular/angular","slug":"angular-angular"},{"repository":"mui/material-ui","slug":"mui-material-ui"}]},"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":"free-programming-books-lint-compliant-markdown-links","title":"Lint-Compliant Markdown Links","description":"When adding/updating entries in markdown lists, follow the repository’s lint-safe formatting and platform/link conventions. Checklist: - Escape special markdown characters in titles/labels: use `\\|` instead of `|`.","repository":"EbookFoundation/free-programming-books","domain":"docs","topic":"Code Style","language":"Markdown","updated":"2025-11-07","comments":12,"stars":388003,"raw":"https://awesomereviewers.com/raw/free-programming-books-lint-compliant-markdown-links.md"},{"slug":"azure-powershell-standardize-powershell-naming","title":"Standardize PowerShell Naming","description":"Apply consistent, semantic naming to generated cmdlets, parameters, and help/docs. - Cmdlet verb semantics: name sync operations with `Invoke-*` rather than `Start-*`/job-style verbs.","repository":"Azure/azure-powershell","domain":"cloud-infra","topic":"Naming Conventions","language":"Markdown","updated":"2026-06-25","comments":11,"stars":4762,"raw":"https://awesomereviewers.com/raw/azure-powershell-standardize-powershell-naming.md"},{"slug":"freecodecamp-consistent-snippet-style","title":"Consistent Snippet Style","description":"All code snippets, hints, seed code, and automated checks must follow a single, consistent formatting and style contract—especially around quote usage and basic JS/TS syntax.","repository":"freeCodeCamp/freeCodeCamp","domain":"docs","topic":"Code Style","language":"Markdown","updated":"2026-05-08","comments":8,"stars":444449,"raw":"https://awesomereviewers.com/raw/freecodecamp-consistent-snippet-style.md"},{"slug":"freecodecamp-consistent-identifier-naming","title":"Consistent Identifier Naming","description":"When updating curriculum challenges or UI code, ensure all identifiers are spelled, cased, and named consistently across: the prompt, hints, and what tests/DOM queries expect. Also use framework-correct attribute names (e.g., JSX `className`) and semantic, descriptive labels for user-facing accessibility (e.g., informative `alt` text).","repository":"freeCodeCamp/freeCodeCamp","domain":"docs","topic":"Naming Conventions","language":"Markdown","updated":"2026-05-04","comments":8,"stars":444449,"raw":"https://awesomereviewers.com/raw/freecodecamp-consistent-identifier-naming.md"},{"slug":"prettier-documentation-example-consistency","title":"Documentation example consistency","description":"Ensure all code examples and documentation maintain consistent formatting standards, use descriptive variable names, and apply proper syntax highlighting. This includes using meaningful identifiers instead of cryptic names like `a60`, applying correct language tags for syntax highlighting (e.g., `css` instead of `jsx` for CSS code), and providing clear...","repository":"prettier/prettier","domain":"devtools","topic":"Code Style","language":"Markdown","updated":"2025-02-22","comments":8,"stars":50772,"raw":"https://awesomereviewers.com/raw/prettier-documentation-example-consistency.md"},{"slug":"30-seconds-of-code-readable-es-style","title":"Readable ES style","description":"Use a consistent, readable JavaScript style that favors early exits, standard APIs, and lint-safe expressions—without sacrificing clarity. - Prefer guard clauses: if a branch returns, don’t wrap the rest in `else`.","repository":"30-seconds/30-seconds-of-code","domain":"app-frameworks","topic":"Code Style","language":"Markdown","updated":"2020-09-22","comments":8,"stars":129334,"raw":"https://awesomereviewers.com/raw/30-seconds-of-code-readable-es-style.md"},{"slug":"fastapi-technical-term-consistency","title":"Technical term consistency","description":"When working with multilingual codebases or documentation, maintain consistent naming conventions for technical terms across all languages. Consider the following practices:","repository":"fastapi/fastapi","domain":"app-frameworks","topic":"Naming Conventions","language":"Markdown","updated":"2025-02-28","comments":7,"stars":86871,"raw":"https://awesomereviewers.com/raw/fastapi-technical-term-consistency.md"},{"slug":"pydantic-consistent-term-capitalization","title":"Consistent term capitalization","description":"Follow consistent capitalization rules for technical terms, acronyms, and library names throughout your codebase and documentation: 1. **Capitalize standard acronyms**: Use ''URL'', ''JSON'', ''API'', ''HTML'', ''CSS'', ''Unicode'', etc. rather than lowercase versions.","repository":"pydantic/pydantic","domain":"app-frameworks","topic":"Naming Conventions","language":"Markdown","updated":"2025-01-29","comments":7,"stars":24377,"raw":"https://awesomereviewers.com/raw/pydantic-consistent-term-capitalization.md"},{"slug":"v-clear-technical-writing","title":"Clear technical writing","description":"Ensure technical documentation uses clear, grammatically correct language with consistent formatting when explaining naming conventions and code structure. This includes proper capitalization, precise word choice, consistent code formatting with backticks, and clear sentence structure.","repository":"vlang/v","domain":"runtimes","topic":"Naming Conventions","language":"Markdown","updated":"2024-11-20","comments":7,"stars":36582,"raw":"https://awesomereviewers.com/raw/v-clear-technical-writing.md"},{"slug":"nuxt-use-consistent-terminology","title":"Use consistent terminology","description":"Prioritize consistent, clear, and beginner-friendly terminology throughout your codebase and documentation. Choose names that are intuitive for users rather than technically precise but confusing. Maintain consistency with established patterns and style guidelines.","repository":"nuxt/nuxt","domain":"app-frameworks","topic":"Naming Conventions","language":"Markdown","updated":"2024-10-16","comments":7,"stars":57769,"raw":"https://awesomereviewers.com/raw/nuxt-use-consistent-terminology.md"},{"slug":"ant-design-markdown-formatting-consistency","title":"Markdown formatting consistency","description":"Ensure consistent markdown formatting in documentation by wrapping all technical terms, API names, property names, and code-related content in backticks. This improves readability and maintains visual consistency across documentation.","repository":"ant-design/ant-design","domain":"app-frameworks","topic":"Code Style","language":"Markdown","updated":"2025-09-03","comments":6,"stars":95882,"raw":"https://awesomereviewers.com/raw/ant-design-markdown-formatting-consistency.md"},{"slug":"helix-consistent-descriptive-naming-conventions","title":"Consistent descriptive naming conventions","description":"Use consistent and descriptive naming conventions across the codebase: 1. Use kebab-case for configuration options and snake_case for internal modifiers","repository":"helix-editor/helix","domain":"devtools","topic":"Naming Conventions","language":"Markdown","updated":"2025-06-06","comments":6,"stars":39026,"raw":"https://awesomereviewers.com/raw/helix-consistent-descriptive-naming-conventions.md"}],"prompt_count":82},"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":14,"share":23,"commands":["uses github/codeql-action/analyze"],"run":null,"via":"GitHub Action github/codeql-action/analyze","triggers":["ci"],"examples":[{"repository":"nodejs/node","slug":"nodejs-node"},{"repository":"langflow-ai/langflow","slug":"langflow-ai-langflow"},{"repository":"mui/material-ui","slug":"mui-material-ui"},{"repository":"neovim/neovim","slug":"neovim-neovim"},{"repository":"prometheus/prometheus","slug":"prometheus-prometheus"},{"repository":"nuxt/nuxt","slug":"nuxt-nuxt"}]},"alternatives":[{"id":"semgrep","repos":5,"share":8}],"note":null},{"kind":"secret-scanning","title":"Secret scanning","method":"static_analysis","method_slug":"static-analysis","catches":"Credentials and tokens committed to the repository.","tool":{"id":"gitleaks","method":"static_analysis","kind":"secret-scanning","languages":["*"],"upstream":"https://github.com/gitleaks/gitleaks","docs":null,"autofix":false,"exit_codes":{},"repos":2,"share":3,"commands":["gitleaks git --config=.gitleaks.toml --baseline-path=.gitleaks-baseline.json --log-opts=$SCAN_REF --report-format=sarif --report-path=gitleaks.sarif .","gitleaks version","pre-commit hook gitleaks"],"run":"gitleaks git --config=.gitleaks.toml --baseline-path=.gitleaks-baseline.json --log-opts=$SCAN_REF --report-format=sarif --report-path=gitleaks.sarif .","via":"pre-commit hook gitleaks","triggers":["pre_commit","ci"],"examples":[{"repository":"awslabs/mcp","slug":"awslabs-mcp"},{"repository":"awslabs/aidlc-workflows","slug":"awslabs-aidlc-workflows"}]},"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":3,"commands":["uses actions/dependency-review-action"],"run":null,"via":"GitHub Action actions/dependency-review-action","triggers":["ci"],"examples":[{"repository":"prettier/prettier","slug":"prettier-prettier"},{"repository":"awslabs/mcp","slug":"awslabs-mcp"}]},"alternatives":[],"note":null}],"prompts":[{"slug":"teleport-enforce-scope-boundaries","title":"Enforce scope boundaries","description":"When implementing hierarchical permission systems with scopes, ensure that permissions granted at a specific scope cannot be used to access resources or escalate privileges outside that scope's boundaries. This prevents lateral movement and privilege escalation attacks.","repository":"gravitational/teleport","domain":"security","topic":"Security","language":"Markdown","updated":"2025-09-04","comments":13,"stars":19109,"raw":"https://awesomereviewers.com/raw/teleport-enforce-scope-boundaries.md"},{"slug":"qwen-code-defense-in-depth-security-guardrails","title":"Defense-in-depth Security Guardrails","description":"When handling security-sensitive interactions (authz/ownership, network callbacks, and untrusted execution), apply defense-in-depth at the boundaries: be precise about guarantees, bind authorization to explicit identities at creation time, validate inbound payloads before side effects, and isolate both execution and filesystem writes.","repository":"QwenLM/qwen-code","domain":"ai-agents","topic":"Security","language":"Markdown","updated":"2026-07-29","comments":9,"stars":26407,"raw":"https://awesomereviewers.com/raw/qwen-code-defense-in-depth-security-guardrails.md"},{"slug":"rails-layer-security-defenses","title":"Layer security defenses","description":"Implement multiple layers of security throughout your application rather than relying on a single protection mechanism. This defense-in-depth approach significantly improves your application's security posture.","repository":"rails/rails","domain":"app-frameworks","topic":"Security","language":"Markdown","updated":"2025-07-01","comments":9,"stars":57027,"raw":"https://awesomereviewers.com/raw/rails-layer-security-defenses.md"},{"slug":"docs-untrusted-actions-checkout","title":"Untrusted Actions Checkout","description":"Treat `pull_request_target` and `workflow_run` as *privileged* contexts: if you use them, you must assume any incoming PR code or artifacts are untrusted.","repository":"github/docs","domain":"security","topic":"Security","language":"Markdown","updated":"2025-09-19","comments":6,"stars":21111,"raw":"https://awesomereviewers.com/raw/docs-untrusted-actions-checkout.md"},{"slug":"bmad-method-treat-inputs-as-untrusted","title":"Treat Inputs as Untrusted","description":"Apply a consistent security posture to every workflow/prompt-controlled value and to any derived content that will be rendered or linked: 1) Validate untrusted paths *before* cleanup/normalization","repository":"bmad-code-org/bmad-method","domain":"security","topic":"Security","language":"Markdown","updated":"2026-07-22","comments":5,"stars":51859,"raw":"https://awesomereviewers.com/raw/bmad-method-treat-inputs-as-untrusted.md"},{"slug":"hermes-agent-explicit-trust-and-consent","title":"Explicit Trust and Consent","description":"When a security-related skill or script causes any external effect (sending data to third parties, spending funds, changing auth, or modifying security config), the implementation and docs must be explicit about (a) trust boundaries, (b) user-controlled/bounded authorization, and (c) safe, targeted, verifiable changes.","repository":"nousresearch/hermes-agent","domain":"ai-agents","topic":"Security","language":"Markdown","updated":"2026-07-18","comments":5,"stars":221948,"raw":"https://awesomereviewers.com/raw/hermes-agent-explicit-trust-and-consent.md"},{"slug":"apisix-secure-examples-correctness","title":"Secure examples correctness","description":"When implementing or documenting security-related plugins/features, ensure examples are both *secure* and *operationally correct*: avoid leaking sensitive data, match cookie/transport settings, use the correct authentication header formats, and ensure authentication happens before authorization/restriction.","repository":"apache/apisix","domain":"cloud-infra","topic":"Security","language":"Markdown","updated":"2026-05-15","comments":5,"stars":16922,"raw":"https://awesomereviewers.com/raw/apisix-secure-examples-correctness.md"},{"slug":"fiber-validate-security-configurations","title":"Validate security configurations","description":"Always verify that security middleware configurations use correct constant values, proper parameter specifications, and follow established security practices. Incorrect configuration values can create vulnerabilities or cause security features to fail silently.","repository":"gofiber/fiber","domain":"app-frameworks","topic":"Security","language":"Markdown","updated":"2025-07-19","comments":5,"stars":37560,"raw":"https://awesomereviewers.com/raw/fiber-validate-security-configurations.md"},{"slug":"prowler-secure-authentication-flows","title":"Secure authentication flows","description":"Implement authentication flows that protect sensitive information and follow secure credential management practices: 1. **Prevent domain enumeration attacks** by returning consistent responses regardless of whether the input (like domain name) is valid:","repository":"prowler-cloud/prowler","domain":"security","topic":"Security","language":"Markdown","updated":"2025-05-27","comments":5,"stars":11834,"raw":"https://awesomereviewers.com/raw/prowler-secure-authentication-flows.md"},{"slug":"mcp-secure-auth-and-secrets","title":"Secure Auth and Secrets","description":"Apply these rules whenever implementing auth, tokens, or security-modes: 1) Never leak tokens/secrets - Don’t print full-privilege tokens to stdout, shell history, CI logs, or transcripts.","repository":"awslabs/mcp","domain":"ai-agents","topic":"Security","language":"Markdown","updated":"2026-07-31","comments":4,"stars":9545,"raw":"https://awesomereviewers.com/raw/mcp-secure-auth-and-secrets.md"},{"slug":"warp-secret-and-inert-safety","title":"Secret and Inert Safety","description":"When handling auth secrets, user directory/path-based configuration, or shell-generated code, treat any value that could reveal identity/organization or execute code as *sensitive* and *untrusted by default*.","repository":"warpdotdev/warp","domain":"devtools","topic":"Security","language":"Markdown","updated":"2026-05-08","comments":4,"stars":56893,"raw":"https://awesomereviewers.com/raw/warp-secret-and-inert-safety.md"},{"slug":"argo-cd-explicit-security-controls","title":"explicit security controls","description":"Security configurations should use explicit controls and secure defaults rather than implicit permissions or hardcoded credentials. This principle helps prevent accidental privilege escalation and credential exposure.","repository":"argoproj/argo-cd","domain":"orchestration","topic":"Security","language":"Markdown","updated":"2025-06-17","comments":4,"stars":20149,"raw":"https://awesomereviewers.com/raw/argo-cd-explicit-security-controls.md"}],"prompt_count":70},{"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":"langflow-api-authentication-requirements","title":"API authentication requirements","description":"Ensure all API documentation and code examples include proper authentication headers and clearly explain authentication requirements. As of Langflow v1.5, all API requests require a Langflow API key, even when `AUTO_LOGIN` is enabled. The only exceptions are MCP endpoints (`/v1/mcp`, `/v1/mcp-projects`, `/v2/mcp`) which don't require authentication...","repository":"langflow-ai/langflow","domain":"ai-agents","topic":"API","language":"Markdown","updated":"2025-07-08","comments":19,"stars":111046,"raw":"https://awesomereviewers.com/raw/langflow-api-authentication-requirements.md"},{"slug":"electron-use-extensible-parameter-objects","title":"Use extensible parameter objects","description":"When designing APIs that may need additional parameters in the future, use objects instead of individual parameters to enable extension without breaking changes. This approach allows new properties to be added while maintaining backward compatibility.","repository":"electron/electron","domain":"devtools","topic":"API","language":"Markdown","updated":"2025-07-04","comments":12,"stars":117644,"raw":"https://awesomereviewers.com/raw/electron-use-extensible-parameter-objects.md"},{"slug":"node-idempotent-error-safe-disposers","title":"Idempotent error-safe disposers","description":"When implementing resource cleanup logic, especially disposers for explicit resource management, always design for resilience during error conditions:","repository":"nodejs/node","domain":"runtimes","topic":"Error Handling","language":"Markdown","updated":"2025-06-29","comments":11,"stars":112178,"raw":"https://awesomereviewers.com/raw/node-idempotent-error-safe-disposers.md"},{"slug":"node-evolve-return-values","title":"Evolve return values","description":"When extending APIs with new capabilities, carefully consider how changes to return values affect consumers. Avoid creating polymorphic return types based on input options as this reduces predictability and makes it difficult to programmatically detect supported features.","repository":"nodejs/node","domain":"runtimes","topic":"API","language":"Markdown","updated":"2025-07-11","comments":8,"stars":112178,"raw":"https://awesomereviewers.com/raw/node-evolve-return-values.md"},{"slug":"fastapi-document-all-responses","title":"Document all responses","description":"When designing APIs, thoroughly document all possible responses your endpoints can return, not just the \"happy path\" success cases. Include documentation for:","repository":"fastapi/fastapi","domain":"app-frameworks","topic":"API","language":"Markdown","updated":"2025-03-05","comments":8,"stars":86871,"raw":"https://awesomereviewers.com/raw/fastapi-document-all-responses.md"},{"slug":"azure-powershell-spec-fidelity-directives","title":"Spec fidelity directives","description":"When using AutoRest (or similar) to generate PowerShell/SDK surfaces, enforce that the generated cmdlets and types preserve the intended REST API contract—especially around nullability, required parameters, and unintended extra parameter-set variants.","repository":"Azure/azure-powershell","domain":"cloud-infra","topic":"API","language":"Markdown","updated":"2026-07-10","comments":7,"stars":4762,"raw":"https://awesomereviewers.com/raw/azure-powershell-spec-fidelity-directives.md"},{"slug":"freecodecamp-express-error-handling","title":"Express error handling","description":"For Express apps, standardize error handling as follows: - Define error-handling middleware with the correct signature: `(err, req, res, next)`. - Register it last in the middleware chain (after routes). If you add a 404 handler, place it after routes but before the error handler.","repository":"freeCodeCamp/freeCodeCamp","domain":"docs","topic":"Error Handling","language":"Markdown","updated":"2026-05-08","comments":7,"stars":444449,"raw":"https://awesomereviewers.com/raw/freecodecamp-express-error-handling.md"},{"slug":"query-precise-api-contracts","title":"Precise API Contracts","description":"When designing or documenting API options and callbacks, ensure the contract is exact, unambiguous, and type-safe. - **Specify true behavior and defaults**: If an option affects multiple behaviors, document what it does *exactly* (including defaults). Prefer the control mechanism that precisely matches intent (e.g., stop polling by returning `false` from...","repository":"tanstack/query","domain":"app-frameworks","topic":"API","language":"Markdown","updated":"2026-03-30","comments":7,"stars":49380,"raw":"https://awesomereviewers.com/raw/query-precise-api-contracts.md"},{"slug":"ant-design-api-evolution-strategy","title":"API evolution strategy","description":"When evolving APIs, design for extensibility and provide clear migration paths to maintain backward compatibility while improving developer experience.","repository":"ant-design/ant-design","domain":"app-frameworks","topic":"API","language":"Markdown","updated":"2025-09-02","comments":7,"stars":95882,"raw":"https://awesomereviewers.com/raw/ant-design-api-evolution-strategy.md"},{"slug":"azure-sdk-for-net-design-stable-apis","title":"Design stable APIs","description":"When creating or modifying APIs, carefully consider what becomes part of your public API surface to ensure backward compatibility and consistent developer experience.","repository":"Azure/azure-sdk-for-net","domain":"cloud-infra","topic":"API","language":"Markdown","updated":"2025-07-02","comments":7,"stars":5809,"raw":"https://awesomereviewers.com/raw/azure-sdk-for-net-design-stable-apis.md"},{"slug":"qwen-code-error-semantics-invariants","title":"Error semantics invariants","description":"When handling failures, treat “what happened” as a precise, testable contract—not an interpretation. Ensure (1) classification predicates are exact and consistent across docs+code, (2) failure causes are not overloaded, (3) cleanup/settlement invariants prevent stranded states, and (4) adapter/step contracts are enforced with safe fallbacks.","repository":"QwenLM/qwen-code","domain":"ai-agents","topic":"Error Handling","language":"Markdown","updated":"2026-07-28","comments":6,"stars":26407,"raw":"https://awesomereviewers.com/raw/qwen-code-error-semantics-invariants.md"},{"slug":"qwen-code-typed-api-contracts","title":"Typed API Contracts","description":"When introducing or changing an API seam (hooks, callback payloads, lifecycle state transitions), require an explicit, end-to-end, type-safe contract that matches implementation and documentation.","repository":"QwenLM/qwen-code","domain":"ai-agents","topic":"API","language":"Markdown","updated":"2026-07-28","comments":6,"stars":26407,"raw":"https://awesomereviewers.com/raw/qwen-code-typed-api-contracts.md"}],"prompt_count":87},{"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":25,"share":41,"commands":["analyze (language: 2)","analyze (language: 1)","Tests (include: 5)"],"run":"analyze (language: 2)","via":null,"triggers":["ci"],"examples":[{"repository":"30-seconds/30-seconds-of-code","slug":"30-seconds-30-seconds-of-code"},{"repository":"nodejs/node","slug":"nodejs-node"},{"repository":"langflow-ai/langflow","slug":"langflow-ai-langflow"},{"repository":"sveltejs/svelte","slug":"sveltejs-svelte"},{"repository":"microsoft/playwright","slug":"microsoft-playwright"},{"repository":"vitejs/vite","slug":"vitejs-vite"}]},"alternatives":[],"note":null}],"prompts":[{"slug":"fastapi-consistent-code-examples","title":"Consistent code examples","description":"Maintain consistent formatting and styling in code examples throughout your NestJS application documentation. This ensures developers can quickly understand dependency injection patterns, module structures, and decorator usage.","repository":"fastapi/fastapi","domain":"app-frameworks","topic":"NestJS","language":"Markdown","updated":"2025-07-02","comments":5,"stars":86871,"raw":"https://awesomereviewers.com/raw/fastapi-consistent-code-examples.md"},{"slug":"django-transaction-aware-task-enqueuing","title":"Transaction-aware task enqueuing","description":"When working with background tasks that depend on database changes, ensure tasks are enqueued only after the related transaction has successfully committed. This prevents tasks from operating on uncommitted or rolled-back data, avoiding race conditions and inconsistent states.","repository":"django/django","domain":"app-frameworks","topic":"Celery","language":"Txt","updated":"2024-12-28","comments":3,"stars":84182,"raw":"https://awesomereviewers.com/raw/django-transaction-aware-task-enqueuing.md"}],"prompt_count":2},{"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":{"id":"coq","method":"formal","kind":"proofs","languages":["*"],"upstream":"https://github.com/rocq-prover/rocq","docs":null,"autofix":false,"exit_codes":{},"repos":2,"share":3,"commands":[],"run":null,"via":null,"triggers":[],"examples":[{"repository":"helix-editor/helix","slug":"helix-editor-helix"},{"repository":"vlang/v","slug":"vlang-v"}]},"alternatives":[],"note":null}],"prompts":[{"slug":"ruff-precise-type-narrowing","title":"Precise type narrowing","description":"Implement sound type narrowing algorithms that balance precision with correctness. When narrowing types: 1. For direct assignments, narrow the type to the assigned value''s type:","repository":"astral-sh/ruff","domain":"devtools","topic":"Algorithms","language":"Markdown","updated":"2025-06-17","comments":8,"stars":40619,"raw":"https://awesomereviewers.com/raw/ruff-precise-type-narrowing.md"},{"slug":"volcano-algorithm-explanation-clarity","title":"Algorithm explanation clarity","description":"When documenting algorithms, provide detailed explanations of the underlying logic with concrete examples and clear process flows. Abstract algorithmic descriptions should be accompanied by specific scenarios that illustrate how the algorithm behaves in practice.","repository":"volcano-sh/volcano","domain":"orchestration","topic":"Algorithms","language":"Markdown","updated":"2025-08-20","comments":6,"stars":4899,"raw":"https://awesomereviewers.com/raw/volcano-algorithm-explanation-clarity.md"},{"slug":"ty-specify-algorithmic-scope-precisely","title":"Specify algorithmic scope precisely","description":"When documenting changes to algorithms, data structures, or computational approaches, explicitly identify the specific components affected rather than using vague or generic descriptions. This includes naming exact data structure classes, clarifying the scope and limitations of algorithmic improvements, and using precise technical terminology.","repository":"astral-sh/ty","domain":"devtools","topic":"Algorithms","language":"Markdown","updated":"2025-08-14","comments":6,"stars":11919,"raw":"https://awesomereviewers.com/raw/ty-specify-algorithmic-scope-precisely.md"},{"slug":"30-seconds-of-code-correct-algorithm-contracts","title":"Correct Algorithm Contracts","description":"For algorithm/data-structure snippets, make correctness and the function contract explicit: don’t silently break edge cases, validate required input constraints, and only mutate inputs when the name/description guarantees it. Also prefer native/built-in equivalents when available.","repository":"30-seconds/30-seconds-of-code","domain":"app-frameworks","topic":"Algorithms","language":"Markdown","updated":"2020-10-22","comments":6,"stars":129334,"raw":"https://awesomereviewers.com/raw/30-seconds-of-code-correct-algorithm-contracts.md"},{"slug":"warp-deterministic-matching-invariants","title":"Deterministic Matching Invariants","description":"When implementing algorithms for pairing/alignment, matching/routing, search, or event fan-out, require a clearly stated invariant and explicit boundary/edge-case behavior, then back it with targeted tests.","repository":"warpdotdev/warp","domain":"devtools","topic":"Algorithms","language":"Markdown","updated":"2026-05-08","comments":5,"stars":56893,"raw":"https://awesomereviewers.com/raw/warp-deterministic-matching-invariants.md"},{"slug":"freecodecamp-deterministic-array-algorithm-contracts","title":"Deterministic Array Algorithm Contracts","description":"For algorithm-heavy code that transforms arrays (multi-step pipelines, scheduling, deduping, cyclic traversal), require clear, testable function contracts and deterministic behavior:","repository":"freeCodeCamp/freeCodeCamp","domain":"docs","topic":"Algorithms","language":"Markdown","updated":"2026-04-02","comments":4,"stars":444449,"raw":"https://awesomereviewers.com/raw/freecodecamp-deterministic-array-algorithm-contracts.md"},{"slug":"prometheus-special-value-handling","title":"special value handling","description":"Algorithms must explicitly define and consistently handle special values like NaN, infinity, and edge cases across all mathematical operations. Special values can significantly impact computational results and should not be treated as afterthoughts.","repository":"prometheus/prometheus","domain":"observability","topic":"Algorithms","language":"Markdown","updated":"2025-07-10","comments":4,"stars":59616,"raw":"https://awesomereviewers.com/raw/prometheus-special-value-handling.md"},{"slug":"elasticsearch-parallel-branch-traceability","title":"Parallel branch traceability","description":"When implementing algorithms with parallel processing branches, ensure proper traceability and data consistency across all branches to facilitate result analysis and debugging:","repository":"elastic/elasticsearch","domain":"data-systems","topic":"Algorithms","language":"Markdown","updated":"2025-06-30","comments":4,"stars":73104,"raw":"https://awesomereviewers.com/raw/elasticsearch-parallel-branch-traceability.md"},{"slug":"v-document-algorithm-behavior","title":"Document algorithm behavior","description":"When implementing or documenting algorithms, clearly specify their behavior, expected outputs, and usage patterns. This includes documenting mathematical operation semantics, output characteristics, and providing complete examples that demonstrate the algorithm's behavior.","repository":"vlang/v","domain":"runtimes","topic":"Algorithms","language":"Markdown","updated":"2025-06-18","comments":4,"stars":36582,"raw":"https://awesomereviewers.com/raw/v-document-algorithm-behavior.md"},{"slug":"typescript-consistent-type-algorithms","title":"Consistent type algorithms","description":"Implement consistent algorithms for type compatibility and comparison across different data structures. When developing type checking logic, ensure similar operations (like assignment compatibility, intersection, or mapping) behave predictably regardless of the underlying type structure.","repository":"microsoft/typescript","domain":"runtimes","topic":"Algorithms","language":"Txt","updated":"2024-10-13","comments":4,"stars":105378,"raw":"https://awesomereviewers.com/raw/typescript-consistent-type-algorithms.md"},{"slug":"redis-deterministic-control-plane-protocols","title":"Deterministic Control-Plane Protocols","description":"When multiple agents participate in cluster control-plane updates (e.g., TD, FC, nodes), treat the protocol as an algorithm and make its conflict-resolution and time/progression semantics explicit in the spec/code review contract.","repository":"redis/redis","domain":"data-systems","topic":"Algorithms","language":"Markdown","updated":"2023-07-06","comments":4,"stars":74261,"raw":"https://awesomereviewers.com/raw/redis-deterministic-control-plane-protocols.md"},{"slug":"swift-mathematical-precision-matters","title":"Mathematical precision matters","description":"When implementing mathematical algorithms, ensure precise terminology and correct implementation of mathematical concepts. This is especially important for complex domains like differentiation, optimization, or numerical methods.","repository":"tensorflow/swift","domain":"ml-systems","topic":"Algorithms","language":"Markdown","updated":"2019-11-26","comments":4,"stars":6136,"raw":"https://awesomereviewers.com/raw/swift-mathematical-precision-matters.md"}],"prompt_count":28},{"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":[{"slug":"qwen-code-atomic-exact-run-cancellation","title":"Atomic Exact-Run Cancellation","description":"When implementing concurrent async workflows with callbacks (Stop/Submit/Cancel, permission settlement, card actions), make the operation safe against stale/foreign/parallel events by using atomic identity validation plus a synchronous “claim” before any awaited side effects.","repository":"QwenLM/qwen-code","domain":"ai-agents","topic":"Concurrency","language":"Markdown","updated":"2026-07-28","comments":7,"stars":26407,"raw":"https://awesomereviewers.com/raw/qwen-code-atomic-exact-run-cancellation.md"},{"slug":"query-persist-only-settled-queries","title":"Persist Only Settled Queries","description":"When using async/concurrent flows (streaming, dehydration/rehydration, optimistic updates), ensure you never persist “in-flight” async state and you always return promises from async callbacks.","repository":"tanstack/query","domain":"app-frameworks","topic":"Concurrency","language":"Markdown","updated":"2025-12-26","comments":4,"stars":49380,"raw":"https://awesomereviewers.com/raw/query-persist-only-settled-queries.md"},{"slug":"appwrite-ensure-proper-async-context","title":"Ensure proper async context","description":"Always wrap asynchronous operations (await, suspend functions, try-await) in the appropriate language-specific async context. Top-level await is generally not supported and will cause runtime errors.","repository":"appwrite/appwrite","domain":"app-frameworks","topic":"Concurrency","language":"Markdown","updated":"2025-05-18","comments":4,"stars":51959,"raw":"https://awesomereviewers.com/raw/appwrite-ensure-proper-async-context.md"},{"slug":"fastapi-respect-async-execution-order","title":"Respect async execution order","description":"When working with asynchronous code, always be mindful of the execution order of operations, particularly with regards to yielded dependencies, middleware, and background tasks. This affects resource management, error handling, and overall application flow.","repository":"fastapi/fastapi","domain":"app-frameworks","topic":"Concurrency","language":"Markdown","updated":"2025-02-25","comments":4,"stars":86871,"raw":"https://awesomereviewers.com/raw/fastapi-respect-async-execution-order.md"},{"slug":"rails-wrap-threaded-code-properly","title":"Wrap threaded code properly","description":"When working with threads in Rails applications, always wrap application code with `Rails.application.executor.wrap` to ensure thread safety and proper state management. Code running outside these wrappers can cause race conditions, memory leaks, and inconsistent application state.","repository":"rails/rails","domain":"app-frameworks","topic":"Concurrency","language":"Markdown","updated":"2025-06-25","comments":3,"stars":57027,"raw":"https://awesomereviewers.com/raw/rails-wrap-threaded-code-properly.md"},{"slug":"bmad-method-single-writer-parallel-join","title":"Single-writer parallel join","description":"When using concurrency/parallel subagents, enforce synchronization and determinism: 1) Parallelize independent work - Start independent steps concurrently (e.g., multiple subagents), each operating on immutable inputs.","repository":"bmad-code-org/bmad-method","domain":"app-frameworks","topic":"Concurrency","language":"Markdown","updated":"2026-07-22","comments":2,"stars":51859,"raw":"https://awesomereviewers.com/raw/bmad-method-single-writer-parallel-join.md"},{"slug":"30-seconds-of-code-async-for-slow-work","title":"Async for slow work","description":"When code performs potentially slow CPU/crypto work, avoid blocking the event loop. Prefer a Promise/callback-based asynchronous wrapper so the runtime can continue handling other work, and keep the function’s API surface consistent so it can replace a sync version without call-site changes. Also ensure your team’s documentation defines async accurately...","repository":"30-seconds/30-seconds-of-code","domain":"app-frameworks","topic":"Concurrency","language":"Markdown","updated":"2018-09-02","comments":2,"stars":129334,"raw":"https://awesomereviewers.com/raw/30-seconds-of-code-async-for-slow-work.md"}],"prompt_count":7},{"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":"traefik-complete-network-configurations","title":"Complete network configurations","description":"Network configuration examples and documentation should include all essential networking components such as ports, protocols, timeouts, and security considerations. Incomplete configurations can lead to connection failures, security vulnerabilities, or unexpected behavior.","repository":"traefik/traefik","domain":"cloud-infra","topic":"Networking","language":"Markdown","updated":"2025-07-13","comments":17,"stars":55772,"raw":"https://awesomereviewers.com/raw/traefik-complete-network-configurations.md"},{"slug":"freecodecamp-middleware-ordering-and-chaining","title":"Middleware ordering and chaining","description":"When using Express, treat middleware registration as an HTTP request-processing pipeline: middleware executes in the order you add it, and the chain advances only if your middleware calls `next()`.","repository":"freeCodeCamp/freeCodeCamp","domain":"docs","topic":"Networking","language":"Markdown","updated":"2026-05-08","comments":5,"stars":444449,"raw":"https://awesomereviewers.com/raw/freecodecamp-middleware-ordering-and-chaining.md"},{"slug":"fastapi-protocol-specific-error-handling","title":"Protocol-specific error handling","description":"Handle errors and responses appropriately based on the network protocol being used. Different protocols have different mechanisms for error reporting and communication patterns.","repository":"fastapi/fastapi","domain":"app-frameworks","topic":"Networking","language":"Markdown","updated":"2025-02-25","comments":5,"stars":86871,"raw":"https://awesomereviewers.com/raw/fastapi-protocol-specific-error-handling.md"},{"slug":"teleport-authenticated-health-checks","title":"Authenticated health checks","description":"When implementing health checks for external services, verify the complete communication stack rather than just basic connectivity. Health checks should validate that your service can successfully authenticate and perform actual operations, not merely establish network connections.","repository":"gravitational/teleport","domain":"security","topic":"Networking","language":"Markdown","updated":"2025-09-05","comments":4,"stars":19109,"raw":"https://awesomereviewers.com/raw/teleport-authenticated-health-checks.md"},{"slug":"argo-cd-document-network-requirements","title":"document network requirements","description":"When documenting network-dependent features, explicitly specify all network configuration requirements including protocol support, certificate handling, and infrastructure setup. Users often encounter connectivity issues due to undocumented network prerequisites.","repository":"argoproj/argo-cd","domain":"orchestration","topic":"Networking","language":"Markdown","updated":"2025-01-20","comments":4,"stars":20149,"raw":"https://awesomereviewers.com/raw/argo-cd-document-network-requirements.md"},{"slug":"langflow-api-endpoint-documentation","title":"API endpoint documentation","description":"Ensure API documentation includes all required networking components and uses proper syntax for shell commands. API examples must include authentication headers, use correct variable expansion syntax, and clearly state network configuration assumptions.","repository":"langflow-ai/langflow","domain":"ai-agents","topic":"Networking","language":"Markdown","updated":"2025-07-02","comments":3,"stars":111046,"raw":"https://awesomereviewers.com/raw/langflow-api-endpoint-documentation.md"},{"slug":"fiber-clear-network-api-documentation","title":"Clear network API documentation","description":"Ensure networking-related API documentation and descriptions are specific, clear, and include concrete implementation details rather than vague or generic statements. This helps developers understand exactly what networking functionality does and how to implement it correctly.","repository":"gofiber/fiber","domain":"app-frameworks","topic":"Networking","language":"Markdown","updated":"2025-06-26","comments":3,"stars":37560,"raw":"https://awesomereviewers.com/raw/fiber-clear-network-api-documentation.md"},{"slug":"kubeflow-specific-network-access-documentation","title":"Specific network access documentation","description":"When documenting network access methods or service connections, always provide specific commands with explicit ports and namespaces rather than general approaches. Include clear examples of how to connect to each required service and explain the underlying proxying mechanisms.","repository":"kubeflow/kubeflow","domain":"ml-systems","topic":"Networking","language":"Markdown","updated":"2022-11-23","comments":3,"stars":15064,"raw":"https://awesomereviewers.com/raw/kubeflow-specific-network-access-documentation.md"},{"slug":"redis-control-plane-connectivity-rules","title":"Control-plane connectivity rules","description":"Define a single, deterministic networking contract between data-plane nodes and the control plane (TD/FC), and make it resilient to CP reachability and multi-FC state consistency.","repository":"redis/redis","domain":"data-systems","topic":"Networking","language":"Markdown","updated":"2022-08-29","comments":3,"stars":74261,"raw":"https://awesomereviewers.com/raw/redis-control-plane-connectivity-rules.md"},{"slug":"apisix-self-contained-secure-networking","title":"Self-Contained Secure Networking","description":"Ensure networking-related docs/examples and configurations are both runnable and secure: (1) every referenced endpoint/service/backend in an example manifest must be defined so the config works when copied, and (2) TLS-related defaults (e.g., certificate verification) must default to secure behavior and be treated as potentially breaking—clearly...","repository":"apache/apisix","domain":"cloud-infra","topic":"Networking","language":"Markdown","updated":"2026-04-21","comments":2,"stars":16922,"raw":"https://awesomereviewers.com/raw/apisix-self-contained-secure-networking.md"},{"slug":"jj-multiple-remote-configuration","title":"Multiple remote configuration","description":"When documenting or implementing features that involve multiple remote repositories, provide clear guidance on different remote configuration strategies and their appropriate use cases. This includes explaining the distinction between remotes you have write access to (typically `origin`) versus read-only upstream remotes, and when to track or sync different...","repository":"jj-vcs/jj","domain":"devtools","topic":"Networking","language":"Markdown","updated":"2025-09-08","comments":2,"stars":21171,"raw":"https://awesomereviewers.com/raw/jj-multiple-remote-configuration.md"},{"slug":"playwright-document-network-limitations","title":"Document network limitations","description":"When documenting network-related features, clearly specify compatibility constraints, browser limitations, and potential side effects. This is especially critical for experimental features or those with platform-specific restrictions.","repository":"microsoft/playwright","domain":"devtools","topic":"Networking","language":"Markdown","updated":"2025-08-15","comments":2,"stars":76113,"raw":"https://awesomereviewers.com/raw/playwright-document-network-limitations.md"}],"prompt_count":23},{"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":"react-router-documentation-clarity-standards","title":"documentation clarity standards","description":"Ensure all React-related documentation, comments, and descriptions maintain high standards of clarity, accuracy, and consistency. This includes using proper grammar, consistent terminology, complete descriptions, and well-structured explanations.","repository":"remix-run/react-router","domain":"app-frameworks","topic":"React","language":"Markdown","updated":"2025-07-11","comments":30,"stars":55270,"raw":"https://awesomereviewers.com/raw/react-router-documentation-clarity-standards.md"},{"slug":"nuxt-documentation-formatting-consistency","title":"documentation formatting consistency","description":"Ensure consistent formatting throughout documentation by applying these standards: wrap code terms, variable names, and boolean values in backticks (`data`, `error`, `status`, `true`, `false`), use proper markdown link syntax with leading slashes (`/docs/guide/...` instead of `docs/guide/...`), maintain consistent punctuation and spacing in code examples,...","repository":"nuxt/nuxt","domain":"app-frameworks","topic":"Next","language":"Markdown","updated":"2025-04-16","comments":16,"stars":57769,"raw":"https://awesomereviewers.com/raw/nuxt-documentation-formatting-consistency.md"},{"slug":"router-ssr-documentation-completeness","title":"SSR documentation completeness","description":"Ensure server-side rendering documentation provides complete implementation details with proper build configurations and explanatory context. SSR setup guides should include comprehensive Vite configurations that clearly separate client and server bundles, detailed explanations of script purposes, and complete file structures.","repository":"TanStack/router","domain":"app-frameworks","topic":"Next","language":"Markdown","updated":"2025-07-20","comments":7,"stars":11590,"raw":"https://awesomereviewers.com/raw/router-ssr-documentation-completeness.md"},{"slug":"angular-use-reactive-signal-patterns","title":"Use reactive signal patterns","description":"Prefer Angular's reactive signal patterns over manual subscription management and imperative approaches. Use signals directly in templates without calling getters, convert observables to signals with `toSignal()`, and maintain reactive data flow throughout your application.","repository":"angular/angular","domain":"app-frameworks","topic":"Angular","language":"Markdown","updated":"2025-09-02","comments":6,"stars":98611,"raw":"https://awesomereviewers.com/raw/angular-use-reactive-signal-patterns.md"},{"slug":"query-control-focus-and-suspense","title":"Control focus and suspense","description":"When implementing React hooks around navigation focus or React Suspense: 1) Treat focus/mount as distinct - If you use `useFocusEffect` to run data refetches, remember the callback also runs on initial mount. Skip the first run when appropriate.","repository":"tanstack/query","domain":"app-frameworks","topic":"React","language":"Markdown","updated":"2025-09-01","comments":6,"stars":49380,"raw":"https://awesomereviewers.com/raw/query-control-focus-and-suspense.md"},{"slug":"react-router-configuration-compatibility-validation","title":"configuration compatibility validation","description":"Ensure that code examples and documentation accurately reflect the constraints and requirements of different rendering modes and configurations. When documenting APIs or providing examples, verify that the suggested approach is compatible with the specific rendering context (SSR, SSG, client-side) and configuration options being used.","repository":"remix-run/react-router","domain":"app-frameworks","topic":"Next","language":"Markdown","updated":"2025-06-26","comments":6,"stars":55270,"raw":"https://awesomereviewers.com/raw/react-router-configuration-compatibility-validation.md"},{"slug":"router-enhance-code-clarity","title":"Enhance code clarity","description":"Ensure all code examples and documentation are as clear and complete as possible for developers. This includes adding clarifying inline comments to explain non-obvious behavior, including all necessary import statements, and structuring information for maximum readability.","repository":"TanStack/router","domain":"app-frameworks","topic":"React","language":"Markdown","updated":"2025-05-01","comments":6,"stars":11590,"raw":"https://awesomereviewers.com/raw/router-enhance-code-clarity.md"},{"slug":"developer-roadmap-valid-angular-examples","title":"Valid Angular Examples","description":"When adding Angular examples (docs, snippets, templates), ensure they are both *syntactically/semantically valid* and shown in the *correct template context*.","repository":"kamranahmedse/developer-roadmap","domain":"docs","topic":"Angular","language":"Markdown","updated":"2024-08-15","comments":6,"stars":354523,"raw":"https://awesomereviewers.com/raw/developer-roadmap-valid-angular-examples.md"},{"slug":"ant-design-react-component-api-clarity","title":"React component API clarity","description":"Ensure React component APIs are well-designed with accurate TypeScript interfaces, clear documentation, and intuitive developer experience. This includes: (1) Using precise type definitions that match actual functionality, avoiding misleading exposed props from internal implementations, (2) Providing accurate property descriptions in documentation that...","repository":"ant-design/ant-design","domain":"app-frameworks","topic":"React","language":"Markdown","updated":"2025-08-20","comments":5,"stars":95882,"raw":"https://awesomereviewers.com/raw/ant-design-react-component-api-clarity.md"},{"slug":"query-use-suspense-only-when-ready","title":"Use Suspense Only When Ready","description":"In Next.js SSR/app-router, do not use `useSuspenseQuery` unless your server prefetch + hydration setup guarantees the data is already in the cache such that the component will not suspend.","repository":"tanstack/query","domain":"app-frameworks","topic":"Next","language":"Markdown","updated":"2024-06-11","comments":5,"stars":49380,"raw":"https://awesomereviewers.com/raw/query-use-suspense-only-when-ready.md"},{"slug":"angular-avoid-reactive-over-engineering","title":"Avoid reactive over-engineering","description":"Choose the simplest React primitive that meets your requirements rather than reaching for complex reactive patterns. Avoid useEffect when useState, useMemo, or useCallback would suffice. If you find yourself using useEffect to copy data from one state to another state, it's a sign you should restructure your component's state management.","repository":"angular/angular","domain":"app-frameworks","topic":"React","language":"Markdown","updated":"2025-09-02","comments":4,"stars":98611,"raw":"https://awesomereviewers.com/raw/angular-avoid-reactive-over-engineering.md"},{"slug":"material-ui-use-slots-for-composition","title":"Use slots for composition","description":"When designing React component APIs, implement the slots pattern using `slots` and `slotProps` props instead of specialized prop names. This approach provides a consistent, flexible, and maintainable way to customize component parts while preserving their functionality.","repository":"mui/material-ui","domain":"app-frameworks","topic":"React","language":"Markdown","updated":"2025-07-07","comments":4,"stars":96063,"raw":"https://awesomereviewers.com/raw/material-ui-use-slots-for-composition.md"}],"prompt_count":25},{"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":25,"share":41,"commands":["analyze (language: 2)","analyze (language: 1)","Tests (include: 5)"],"run":"analyze (language: 2)","via":null,"triggers":["ci"],"examples":[{"repository":"30-seconds/30-seconds-of-code","slug":"30-seconds-30-seconds-of-code"},{"repository":"nodejs/node","slug":"nodejs-node"},{"repository":"langflow-ai/langflow","slug":"langflow-ai-langflow"},{"repository":"sveltejs/svelte","slug":"sveltejs-svelte"},{"repository":"microsoft/playwright","slug":"microsoft-playwright"},{"repository":"vitejs/vite","slug":"vitejs-vite"}]},"alternatives":[],"note":null}],"prompts":[{"slug":"query-explicit-staletime-policy","title":"Explicit StaleTime Policy","description":"For every query, define a clear staleness/refetch policy—especially for SSR/hydration—rather than relying on defaults or assumptions. **Standards** - **Always choose `staleTime` deliberately** (default is `0`, which means cached data is treated as stale).","repository":"tanstack/query","domain":"app-frameworks","topic":"Caching","language":"Markdown","updated":"2026-03-30","comments":6,"stars":49380,"raw":"https://awesomereviewers.com/raw/query-explicit-staletime-policy.md"},{"slug":"django-prevent-n1-queries","title":"Prevent N+1 queries","description":"The N+1 query problem is one of the most common performance bottlenecks in Django applications. This occurs when you retrieve a list of objects and then access related objects for each one individually, causing an additional database query for each parent object.","repository":"django/django","domain":"app-frameworks","topic":"Database","language":"Txt","updated":"2025-07-06","comments":4,"stars":84182,"raw":"https://awesomereviewers.com/raw/django-prevent-n1-queries.md"},{"slug":"elasticsearch-configure-type-serialization","title":"Configure type serialization","description":"When working with databases that exchange data with other systems, ensure proper serialization and deserialization of data types like UUIDs, dates, or complex objects. System-specific representation differences can lead to data corruption, query failures, or incorrect results.","repository":"elastic/elasticsearch","domain":"data-systems","topic":"Database","language":"Markdown","updated":"2025-07-02","comments":4,"stars":73104,"raw":"https://awesomereviewers.com/raw/elasticsearch-configure-type-serialization.md"},{"slug":"rails-understand-query-method-behavior","title":"Understand query method behavior","description":"When working with database queries in Active Record, it's essential to understand the precise behavior of query methods to avoid unexpected results and performance issues.","repository":"rails/rails","domain":"app-frameworks","topic":"Database","language":"Markdown","updated":"2025-05-20","comments":4,"stars":57027,"raw":"https://awesomereviewers.com/raw/rails-understand-query-method-behavior.md"},{"slug":"mcp-data-model-guardrails","title":"Data model guardrails","description":"Default schemas should be designed for (a) correct capacity/performance assumptions and (b) efficient, queryable storage. 1) Use correct cardinality math for sizing","repository":"awslabs/mcp","domain":"ai-agents","topic":"Database","language":"Markdown","updated":"2026-07-31","comments":3,"stars":9545,"raw":"https://awesomereviewers.com/raw/mcp-data-model-guardrails.md"},{"slug":"warp-cache-invalidation-rules","title":"Cache invalidation rules","description":"Any cached value must have an explicit, testable “when does it become stale?” policy, plus a fallback path when updates may be missed. Apply this as a checklist:","repository":"warpdotdev/warp","domain":"devtools","topic":"Caching","language":"Markdown","updated":"2026-05-08","comments":3,"stars":56893,"raw":"https://awesomereviewers.com/raw/warp-cache-invalidation-rules.md"},{"slug":"bmad-method-validate-and-scope-cache","title":"Validate and Scope Cache","description":"When using cached data/artifacts, treat the cache as ephemeral and potentially stale/corrupt. Apply three rules: 1) Make cache scope explicit (and CI-safe)","repository":"bmad-code-org/bmad-method","domain":"app-frameworks","topic":"Caching","language":"Markdown","updated":"2026-04-29","comments":3,"stars":51859,"raw":"https://awesomereviewers.com/raw/bmad-method-validate-and-scope-cache.md"},{"slug":"neon-adaptive-cache-expiration-strategy","title":"Adaptive cache expiration strategy","description":"Design cache expiration policies that align with actual workload patterns rather than arbitrary timeframes. For systems with varying access patterns (e.g., daily vs. monthly workloads), implement configurable TTL settings to prevent premature cache invalidation.","repository":"neondatabase/neon","domain":"data-systems","topic":"Caching","language":"Markdown","updated":"2025-07-01","comments":3,"stars":19015,"raw":"https://awesomereviewers.com/raw/neon-adaptive-cache-expiration-strategy.md"},{"slug":"uv-optimize-cache-sharing-strategies","title":"Optimize cache sharing strategies","description":"Select the appropriate cache sharing approach based on your execution environment to maximize performance and efficiency. When working with containerized applications:","repository":"astral-sh/uv","domain":"devtools","topic":"Caching","language":"Markdown","updated":"2025-06-22","comments":3,"stars":60322,"raw":"https://awesomereviewers.com/raw/uv-optimize-cache-sharing-strategies.md"},{"slug":"neon-cache-performance-preservation","title":"Cache performance preservation","description":"When implementing database failover or restart mechanisms, ensure performance consistency by preserving and prewarming caches. Database performance can significantly degrade after restarts due to cold caches (buffer pools, file system cache, query plan cache), especially for large workloads.","repository":"neondatabase/neon","domain":"data-systems","topic":"Database","language":"Markdown","updated":"2025-03-24","comments":3,"stars":19015,"raw":"https://awesomereviewers.com/raw/neon-cache-performance-preservation.md"},{"slug":"influxdb-document-complete-data-flows","title":"Document complete data flows","description":"When documenting database systems, ensure all documentation includes complete end-to-end data flows. Both diagrams and textual descriptions should clearly indicate:","repository":"influxdata/influxdb","domain":"data-systems","topic":"Database","language":"Markdown","updated":"2025-01-24","comments":3,"stars":30268,"raw":"https://awesomereviewers.com/raw/influxdb-document-complete-data-flows.md"},{"slug":"docs-use-correct-cache-scope","title":"Use correct cache scope","description":"When using branch-scoped caches (e.g., for dependency caching), make the cache scope key match the ref GitHub uses for that event. Don’t use `github.ref_name` blindly—its value differs by event (and can cause cache misses). Also, for repos with many PRs, mitigate cache thrashing by proactively deleting branch-scoped caches on a faster cadence.","repository":"github/docs","domain":"app-frameworks","topic":"Caching","language":"Markdown","updated":"2024-10-29","comments":3,"stars":21111,"raw":"https://awesomereviewers.com/raw/docs-use-correct-cache-scope.md"}],"prompt_count":22},{"slug":"performance","title":"Hot paths and performance","topics":["Performance Optimization"],"checks":[],"prompts":[{"slug":"mxnet-explain-optimization-mechanisms","title":"Explain optimization mechanisms","description":"When implementing or documenting performance optimizations, clearly explain the mechanism and expected performance benefit. For memory-bound optimizations, specify exactly how memory operations are reduced:","repository":"apache/mxnet","domain":"ml-systems","topic":"Performance Optimization","language":"Markdown","updated":"2022-08-25","comments":5,"stars":20801,"raw":"https://awesomereviewers.com/raw/mxnet-explain-optimization-mechanisms.md"},{"slug":"neon-proactive-cache-warming","title":"Proactive cache warming","description":"Implement proactive cache warming strategies to minimize performance degradation after system restarts or during cold starts. Rather than waiting for normal workload patterns to gradually populate caches, actively prefetch and load likely-needed data into memory ahead of time.","repository":"neondatabase/neon","domain":"data-systems","topic":"Performance Optimization","language":"Markdown","updated":"2025-07-01","comments":4,"stars":19015,"raw":"https://awesomereviewers.com/raw/neon-proactive-cache-warming.md"},{"slug":"vite-leverage-native-tooling","title":"Leverage native tooling","description":"Prioritize native or Rust-based implementations of build tools over their JavaScript counterparts to significantly improve performance in both development and build phases. Tools like Rolldown (replacing Rollup and esbuild) can reduce build times and provide a more consistent experience between development and production environments.","repository":"vitejs/vite","domain":"devtools","topic":"Performance Optimization","language":"Markdown","updated":"2025-04-18","comments":4,"stars":74031,"raw":"https://awesomereviewers.com/raw/vite-leverage-native-tooling.md"},{"slug":"nuxt-strategic-component-loading","title":"Strategic component loading","description":"Choose component loading strategies based on when interactivity is actually needed, not just code splitting. Lazy prefixed components only control chunk size but still load eagerly with the page's scripts. Use delayed hydration for components that don't need immediate interactivity, avoiding unnecessary JavaScript execution during initial page load. Be...","repository":"nuxt/nuxt","domain":"app-frameworks","topic":"Performance Optimization","language":"Markdown","updated":"2025-04-03","comments":4,"stars":57769,"raw":"https://awesomereviewers.com/raw/nuxt-strategic-component-loading.md"},{"slug":"30-seconds-of-code-reduce-runtime-overhead","title":"Reduce runtime overhead","description":"When optimizing performance, remove repeated work in hot paths: avoid per-call overhead, extra passes over the same data, and unnecessary allocations; validate choices with benchmarks.","repository":"30-seconds/30-seconds-of-code","domain":"app-frameworks","topic":"Performance Optimization","language":"Markdown","updated":"2018-07-10","comments":4,"stars":129334,"raw":"https://awesomereviewers.com/raw/30-seconds-of-code-reduce-runtime-overhead.md"},{"slug":"node-resource-aware-programming-patterns","title":"Resource-aware programming patterns","description":"When optimizing application performance, be mindful of system resource constraints and use appropriate patterns to handle different scenarios efficiently:","repository":"nodejs/node","domain":"runtimes","topic":"Performance Optimization","language":"Markdown","updated":"2025-07-13","comments":3,"stars":112178,"raw":"https://awesomereviewers.com/raw/node-resource-aware-programming-patterns.md"},{"slug":"elasticsearch-stage-intensive-operations-carefully","title":"Stage intensive operations carefully","description":"When implementing operations that consume significant system resources (CPU, memory, I/O), introduce changes gradually while monitoring performance. This prevents cascading performance issues that can degrade the entire system.","repository":"elastic/elasticsearch","domain":"data-systems","topic":"Performance Optimization","language":"Markdown","updated":"2025-06-30","comments":3,"stars":73104,"raw":"https://awesomereviewers.com/raw/elasticsearch-stage-intensive-operations-carefully.md"},{"slug":"rails-document-performance-implications","title":"Document performance implications","description":"Clearly document the performance implications of features and configurations to help users make informed decisions. Avoid overstating or understating performance impacts. Instead, provide specific context about when certain features might impact performance and in what environments they are appropriate.","repository":"rails/rails","domain":"app-frameworks","topic":"Performance Optimization","language":"Markdown","updated":"2025-06-06","comments":3,"stars":57027,"raw":"https://awesomereviewers.com/raw/rails-document-performance-implications.md"},{"slug":"yoga-optimize-build-configurations","title":"Optimize build configurations","description":"When configuring CMake builds, carefully select compiler and linker flags that optimize for performance while maintaining cross-platform compatibility. Performance-oriented flags can significantly impact runtime speed, binary size, and resource utilization, but must be applied conditionally based on the target platform and compiler.","repository":"facebook/yoga","domain":"runtimes","topic":"Performance Optimization","language":"Txt","updated":"2025-03-05","comments":3,"stars":18255,"raw":"https://awesomereviewers.com/raw/yoga-optimize-build-configurations.md"},{"slug":"neovim-defer-expensive-operations","title":"defer expensive operations","description":"Avoid performing expensive operations (like module loading, event emissions, or resource allocation) until they are actually needed. This pattern significantly improves startup time and runtime performance by reducing unnecessary work.","repository":"neovim/neovim","domain":"devtools","topic":"Performance Optimization","language":"Txt","updated":"2025-06-23","comments":2,"stars":91433,"raw":"https://awesomereviewers.com/raw/neovim-defer-expensive-operations.md"},{"slug":"kilocode-document-performance-tool-lifecycle","title":"Document performance tool lifecycle","description":"When creating performance optimization tools, especially temporary dev-only utilities, clearly document their purpose, scope, and removal criteria in the README or documentation. This helps teams make informed decisions about maintenance vs. performance benefits over time.","repository":"kilo-org/kilocode","domain":"ai-agents","topic":"Performance Optimization","language":"Markdown","updated":"2025-05-28","comments":2,"stars":7302,"raw":"https://awesomereviewers.com/raw/kilocode-document-performance-tool-lifecycle.md"},{"slug":"material-ui-use-direct-path-imports","title":"Use direct path imports","description":"For optimal performance, use direct path imports instead of barrel imports when working with UI component libraries like Material UI. This practice improves both production bundle size through better tree-shaking and significantly enhances development server performance.","repository":"mui/material-ui","domain":"app-frameworks","topic":"Performance Optimization","language":"Markdown","updated":"2025-04-29","comments":2,"stars":96063,"raw":"https://awesomereviewers.com/raw/material-ui-use-direct-path-imports.md"}],"prompt_count":22},{"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-provider-documentation-completeness","title":"AI provider documentation completeness","description":"Ensure comprehensive documentation for AI/ML provider integrations that covers all usage patterns, uses precise terminology, and provides helpful context for developers.","repository":"BerriAI/litellm","domain":"llm-infra","topic":"AI","language":"Markdown","updated":"2025-08-12","comments":9,"stars":28310,"raw":"https://awesomereviewers.com/raw/litellm-ai-provider-documentation-completeness.md"},{"slug":"bmad-method-deterministic-prompt-contracts","title":"Deterministic Prompt Contracts","description":"Write AI prompt/workflow steps as deterministic contracts: remove ambiguity, force required lookups, gate behavior by mode, and make unattended/automation outputs schema-correct.","repository":"bmad-code-org/bmad-method","domain":"ai-agents","topic":"AI","language":"Markdown","updated":"2026-08-07","comments":8,"stars":51859,"raw":"https://awesomereviewers.com/raw/bmad-method-deterministic-prompt-contracts.md"},{"slug":"mxnet-technical-precision-matters","title":"Technical precision matters","description":"When documenting AI models, frameworks, and optimization techniques, precision in language is as important as precision in your algorithms. Technical inaccuracies or unclear explanations can lead to implementation errors and confusion.","repository":"apache/mxnet","domain":"ml-systems","topic":"AI","language":"Markdown","updated":"2022-08-25","comments":8,"stars":20801,"raw":"https://awesomereviewers.com/raw/mxnet-technical-precision-matters.md"},{"slug":"dspy-ai-configuration-documentation","title":"AI configuration documentation","description":"Ensure AI model configurations and related documentation use precise terminology and provide clear, complete setup instructions without overwhelming users.","repository":"stanfordnlp/dspy","domain":"ai-agents","topic":"AI","language":"Markdown","updated":"2025-08-12","comments":6,"stars":27813,"raw":"https://awesomereviewers.com/raw/dspy-ai-configuration-documentation.md"},{"slug":"developer-roadmap-accurate-ai-content","title":"Accurate AI Content","description":"When writing AI/LLM-related documentation or roadmap material, ensure it (a) states model limitations precisely, (b) stays in the correct scope for the node/context, and (c) explains implementations in terms of the underlying pipeline (prefer pre-trained tools) rather than framework specifics.","repository":"kamranahmedse/developer-roadmap","domain":"docs","topic":"AI","language":"Markdown","updated":"2024-11-04","comments":6,"stars":354523,"raw":"https://awesomereviewers.com/raw/developer-roadmap-accurate-ai-content.md"},{"slug":"angular-ai-documentation-clarity","title":"AI documentation clarity","description":"Ensure AI-related documentation, comments, and explanations are clear, accurate, and well-structured. This includes fixing spelling errors, using precise terminology, adding necessary context about experimental features, and employing active voice for better readability.","repository":"angular/angular","domain":"app-frameworks","topic":"AI","language":"Markdown","updated":"2025-08-19","comments":5,"stars":98611,"raw":"https://awesomereviewers.com/raw/angular-ai-documentation-clarity.md"},{"slug":"goose-ai-terminology-consistency","title":"AI terminology consistency","description":"Maintain consistent terminology when describing AI systems, capabilities, and workflows throughout documentation and content. This includes using standardized terms for AI entities (consistently choosing between \"AI\", \"assistant\", \"model\", or \"agent\"), technical processes, and capability descriptions.","repository":"block/goose","domain":"ai-agents","topic":"AI","language":"Markdown","updated":"2025-07-19","comments":4,"stars":19037,"raw":"https://awesomereviewers.com/raw/goose-ai-terminology-consistency.md"},{"slug":"langflow-ai-response-variability","title":"AI response variability","description":"When documenting AI model interactions, account for the non-deterministic nature of AI responses and avoid assumptions about specific outputs. AI models can produce different responses to identical inputs, and model behavior changes over time through updates and improvements.","repository":"langflow-ai/langflow","domain":"ai-agents","topic":"AI","language":"Markdown","updated":"2025-07-14","comments":4,"stars":111046,"raw":"https://awesomereviewers.com/raw/langflow-ai-response-variability.md"},{"slug":"vllm-document-ai-model-capabilities","title":"Document AI model capabilities","description":"Provide clear, comprehensive documentation for AI model capabilities, especially for multimodal features and deployment scenarios. Include: 1. Explicit documentation of supported input types and formats","repository":"vllm-project/vllm","domain":"llm-infra","topic":"AI","language":"Markdown","updated":"2025-07-08","comments":4,"stars":51730,"raw":"https://awesomereviewers.com/raw/vllm-document-ai-model-capabilities.md"},{"slug":"jan-document-ai-infrastructure-requirements","title":"Document AI infrastructure requirements","description":"When documenting AI applications that run local models or perform inference, always provide comprehensive infrastructure requirements including hardware specifications, platform-specific drivers, and setup instructions. This ensures users can successfully run AI models without encountering compatibility issues.","repository":"menloresearch/jan","domain":"llm-infra","topic":"AI","language":"Markdown","updated":"2023-11-16","comments":4,"stars":37620,"raw":"https://awesomereviewers.com/raw/jan-document-ai-infrastructure-requirements.md"},{"slug":"deeplearning4j-document-ai-apis-completely","title":"Document AI APIs completely","description":"When developing AI libraries and tools, provide comprehensive and accurate API documentation that helps users navigate complex functionality. Documentation should:","repository":"deeplearning4j/deeplearning4j","domain":"ml-systems","topic":"AI","language":"Markdown","updated":"2019-10-24","comments":4,"stars":14036,"raw":"https://awesomereviewers.com/raw/deeplearning4j-document-ai-apis-completely.md"},{"slug":"sglang-document-ai-limitations","title":"Document AI limitations","description":"When implementing AI model support or hardware backends, clearly document known limitations, compatibility constraints, and version requirements to prevent integration issues and set proper expectations.","repository":"sgl-project/sglang","domain":"llm-infra","topic":"AI","language":"Markdown","updated":"2025-08-10","comments":3,"stars":17245,"raw":"https://awesomereviewers.com/raw/sglang-document-ai-limitations.md"}],"prompt_count":29},{"slug":"observability","title":"Logging, metrics, tracing","topics":["Logging","Observability"],"checks":[],"prompts":[{"slug":"traefik-complete-observability-router-options","title":"complete observability router options","description":"When documenting router configuration options for any provider (Docker, Consul Catalog, ECS, KV stores, Nomad, etc.), ensure that all observability-related router options are included and properly documented. This is critical for enabling comprehensive monitoring, tracing, and logging capabilities.","repository":"traefik/traefik","domain":"cloud-infra","topic":"Observability","language":"Markdown","updated":"2025-02-13","comments":6,"stars":55772,"raw":"https://awesomereviewers.com/raw/traefik-complete-observability-router-options.md"},{"slug":"prometheus-complete-observability-documentation","title":"Complete observability documentation","description":"Ensure documentation for observability systems provides comprehensive information including all required permissions, complete configuration options, and clear warnings about operational impacts. Monitoring and metrics systems often have significant performance and security implications that users must understand to operate them safely.","repository":"prometheus/prometheus","domain":"observability","topic":"Observability","language":"Markdown","updated":"2025-07-17","comments":4,"stars":59616,"raw":"https://awesomereviewers.com/raw/prometheus-complete-observability-documentation.md"},{"slug":"opentelemetry-python-place-attributes-correctly","title":"Place attributes correctly","description":"When implementing observability with OpenTelemetry, place attributes at the appropriate level in the telemetry hierarchy to ensure effective data collection and analysis:","repository":"open-telemetry/opentelemetry-python","domain":"observability","topic":"Observability","language":"Markdown","updated":"2025-06-24","comments":4,"stars":2061,"raw":"https://awesomereviewers.com/raw/opentelemetry-python-place-attributes-correctly.md"},{"slug":"agentcore-samples-tracing-schema-and-continuity","title":"Tracing schema and continuity","description":"When adding or integrating agent frameworks/invocation paths, ensure observability works end-to-end by meeting BOTH requirements: (1) the emitted telemetry conforms to the documented OpenTelemetry/OpenInference schema (not merely “OTLP transport”), and (2) trace context is propagated across boundaries (e.g., Lambda → AgentCore) so traces are continuous and...","repository":"awslabs/agentcore-samples","domain":"ai-agents","topic":"Observability","language":"Markdown","updated":"2026-07-15","comments":3,"stars":3244,"raw":"https://awesomereviewers.com/raw/agentcore-samples-tracing-schema-and-continuity.md"},{"slug":"litellm-prefer-lightweight-observability-integrations","title":"Prefer lightweight observability integrations","description":"Observability integrations should minimize external dependencies and avoid patching LiteLLM's core functions. Instead of requiring users to install additional SDKs, prefer lightweight approaches using custom loggers with direct HTTP calls (like httpx) or implement CustomBatchLogger interfaces. Avoid monkey-patching completion functions as this can cause...","repository":"BerriAI/litellm","domain":"llm-infra","topic":"Observability","language":"Markdown","updated":"2025-07-10","comments":3,"stars":28310,"raw":"https://awesomereviewers.com/raw/litellm-prefer-lightweight-observability-integrations.md"},{"slug":"node-use-appropriate-metric-types","title":"Use appropriate metric types","description":"When instrumenting applications with metrics, choose the correct metric type based on what you''re measuring to ensure accurate and useful observability data:","repository":"nodejs/node","domain":"runtimes","topic":"Observability","language":"Markdown","updated":"2025-07-06","comments":3,"stars":112178,"raw":"https://awesomereviewers.com/raw/node-use-appropriate-metric-types.md"},{"slug":"rails-environment-specific-logger-configuration","title":"Environment-specific logger configuration","description":"Configure loggers in environment-specific files rather than in application.rb or initializers. Different environments (development, test, production) typically require different logging levels and configurations, and Rails is designed to support this pattern.","repository":"rails/rails","domain":"app-frameworks","topic":"Logging","language":"Markdown","updated":"2025-01-18","comments":3,"stars":57027,"raw":"https://awesomereviewers.com/raw/rails-environment-specific-logger-configuration.md"},{"slug":"mcp-validated-observability-guidance","title":"Validated Observability Guidance","description":"When updating observability docs, dashboards, or diagnostic query packs, ensure the guidance is both actionable and correct: 1) Add critical alerting/scale guidance","repository":"awslabs/mcp","domain":"ai-agents","topic":"Observability","language":"Markdown","updated":"2026-07-14","comments":2,"stars":9545,"raw":"https://awesomereviewers.com/raw/mcp-validated-observability-guidance.md"},{"slug":"apisix-trace-semconv-and-completeness","title":"Trace semconv and completeness","description":"Make observability outputs standards-compliant and fully observable. Apply this when writing instrumentation and when publishing tracing/telemetry examples:","repository":"apache/apisix","domain":"cloud-infra","topic":"Observability","language":"Markdown","updated":"2026-04-26","comments":2,"stars":16922,"raw":"https://awesomereviewers.com/raw/apisix-trace-semconv-and-completeness.md"},{"slug":"teleport-design-comprehensive-metrics","title":"Design comprehensive metrics","description":"When designing observability metrics, ensure they are explicit about all possible states, comprehensive in scope, and clearly documented to avoid ambiguity. Metrics should accurately represent what is being monitored and make their limitations transparent.","repository":"gravitational/teleport","domain":"security","topic":"Observability","language":"Markdown","updated":"2025-08-26","comments":2,"stars":19109,"raw":"https://awesomereviewers.com/raw/teleport-design-comprehensive-metrics.md"},{"slug":"argo-cd-document-observability-prerequisites","title":"Document observability prerequisites","description":"When documenting observability features such as metrics, debugging capabilities, or monitoring tools, always include clear information about their prerequisites, enabling conditions, and limitations. This ensures developers understand when these features are available and how to access them.","repository":"argoproj/argo-cd","domain":"orchestration","topic":"Observability","language":"Markdown","updated":"2025-07-08","comments":2,"stars":20149,"raw":"https://awesomereviewers.com/raw/argo-cd-document-observability-prerequisites.md"},{"slug":"azure-sdk-for-net-use-higher-level-telemetry","title":"Use higher-level telemetry","description":"When implementing observability for Azure services, prefer higher-level telemetry packages and configuration methods over low-level implementations. For Azure Monitor integration, use the Azure.Monitor.OpenTelemetry.AspNetCore package instead of the lower-level Azure.Monitor.OpenTelemetry.Exporter, as it provides simpler integration and is the recommended...","repository":"Azure/azure-sdk-for-net","domain":"cloud-infra","topic":"Observability","language":"Markdown","updated":"2025-06-23","comments":2,"stars":5809,"raw":"https://awesomereviewers.com/raw/azure-sdk-for-net-use-higher-level-telemetry.md"}],"prompt_count":19},{"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":8,"share":13,"commands":["pre-commit hook end-of-file-fixer","pre-commit hook trailing-whitespace","pre-commit hook check-added-large-files"],"run":null,"via":"pre-commit hook end-of-file-fixer","triggers":["pre_commit","ci"],"examples":[{"repository":"langflow-ai/langflow","slug":"langflow-ai-langflow"},{"repository":"fastapi/fastapi","slug":"fastapi-fastapi"},{"repository":"bmad-code-org/bmad-method","slug":"bmad-code-org-bmad-method"},{"repository":"astral-sh/ruff","slug":"astral-sh-ruff"},{"repository":"pydantic/pydantic","slug":"pydantic-pydantic"},{"repository":"SWE-agent/SWE-agent","slug":"swe-agent-swe-agent"}]},"alternatives":[],"note":null}],"prompts":[{"slug":"traefik-configuration-value-consistency","title":"configuration value consistency","description":"Ensure configuration values follow consistent formats, use meaningful defaults, and accurately distinguish between required and optional fields across all documentation.","repository":"traefik/traefik","domain":"cloud-infra","topic":"Configurations","language":"Markdown","updated":"2025-06-25","comments":18,"stars":55772,"raw":"https://awesomereviewers.com/raw/traefik-configuration-value-consistency.md"},{"slug":"langflow-configuration-documentation-clarity","title":"Configuration documentation clarity","description":"Ensure configuration documentation clearly distinguishes between deployment contexts and uses consistent terminology throughout. When documenting configuration procedures, explicitly specify the target deployment type (Langflow Desktop vs OSS) and platform (macOS vs Windows) to avoid user confusion.","repository":"langflow-ai/langflow","domain":"ai-agents","topic":"Configurations","language":"Markdown","updated":"2025-07-09","comments":17,"stars":111046,"raw":"https://awesomereviewers.com/raw/langflow-configuration-documentation-clarity.md"},{"slug":"brew-follow-support-tiers","title":"Follow support tiers","description":"Configure your Homebrew installation according to the defined support tiers to ensure optimal functionality and support. For Tier 1 support (fully supported):","repository":"Homebrew/brew","domain":"devtools","topic":"Configurations","language":"Markdown","updated":"2025-04-12","comments":12,"stars":44168,"raw":"https://awesomereviewers.com/raw/brew-follow-support-tiers.md"},{"slug":"hermes-agent-config-source-alignment","title":"Config source alignment","description":"Behavioral configuration must be documented and wired through the supported config system, with examples matching the actual runtime resolution. Apply these rules:","repository":"nousresearch/hermes-agent","domain":"ai-agents","topic":"Configurations","language":"Markdown","updated":"2026-07-28","comments":10,"stars":221948,"raw":"https://awesomereviewers.com/raw/hermes-agent-config-source-alignment.md"},{"slug":"ragflow-config-documentation-constraints","title":"Config Documentation Constraints","description":"When adding or updating configuration-related docs (env vars, config files, feature/transport flags, and deployment commands), ensure the guidance is (1) context-correct, (2) compatibility-checked, and (3) explicit about defaults/overrides.","repository":"infiniflow/ragflow","domain":"llm-infra","topic":"Configurations","language":"Markdown","updated":"2025-11-11","comments":10,"stars":80174,"raw":"https://awesomereviewers.com/raw/ragflow-config-documentation-constraints.md"},{"slug":"ty-configuration-documentation-clarity","title":"Configuration documentation clarity","description":"Configuration documentation should be precise, specific, and include helpful context for users. Avoid vague or ambiguous language that could lead to misunderstanding of how settings behave.","repository":"astral-sh/ty","domain":"devtools","topic":"Configurations","language":"Markdown","updated":"2025-08-06","comments":10,"stars":11919,"raw":"https://awesomereviewers.com/raw/ty-configuration-documentation-clarity.md"},{"slug":"teleport-thoughtful-configuration-design","title":"thoughtful configuration design","description":"When designing configuration schemas and fields, carefully consider their placement, validation, and long-term implications to prevent conflicts, maintain compatibility, and ensure good user experience.","repository":"gravitational/teleport","domain":"security","topic":"Configurations","language":"Markdown","updated":"2025-09-05","comments":9,"stars":19109,"raw":"https://awesomereviewers.com/raw/teleport-thoughtful-configuration-design.md"},{"slug":"poetry-explicit-configuration-specification","title":"explicit configuration specification","description":"Always explicitly specify configuration values rather than relying on defaults or implicit behavior. Poetry requires unambiguous configuration to function correctly, and many issues arise from incomplete or assumed specifications.","repository":"python-poetry/poetry","domain":"devtools","topic":"Configurations","language":"Markdown","updated":"2025-01-29","comments":9,"stars":33496,"raw":"https://awesomereviewers.com/raw/poetry-explicit-configuration-specification.md"},{"slug":"docs-pin-ci-actions-by-sha","title":"Pin CI Actions By SHA","description":"When writing CI/CD workflows (and the documentation snippets that users copy/paste), always: - **Pin every third-party GitHub Action to an immutable commit SHA** (optionally with a comment showing the intended version), instead of using only tags like `@v4`.","repository":"github/docs","domain":"orchestration","topic":"CI/CD","language":"Markdown","updated":"2026-10-01","comments":8,"stars":21111,"raw":"https://awesomereviewers.com/raw/docs-pin-ci-actions-by-sha.md"},{"slug":"celery-explicit-dependency-constraints","title":"Explicit dependency constraints","description":"In configuration/requirements files, make compatibility explicit: bound versions to prevent silent breakage across Python/platform build environments, and use environment markers for dependencies that differ by Python version, OS, implementation, or wheel availability.","repository":"celery/celery","domain":"orchestration","topic":"Configurations","language":"Txt","updated":"2026-02-10","comments":8,"stars":28464,"raw":"https://awesomereviewers.com/raw/celery-explicit-dependency-constraints.md"},{"slug":"mermaid-changeset-release-hygiene","title":"Changeset release hygiene","description":"Ensure changeset PRs produce correct and minimal release automation output. Apply these rules before submitting: - **Create changesets only for user/release-relevant changes.** If it’s documentation-only, **do not** add a changeset.","repository":"mermaid-js/mermaid","domain":"devtools","topic":"CI/CD","language":"Markdown","updated":"2026-01-29","comments":8,"stars":87952,"raw":"https://awesomereviewers.com/raw/mermaid-changeset-release-hygiene.md"},{"slug":"fastapi-isolate-configuration-concerns","title":"Isolate configuration concerns","description":"Keep configuration settings separate from application code by using environment variables or dedicated configuration files. This promotes better maintainability, security, and flexibility across different deployment environments.","repository":"fastapi/fastapi","domain":"app-frameworks","topic":"Configurations","language":"Markdown","updated":"2025-06-21","comments":8,"stars":86871,"raw":"https://awesomereviewers.com/raw/fastapi-isolate-configuration-concerns.md"}],"prompt_count":147},{"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":3,"commands":["uses actions/dependency-review-action"],"run":null,"via":"GitHub Action actions/dependency-review-action","triggers":["ci"],"examples":[{"repository":"prettier/prettier","slug":"prettier-prettier"},{"repository":"awslabs/mcp","slug":"awslabs-mcp"}]},"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":25,"share":41,"commands":["analyze (language: 2)","analyze (language: 1)","Tests (include: 5)"],"run":"analyze (language: 2)","via":null,"triggers":["ci"],"examples":[{"repository":"30-seconds/30-seconds-of-code","slug":"30-seconds-30-seconds-of-code"},{"repository":"nodejs/node","slug":"nodejs-node"},{"repository":"langflow-ai/langflow","slug":"langflow-ai-langflow"},{"repository":"sveltejs/svelte","slug":"sveltejs-svelte"},{"repository":"microsoft/playwright","slug":"microsoft-playwright"},{"repository":"vitejs/vite","slug":"vitejs-vite"}]},"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":25,"share":41,"commands":["analyze (language: 2)","analyze (language: 1)","Tests (include: 5)"],"run":"analyze (language: 2)","via":null,"triggers":["ci"],"examples":[{"repository":"30-seconds/30-seconds-of-code","slug":"30-seconds-30-seconds-of-code"},{"repository":"nodejs/node","slug":"nodejs-node"},{"repository":"langflow-ai/langflow","slug":"langflow-ai-langflow"},{"repository":"sveltejs/svelte","slug":"sveltejs-svelte"},{"repository":"microsoft/playwright","slug":"microsoft-playwright"},{"repository":"vitejs/vite","slug":"vitejs-vite"}]},"alternatives":[],"note":null}],"prompts":[{"slug":"fastapi-sync-versus-async-tests","title":"Sync versus async tests","description":"Choose the appropriate testing approach based on your test requirements. For standard API endpoint testing, use `TestClient` with regular functions. For tests requiring async operations (like database queries), use `AsyncClient` with proper async test configuration.","repository":"fastapi/fastapi","domain":"app-frameworks","topic":"Testing","language":"Markdown","updated":"2025-06-16","comments":7,"stars":86871,"raw":"https://awesomereviewers.com/raw/fastapi-sync-versus-async-tests.md"},{"slug":"qwen-code-evidence-grade-testing","title":"Evidence-grade Testing","description":"When adding or updating test/verification logic, treat the harness setup as part of the test and ensure the evidence is causally attributable and non-vacuous.","repository":"QwenLM/qwen-code","domain":"ai-agents","topic":"Testing","language":"Markdown","updated":"2026-07-26","comments":5,"stars":26407,"raw":"https://awesomereviewers.com/raw/qwen-code-evidence-grade-testing.md"},{"slug":"svelte-prefer-testing-libraries","title":"prefer testing libraries","description":"When testing components, use established testing libraries like @testing-library/svelte instead of low-level DOM manipulation approaches. Low-level testing with direct mount/unmount and querySelector calls is brittle and requires frequent updates when component structure changes. Testing libraries provide user-focused APIs that are more robust to...","repository":"sveltejs/svelte","domain":"app-frameworks","topic":"Testing","language":"Markdown","updated":"2024-07-26","comments":5,"stars":83580,"raw":"https://awesomereviewers.com/raw/svelte-prefer-testing-libraries.md"},{"slug":"playwright-testing-best-practices","title":"testing best practices","description":"Choose testing methods, configurations, and approaches that prioritize user experience and reliability over theoretical completeness. Consider the practical needs of your development team and testing environment when making decisions.","repository":"microsoft/playwright","domain":"devtools","topic":"Testing","language":"Markdown","updated":"2025-08-12","comments":4,"stars":76113,"raw":"https://awesomereviewers.com/raw/playwright-testing-best-practices.md"},{"slug":"cypress-clarify-testing-documentation","title":"Clarify testing documentation","description":"Ensure that testing documentation, including changelogs, API docs, and guides, uses clear and precise language that doesn't confuse developers. Avoid ambiguous statements that might mislead users who already understand the concepts, use proper technical terminology, and provide concrete examples that reflect real-world usage patterns.","repository":"cypress-io/cypress","domain":"devtools","topic":"Testing","language":"Markdown","updated":"2025-07-02","comments":3,"stars":48850,"raw":"https://awesomereviewers.com/raw/cypress-clarify-testing-documentation.md"},{"slug":"prometheus-document-test-tool-options","title":"document test tool options","description":"When documenting test tools, migration utilities, or testing frameworks, provide comprehensive explanations of different modes or options available, including their trade-offs and appropriate use cases. This helps developers make informed decisions about which approach best fits their testing needs.","repository":"prometheus/prometheus","domain":"observability","topic":"Testing","language":"Markdown","updated":"2025-06-14","comments":3,"stars":59616,"raw":"https://awesomereviewers.com/raw/prometheus-document-test-tool-options.md"},{"slug":"awesome-go-enforce-coverage-thresholds","title":"Enforce coverage thresholds","description":"All code contributions must meet a minimum test coverage threshold of 80% before being accepted. This ensures adequate testing and helps maintain code quality standards across the project.","repository":"avelino/awesome-go","domain":"docs","topic":"Testing","language":"Markdown","updated":"2024-08-13","comments":3,"stars":151435,"raw":"https://awesomereviewers.com/raw/awesome-go-enforce-coverage-thresholds.md"},{"slug":"mermaid-comprehensive-test-coverage","title":"Comprehensive Test Coverage","description":"When implementing or extending functionality, ensure tests (primarily unit tests for non-renderer code) cover the full supported behavior surface—not just a subset.","repository":"mermaid-js/mermaid","domain":"devtools","topic":"Testing","language":"Markdown","updated":"2026-01-29","comments":2,"stars":87952,"raw":"https://awesomereviewers.com/raw/mermaid-comprehensive-test-coverage.md"},{"slug":"volcano-implement-simulation-testing","title":"Implement simulation testing","description":"When developing complex systems like schedulers or resource managers, create simulation-based testing frameworks to validate functionality in scenarios that cannot be easily reproduced in development environments. This approach enables testing of hardware configurations you don't have access to (GPU/NPU nodes), large-scale cluster behaviors, and parameter...","repository":"volcano-sh/volcano","domain":"orchestration","topic":"Testing","language":"Markdown","updated":"2025-07-17","comments":2,"stars":4899,"raw":"https://awesomereviewers.com/raw/volcano-implement-simulation-testing.md"},{"slug":"turborepo-verify-test-commands","title":"Verify test commands","description":"Always verify that test commands documented in project guides work exactly as written. Test commands should be copy-paste executable without modification. When adding or updating test command examples in documentation:","repository":"vercel/turborepo","domain":"devtools","topic":"Testing","language":"Markdown","updated":"2025-07-08","comments":2,"stars":28115,"raw":"https://awesomereviewers.com/raw/turborepo-verify-test-commands.md"},{"slug":"typescript-use-typescript-specific-tests","title":"Use TypeScript-specific tests","description":"Always use fourslash tests (for IDE/language service features) or compiler tests (for TypeScript compilation behavior) instead of direct unit tests. Place tests in the correct directories: `tests/cases/compiler` or `tests/cases/fourslash`.","repository":"microsoft/typescript","domain":"runtimes","topic":"Testing","language":"Markdown","updated":"2025-06-18","comments":2,"stars":105378,"raw":"https://awesomereviewers.com/raw/typescript-use-typescript-specific-tests.md"},{"slug":"dspy-add-comprehensive-test-coverage","title":"Add comprehensive test coverage","description":"When introducing new functionality, always include corresponding test coverage that extends existing test infrastructure and validates the feature across multiple scenarios. This ensures robustness and maintains code quality standards.","repository":"stanfordnlp/dspy","domain":"ai-agents","topic":"Testing","language":"Markdown","updated":"2024-12-05","comments":2,"stars":27813,"raw":"https://awesomereviewers.com/raw/dspy-add-comprehensive-test-coverage.md"}],"prompt_count":12},{"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":{"id":"mkdocs","method":"static_analysis","kind":"docs-build","languages":["python","docs"],"upstream":"https://github.com/mkdocs/mkdocs","docs":null,"autofix":false,"exit_codes":{},"repos":8,"share":13,"commands":["mkdocs build","mkdocs build --strict","mkdocs build --strict -f mkdocs.yml"],"run":"mkdocs build","via":null,"triggers":["ci","local"],"examples":[{"repository":"astral-sh/uv","slug":"astral-sh-uv"},{"repository":"traefik/traefik","slug":"traefik-traefik"},{"repository":"astral-sh/ruff","slug":"astral-sh-ruff"},{"repository":"pydantic/pydantic","slug":"pydantic-pydantic"},{"repository":"jj-vcs/jj","slug":"jj-vcs-jj"},{"repository":"argoproj/argo-cd","slug":"argoproj-argo-cd"}]},"alternatives":[{"id":"sphinx","repos":1,"share":2}],"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":5,"share":8,"commands":["codespell","codespell --toml pyproject.toml","codespell --toml pyproject.toml --write"],"run":"codespell","via":"GitHub Action codespell-project/actions-codespell","triggers":["pre_commit","ci","local"],"examples":[{"repository":"langflow-ai/langflow","slug":"langflow-ai-langflow"},{"repository":"gofiber/fiber","slug":"gofiber-fiber"},{"repository":"pydantic/pydantic","slug":"pydantic-pydantic"},{"repository":"jj-vcs/jj","slug":"jj-vcs-jj"},{"repository":"open-telemetry/opentelemetry-python","slug":"open-telemetry-opentelemetry-python"}]},"alternatives":[],"note":null}],"prompts":[{"slug":"free-programming-books-canonical-documentation-entries","title":"Canonical Documentation Entries","description":"When adding or updating documentation entries (e.g., course/resource lists), use canonical metadata and URLs so links don’t break, don’t leak tracking, and render correctly.","repository":"EbookFoundation/free-programming-books","domain":"docs","topic":"Documentation","language":"Markdown","updated":"2026-02-03","comments":47,"stars":388003,"raw":"https://awesomereviewers.com/raw/free-programming-books-canonical-documentation-entries.md"},{"slug":"oh-my-pi-changelog-entry-conventions","title":"Changelog entry conventions","description":"Changelog entries follow a consistent, repo-wide convention, since many PRs were flagged for violating it: 1. **Placement**: New entries always go under `## [Unreleased]`, under the correct `### Added`/`### Changed`/`### Fixed`/`### Removed` subsection matching the nature of the change. Never add or edit content under an already-released version heading —...","repository":"can1357/oh-my-pi","domain":"docs","topic":"Documentation","language":"Markdown","updated":"2026-10-31","comments":21,"stars":37317,"raw":"https://awesomereviewers.com/raw/oh-my-pi-changelog-entry-conventions.md"},{"slug":"hermes-agent-doc-accuracy-and-conformance","title":"Doc accuracy and conformance","description":"Require every documentation change to pass two gates: (1) strict doc-schema conformance, and (2) factual/behavioral accuracy against the implementation and shipped artifacts.","repository":"nousresearch/hermes-agent","domain":"ai-agents","topic":"Documentation","language":"Markdown","updated":"2026-07-28","comments":18,"stars":221948,"raw":"https://awesomereviewers.com/raw/hermes-agent-doc-accuracy-and-conformance.md"},{"slug":"apisix-docs-match-implementation","title":"Docs Match Implementation","description":"Docs must be verifiable against the actual plugin/runtime behavior: schemas (fields/types/requiredness), defaults, and example outputs. Additionally, follow the repo’s established doc formatting conventions for things like canonical tags and secret-value prefixes.","repository":"apache/apisix","domain":"cloud-infra","topic":"Documentation","language":"Markdown","updated":"2026-04-27","comments":16,"stars":16922,"raw":"https://awesomereviewers.com/raw/apisix-docs-match-implementation.md"},{"slug":"svelte-realistic-documentation-examples","title":"realistic documentation examples","description":"Use practical, complete examples in documentation rather than oversimplified or contrived ones that cut corners. Documentation examples should reflect real-world usage patterns and include necessary context, edge cases, and limitations.","repository":"sveltejs/svelte","domain":"app-frameworks","topic":"Documentation","language":"Markdown","updated":"2025-07-15","comments":15,"stars":83580,"raw":"https://awesomereviewers.com/raw/svelte-realistic-documentation-examples.md"},{"slug":"electron-provide-contextual-explanations","title":"Provide contextual explanations","description":"Documentation should explain not just what APIs and features do, but when, why, and how to use them. Provide sufficient context for developers to understand the purpose, appropriate use cases, and practical implementation details.","repository":"electron/electron","domain":"devtools","topic":"Documentation","language":"Markdown","updated":"2025-06-26","comments":12,"stars":117644,"raw":"https://awesomereviewers.com/raw/electron-provide-contextual-explanations.md"},{"slug":"promptfoo-verify-documentation-against-behavior","title":"Verify documentation against behavior","description":"Every factual claim in documentation—links, API endpoints, default behaviors, required vs. optional settings, supported capabilities, and setup commands—must be verified against the actual running system (built site, source code, or live execution) before publishing, not assumed. Precisely scope statements to the environment or configuration they apply to,...","repository":"promptfoo/promptfoo","domain":"ai-agents","topic":"Documentation","language":"Markdown","updated":"2026-10-18","comments":11,"stars":26565,"raw":"https://awesomereviewers.com/raw/promptfoo-verify-documentation-against-behavior.md"},{"slug":"langflow-organize-documentation-content","title":"Organize documentation content","description":"Structure documentation to prevent information overload and improve readability by using appropriate organizational elements and callouts judiciously.","repository":"langflow-ai/langflow","domain":"ai-agents","topic":"Documentation","language":"Markdown","updated":"2025-07-14","comments":11,"stars":111046,"raw":"https://awesomereviewers.com/raw/langflow-organize-documentation-content.md"},{"slug":"nuxt-precise-language-usage","title":"precise language usage","description":"Use precise, natural language in documentation to improve clarity and readability. Focus on accurate word choice, proper grammar, and natural phrasing that flows well for readers.","repository":"nuxt/nuxt","domain":"app-frameworks","topic":"Documentation","language":"Markdown","updated":"2025-04-09","comments":11,"stars":57769,"raw":"https://awesomereviewers.com/raw/nuxt-precise-language-usage.md"},{"slug":"freecodecamp-documentation-clarity-rules","title":"Documentation clarity rules","description":"When writing technical curriculum/docs, ensure the content is (a) accurate, (b) unambiguous about what learners must do and what the expected output/input is, and (c) consistent in formatting and tone.","repository":"freeCodeCamp/freeCodeCamp","domain":"docs","topic":"Documentation","language":"Markdown","updated":"2026-05-08","comments":10,"stars":444449,"raw":"https://awesomereviewers.com/raw/freecodecamp-documentation-clarity-rules.md"},{"slug":"jj-define-technical-terms-clearly","title":"Define technical terms clearly","description":"Always define technical terms and concepts explicitly in documentation rather than assuming reader knowledge. Avoid ambiguous phrasing that could be interpreted multiple ways.","repository":"jj-vcs/jj","domain":"devtools","topic":"Documentation","language":"Markdown","updated":"2025-10-11","comments":10,"stars":21171,"raw":"https://awesomereviewers.com/raw/jj-define-technical-terms-clearly.md"},{"slug":"30-seconds-of-code-document-behavior-clearly","title":"Document behavior clearly","description":"For every snippet/glossary entry, the documentation must make the implementation’s behavior and constraints immediately clear—especially anything that can surprise users.","repository":"30-seconds/30-seconds-of-code","domain":"docs","topic":"Documentation","language":"Markdown","updated":"2020-09-16","comments":10,"stars":129334,"raw":"https://awesomereviewers.com/raw/30-seconds-of-code-document-behavior-clearly.md"}],"prompt_count":119}]}