@oddessentials/repo-standards 1.2.1 → 2.0.0

package/dist/config/standards.go.github-actions.json

@@ -35,6 +35,12 @@
         "id": "linting",
         "label": "Linting",
         "stack": {
+          "bazelHints": {
+            "commands": [
+              "bazel test //... --@io_bazel_rules_go//go/config:nogo=@//:nogo"
+            ],
+            "notes": "Use nogo for static analysis via rules_go. Configure nogo target with desired analyzers."
+          },
           "exampleConfigFiles": [
             ".golangci.yml",
             ".golangci.yaml"
@@ -64,6 +70,12 @@
         "id": "unit-test-runner",
         "label": "Unit Test Runner",
         "stack": {
+          "bazelHints": {
+            "commands": [
+              "bazel test //..."
+            ],
+            "notes": "rules_go go_test targets wrap 'go test' with Bazel's caching and hermeticity."
+          },
           "exampleConfigFiles": [
             "go.mod"
           ],
@@ -157,6 +169,12 @@
         "id": "unit-test-reporter",
         "label": "Unit Test Reporter / Coverage",
         "stack": {
+          "bazelHints": {
+            "commands": [
+              "bazel coverage //..."
+            ],
+            "notes": "rules_go supports coverage via bazel coverage. Use --combined_report=lcov for aggregated output."
+          },
           "exampleConfigFiles": [
             "go.mod"
           ],
@@ -178,6 +196,13 @@
         "id": "ci-quality-gates",
         "label": "CI Quality Gates",
         "stack": {
+          "bazelHints": {
+            "commands": [
+              "bazel build //...",
+              "bazel test //..."
+            ],
+            "notes": "rules_go go_binary and go_test targets provide hermetic builds and tests."
+          },
           "exampleConfigFiles": [
             ".github/workflows/*",
             "azure-pipelines.yml"
@@ -197,6 +222,12 @@
         "id": "code-formatter",
         "label": "Code Formatter",
         "stack": {
+          "bazelHints": {
+            "commands": [
+              "bazel run @go_sdk//:bin/gofmt -- -d ."
+            ],
+            "notes": "Run gofmt via the Bazel-managed Go SDK for hermetic formatting checks."
+          },
           "exampleConfigFiles": [],
           "exampleTools": [
             "gofmt",
@@ -238,6 +269,12 @@
         "id": "type-checking",
         "label": "Type Checking",
         "stack": {
+          "bazelHints": {
+            "commands": [
+              "bazel build //..."
+            ],
+            "notes": "Go type checking is inherent to compilation. bazel build with rules_go enforces type safety."
+          },
           "exampleConfigFiles": [
             "go.mod"
           ],
@@ -515,6 +552,43 @@
     "github-actions"
   ],
   "meta": {
+    "bazelIntegration": {
+      "advisoryNotice": "bazelHints are suggestions, not required execution paths. Consumers should prefer stack-native commands unless explicitly adopting Bazel.",
+      "ciContract": {
+        "configFlag": "--config=ci (define in .bazelrc)",
+        "deterministicFlags": [
+          "--nokeep_going",
+          "--test_output=errors"
+        ],
+        "remoteCache": "Optional; not required for CI",
+        "versionPinning": "Use .bazelversion file for Bazelisk"
+      },
+      "description": "Bazel build executor support for quality checks. All hints are ADVISORY—stack-native commands remain the default execution path.",
+      "detectionRules": {
+        "notes": "Detection uses repo-root markers only. Nested BUILD files do not trigger Bazel mode.",
+        "optionalMarkers": [
+          ".bazelrc",
+          ".bazelversion"
+        ],
+        "rootMarkers": [
+          "MODULE.bazel",
+          "WORKSPACE.bazel",
+          "WORKSPACE"
+        ]
+      },
+      "optOut": {
+        "configPath": "meta.bazelIntegration.enabled",
+        "description": "Set meta.bazelIntegration.enabled = false in repo config to disable Bazel hints"
+      },
+      "targetConventions": {
+        "build": "bazel build //...",
+        "coverage": "bazel coverage //...",
+        "description": "Recommended target naming (not assumed to exist). These are illustrative patterns; actual targets are repo-defined.",
+        "format": "bazel run //tools/format:check",
+        "lint": "//tools/lint:lint or bazel test //... with lint aspects",
+        "test": "bazel test //..."
+      }
+    },
     "complexityChecks": {
       "description": "When supported by the stack, run cyclomatic complexity or similar metrics in CI as a warning-only check initially.",
       "enabledByDefault": true

package/dist/config/standards.go.json

@@ -41,6 +41,12 @@
         "id": "linting",
         "label": "Linting",
         "stack": {
+          "bazelHints": {
+            "commands": [
+              "bazel test //... --@io_bazel_rules_go//go/config:nogo=@//:nogo"
+            ],
+            "notes": "Use nogo for static analysis via rules_go. Configure nogo target with desired analyzers."
+          },
           "exampleConfigFiles": [
             ".golangci.yml",
             ".golangci.yaml"
@@ -73,6 +79,12 @@
         "id": "unit-test-runner",
         "label": "Unit Test Runner",
         "stack": {
+          "bazelHints": {
+            "commands": [
+              "bazel test //..."
+            ],
+            "notes": "rules_go go_test targets wrap 'go test' with Bazel's caching and hermeticity."
+          },
           "exampleConfigFiles": [
             "go.mod"
           ],
@@ -178,6 +190,12 @@
         "id": "unit-test-reporter",
         "label": "Unit Test Reporter / Coverage",
         "stack": {
+          "bazelHints": {
+            "commands": [
+              "bazel coverage //..."
+            ],
+            "notes": "rules_go supports coverage via bazel coverage. Use --combined_report=lcov for aggregated output."
+          },
           "exampleConfigFiles": [
             "go.mod"
           ],
@@ -202,6 +220,13 @@
         "id": "ci-quality-gates",
         "label": "CI Quality Gates",
         "stack": {
+          "bazelHints": {
+            "commands": [
+              "bazel build //...",
+              "bazel test //..."
+            ],
+            "notes": "rules_go go_binary and go_test targets provide hermetic builds and tests."
+          },
           "exampleConfigFiles": [
             ".github/workflows/*",
             "azure-pipelines.yml"
@@ -224,6 +249,12 @@
         "id": "code-formatter",
         "label": "Code Formatter",
         "stack": {
+          "bazelHints": {
+            "commands": [
+              "bazel run @go_sdk//:bin/gofmt -- -d ."
+            ],
+            "notes": "Run gofmt via the Bazel-managed Go SDK for hermetic formatting checks."
+          },
           "exampleConfigFiles": [],
           "exampleTools": [
             "gofmt",
@@ -271,6 +302,12 @@
         "id": "type-checking",
         "label": "Type Checking",
         "stack": {
+          "bazelHints": {
+            "commands": [
+              "bazel build //..."
+            ],
+            "notes": "Go type checking is inherent to compilation. bazel build with rules_go enforces type safety."
+          },
           "exampleConfigFiles": [
             "go.mod"
           ],
@@ -584,6 +621,43 @@
     "github-actions"
   ],
   "meta": {
+    "bazelIntegration": {
+      "advisoryNotice": "bazelHints are suggestions, not required execution paths. Consumers should prefer stack-native commands unless explicitly adopting Bazel.",
+      "ciContract": {
+        "configFlag": "--config=ci (define in .bazelrc)",
+        "deterministicFlags": [
+          "--nokeep_going",
+          "--test_output=errors"
+        ],
+        "remoteCache": "Optional; not required for CI",
+        "versionPinning": "Use .bazelversion file for Bazelisk"
+      },
+      "description": "Bazel build executor support for quality checks. All hints are ADVISORY—stack-native commands remain the default execution path.",
+      "detectionRules": {
+        "notes": "Detection uses repo-root markers only. Nested BUILD files do not trigger Bazel mode.",
+        "optionalMarkers": [
+          ".bazelrc",
+          ".bazelversion"
+        ],
+        "rootMarkers": [
+          "MODULE.bazel",
+          "WORKSPACE.bazel",
+          "WORKSPACE"
+        ]
+      },
+      "optOut": {
+        "configPath": "meta.bazelIntegration.enabled",
+        "description": "Set meta.bazelIntegration.enabled = false in repo config to disable Bazel hints"
+      },
+      "targetConventions": {
+        "build": "bazel build //...",
+        "coverage": "bazel coverage //...",
+        "description": "Recommended target naming (not assumed to exist). These are illustrative patterns; actual targets are repo-defined.",
+        "format": "bazel run //tools/format:check",
+        "lint": "//tools/lint:lint or bazel test //... with lint aspects",
+        "test": "bazel test //..."
+      }
+    },
     "complexityChecks": {
       "description": "When supported by the stack, run cyclomatic complexity or similar metrics in CI as a warning-only check initially.",
       "enabledByDefault": true

package/dist/config/standards.json

@@ -118,6 +118,12 @@
         "label": "Linting",
         "stackHints": {
           "csharp-dotnet": {
+            "bazelHints": {
+              "commands": [
+                "bazel build //... --aspects=@rules_dotnet//dotnet:analyzers.bzl%analyzer_aspect"
+              ],
+              "notes": "Use rules_dotnet analyzer aspects for Roslyn-based linting in Bazel."
+            },
             "exampleConfigFiles": [
               ".editorconfig",
               "Directory.Build.props"
@@ -139,6 +145,12 @@
             "verification": ".editorconfig must exist to drive the .NET formatting and analysis tooling."
           },
           "go": {
+            "bazelHints": {
+              "commands": [
+                "bazel test //... --@io_bazel_rules_go//go/config:nogo=@//:nogo"
+              ],
+              "notes": "Use nogo for static analysis via rules_go. Configure nogo target with desired analyzers."
+            },
             "exampleConfigFiles": [
               ".golangci.yml",
               ".golangci.yaml"
@@ -158,6 +170,13 @@
             "verification": ".golangci.yml or .golangci.yaml indicates linting is configured. Run 'golangci-lint run' to verify."
           },
           "python": {
+            "bazelHints": {
+              "commands": [
+                "bazel test //...:ruff_test",
+                "bazel run //tools/lint:ruff -- check ."
+              ],
+              "notes": "Use rules_python with ruff wrapped as py_test or a custom run target."
+            },
             "exampleConfigFiles": [
               "pyproject.toml",
               ".flake8"
@@ -180,6 +199,12 @@
             "verification": "pyproject.toml (or ruff.toml / .flake8) signals that linting tools are configured for the repository."
           },
           "rust": {
+            "bazelHints": {
+              "commands": [
+                "bazel build //... --aspects=@rules_rust//rust:defs.bzl%clippy_aspect --output_groups=clippy_checks"
+              ],
+              "notes": "rules_rust includes clippy_aspect for Bazel-native Clippy linting on all Rust targets."
+            },
             "exampleConfigFiles": [
               "clippy.toml",
               ".clippy.toml"
@@ -199,6 +224,15 @@
             "verification": "Clippy is available via rustup component. Run 'cargo clippy' to verify linting is configured."
           },
           "typescript-js": {
+            "bazelHints": {
+              "commands": [
+                "bazel test //... --aspects=//tools:lint.bzl%eslint_aspect --output_groups=report"
+              ],
+              "notes": "Wrap eslint via aspect_rules_lint or a custom sh_test rule. Aspect-based linting runs on all source files.",
+              "recommendedTargets": [
+                "//tools/lint:lint"
+              ]
+            },
             "exampleConfigFiles": [
               ".eslintrc.*"
             ],
@@ -250,6 +284,12 @@
         "label": "Unit Test Runner",
         "stackHints": {
           "csharp-dotnet": {
+            "bazelHints": {
+              "commands": [
+                "bazel test //..."
+              ],
+              "notes": "Use rules_dotnet to define test targets for xUnit/NUnit/MSTest projects."
+            },
             "exampleConfigFiles": [
               "*.Tests.csproj"
             ],
@@ -265,6 +305,12 @@
             "verification": "Test projects are present in the solution; test configuration is defined."
           },
           "go": {
+            "bazelHints": {
+              "commands": [
+                "bazel test //..."
+              ],
+              "notes": "rules_go go_test targets wrap 'go test' with Bazel's caching and hermeticity."
+            },
             "exampleConfigFiles": [
               "go.mod"
             ],
@@ -279,6 +325,12 @@
             "verification": "Run 'go test ./...' to verify the test suite is configured and passing."
           },
           "python": {
+            "bazelHints": {
+              "commands": [
+                "bazel test //..."
+              ],
+              "notes": "Use rules_python py_test for pytest-based tests. Tests are hermetically isolated."
+            },
             "exampleConfigFiles": [
               "pytest.ini",
               "pyproject.toml"
@@ -298,6 +350,12 @@
             "verification": "Test framework configuration is present; tests/ directory or pytest configuration exists."
           },
           "rust": {
+            "bazelHints": {
+              "commands": [
+                "bazel test //..."
+              ],
+              "notes": "rules_rust rust_test targets run cargo test under Bazel's hermetic environment."
+            },
             "exampleConfigFiles": [
               "Cargo.toml"
             ],
@@ -314,6 +372,12 @@
             "verification": "Run 'cargo test' to verify the test suite is configured and passing."
           },
           "typescript-js": {
+            "bazelHints": {
+              "commands": [
+                "bazel test //..."
+              ],
+              "notes": "Bazel discovers and runs all test targets. Use rules_js for Jest/Vitest integration."
+            },
             "exampleConfigFiles": [
               "jest.config.*"
             ],
@@ -625,6 +689,12 @@
         "label": "Unit Test Reporter / Coverage",
         "stackHints": {
           "csharp-dotnet": {
+            "bazelHints": {
+              "commands": [
+                "bazel coverage //..."
+              ],
+              "notes": "Use rules_dotnet with coverage instrumentation enabled."
+            },
             "exampleConfigFiles": [
               "*.csproj"
             ],
@@ -636,6 +706,12 @@
             "verification": "Run the test suite with coverage enabled (for example, using coverlet or a similar tool) and verify that coverage reports are generated and used in CI to monitor thresholds."
           },
           "go": {
+            "bazelHints": {
+              "commands": [
+                "bazel coverage //..."
+              ],
+              "notes": "rules_go supports coverage via bazel coverage. Use --combined_report=lcov for aggregated output."
+            },
             "exampleConfigFiles": [
               "go.mod"
             ],
@@ -647,6 +723,12 @@
             "verification": "Run 'go test -cover ./...' and verify coverage reports are produced and thresholds monitored."
           },
           "python": {
+            "bazelHints": {
+              "commands": [
+                "bazel coverage //..."
+              ],
+              "notes": "Use rules_python py_test with coverage instrumentation. Combine with --combined_report=lcov."
+            },
             "exampleConfigFiles": [
               "pytest.ini",
               "pyproject.toml"
@@ -660,6 +742,12 @@
             "verification": "Run the unit tests with coverage (for example, pytest with pytest-cov) and confirm that coverage reports are generated and referenced in CI to enforce or track thresholds."
           },
           "rust": {
+            "bazelHints": {
+              "commands": [
+                "bazel coverage //..."
+              ],
+              "notes": "Bazel coverage with rules_rust requires LLVM instrumentation. May need additional toolchain configuration."
+            },
             "exampleConfigFiles": [
               "Cargo.toml"
             ],
@@ -672,6 +760,12 @@
             "verification": "Run 'cargo tarpaulin' or equivalent and verify coverage reports are generated and thresholds enforced."
           },
           "typescript-js": {
+            "bazelHints": {
+              "commands": [
+                "bazel coverage //..."
+              ],
+              "notes": "Bazel coverage collects coverage data from all test targets. Use --combined_report=lcov for aggregated reports."
+            },
             "exampleConfigFiles": [
               "jest.config.*"
             ],
@@ -707,6 +801,13 @@
         "label": "CI Quality Gates",
         "stackHints": {
           "csharp-dotnet": {
+            "bazelHints": {
+              "commands": [
+                "bazel build //...",
+                "bazel test //..."
+              ],
+              "notes": "Bazel handles all analysis, testing, and packaging via defined targets."
+            },
             "exampleConfigFiles": [
               ".github/workflows/*",
               "azure-pipelines.yml"
@@ -716,6 +817,13 @@
             "verification": "Open the CI configuration and verify there is a job or stage that runs analyzers, tests, build, and any required packaging or container checks before merging to main."
           },
           "go": {
+            "bazelHints": {
+              "commands": [
+                "bazel build //...",
+                "bazel test //..."
+              ],
+              "notes": "rules_go go_binary and go_test targets provide hermetic builds and tests."
+            },
             "exampleConfigFiles": [
               ".github/workflows/*",
               "azure-pipelines.yml"
@@ -725,6 +833,13 @@
             "verification": "Verify CI runs golangci-lint, go test, and go build before merging to main."
           },
           "python": {
+            "bazelHints": {
+              "commands": [
+                "bazel build //...",
+                "bazel test //..."
+              ],
+              "notes": "Bazel py_binary and py_test targets replace traditional Python tooling."
+            },
             "exampleConfigFiles": [
               ".github/workflows/*",
               "azure-pipelines.yml"
@@ -734,6 +849,13 @@
             "verification": "Open the CI configuration and verify there is a job or stage that runs linting, type checking (if used), tests, and any packaging or container checks before merging to main."
           },
           "rust": {
+            "bazelHints": {
+              "commands": [
+                "bazel build //...",
+                "bazel test //..."
+              ],
+              "notes": "rules_rust provides rust_library, rust_test, and clippy_aspect for complete CI."
+            },
             "exampleConfigFiles": [
               ".github/workflows/*",
               "azure-pipelines.yml"
@@ -743,6 +865,13 @@
             "verification": "Verify CI runs cargo clippy, cargo test, and cargo build before merging to main."
           },
           "typescript-js": {
+            "bazelHints": {
+              "commands": [
+                "bazel build //...",
+                "bazel test //..."
+              ],
+              "notes": "Replace npm run ci with Bazel commands. All quality gates run as Bazel targets."
+            },
             "exampleConfigFiles": [
               ".github/workflows/*",
               "azure-pipelines.yml"
@@ -776,6 +905,12 @@
         "label": "Code Formatter",
         "stackHints": {
           "csharp-dotnet": {
+            "bazelHints": {
+              "commands": [
+                "bazel run //tools/format:dotnet_format -- --verify-no-changes"
+              ],
+              "notes": "Wrap dotnet format as a Bazel run target."
+            },
             "exampleConfigFiles": [
               ".editorconfig"
             ],
@@ -786,6 +921,12 @@
             "verification": "Run the configured formatter or code style enforcement (for example, `dotnet format`) and confirm that code in the repository conforms to the defined rules."
           },
           "go": {
+            "bazelHints": {
+              "commands": [
+                "bazel run @go_sdk//:bin/gofmt -- -d ."
+              ],
+              "notes": "Run gofmt via the Bazel-managed Go SDK for hermetic formatting checks."
+            },
             "exampleConfigFiles": [],
             "exampleTools": [
               "gofmt",
@@ -795,6 +936,12 @@
             "verification": "Run 'gofmt -d .' or 'goimports -d .' and confirm no output indicates clean formatting."
           },
           "python": {
+            "bazelHints": {
+              "commands": [
+                "bazel run //tools/format:black -- --check ."
+              ],
+              "notes": "Wrap black as a py_binary run target for format checking."
+            },
             "exampleConfigFiles": [
               "pyproject.toml"
             ],
@@ -805,6 +952,12 @@
             "verification": "Run the configured formatter (for example, `black .` or `black --check .`) and confirm it reports clean formatting on committed code and auto-fixes as expected locally."
           },
           "rust": {
+            "bazelHints": {
+              "commands": [
+                "bazel build //... --aspects=@rules_rust//rust:defs.bzl%rustfmt_aspect --output_groups=rustfmt_checks"
+              ],
+              "notes": "rules_rust includes rustfmt_aspect for Bazel-native format checking."
+            },
             "exampleConfigFiles": [
               "rustfmt.toml",
               ".rustfmt.toml"
@@ -816,6 +969,13 @@
             "verification": "Run 'cargo fmt --check' and confirm it reports clean formatting. Use 'cargo fmt' to auto-fix."
           },
           "typescript-js": {
+            "bazelHints": {
+              "commands": [
+                "bazel run //tools/format:check",
+                "bazel test //...:format_test"
+              ],
+              "notes": "Wrap Prettier as a run target for formatting checks. Use aspect_rules_lint for format aspects."
+            },
             "exampleConfigFiles": [
               ".prettierrc.*",
               ".prettierignore"
@@ -930,6 +1090,12 @@
         "label": "Type Checking",
         "stackHints": {
           "csharp-dotnet": {
+            "bazelHints": {
+              "commands": [
+                "bazel build //..."
+              ],
+              "notes": "C# type errors surface during bazel build with rules_dotnet. No separate typecheck step needed."
+            },
             "exampleConfigFiles": [
               ".editorconfig",
               "Directory.Build.props",
@@ -951,6 +1117,12 @@
             "verification": ".editorconfig must exist; Directory.Build.props is optional for shared build configuration."
           },
           "go": {
+            "bazelHints": {
+              "commands": [
+                "bazel build //..."
+              ],
+              "notes": "Go type checking is inherent to compilation. bazel build with rules_go enforces type safety."
+            },
             "exampleConfigFiles": [
               "go.mod"
             ],
@@ -965,6 +1137,13 @@
             "verification": "Run 'go build ./...' to verify type correctness. Use 'go vet ./...' for additional static analysis."
           },
           "python": {
+            "bazelHints": {
+              "commands": [
+                "bazel test //...:mypy_test",
+                "bazel run //tools/typecheck:mypy"
+              ],
+              "notes": "Wrap mypy as a py_test or run target for Bazel-based type checking."
+            },
             "exampleConfigFiles": [
               "mypy.ini",
               "pyproject.toml"
@@ -985,6 +1164,12 @@
             "verification": "pyproject.toml (or mypy.ini) signals that mypy configuration is available for the repository."
           },
           "rust": {
+            "bazelHints": {
+              "commands": [
+                "bazel build //..."
+              ],
+              "notes": "Rust type checking is inherent to compilation. bazel build with rules_rust enforces type safety."
+            },
             "exampleConfigFiles": [
               "Cargo.toml"
             ],
@@ -998,6 +1183,12 @@
             "verification": "Run 'cargo check' or 'cargo build' to verify type correctness. All Rust code is type-checked by default."
           },
           "typescript-js": {
+            "bazelHints": {
+              "commands": [
+                "bazel build //..."
+              ],
+              "notes": "TypeScript type errors surface during bazel build with rules_ts. No separate typecheck step needed."
+            },
             "exampleConfigFiles": [
               "tsconfig.json"
             ],
@@ -2043,6 +2234,43 @@
     "github-actions"
   ],
   "meta": {
+    "bazelIntegration": {
+      "advisoryNotice": "bazelHints are suggestions, not required execution paths. Consumers should prefer stack-native commands unless explicitly adopting Bazel.",
+      "ciContract": {
+        "configFlag": "--config=ci (define in .bazelrc)",
+        "deterministicFlags": [
+          "--nokeep_going",
+          "--test_output=errors"
+        ],
+        "remoteCache": "Optional; not required for CI",
+        "versionPinning": "Use .bazelversion file for Bazelisk"
+      },
+      "description": "Bazel build executor support for quality checks. All hints are ADVISORY—stack-native commands remain the default execution path.",
+      "detectionRules": {
+        "notes": "Detection uses repo-root markers only. Nested BUILD files do not trigger Bazel mode.",
+        "optionalMarkers": [
+          ".bazelrc",
+          ".bazelversion"
+        ],
+        "rootMarkers": [
+          "MODULE.bazel",
+          "WORKSPACE.bazel",
+          "WORKSPACE"
+        ]
+      },
+      "optOut": {
+        "configPath": "meta.bazelIntegration.enabled",
+        "description": "Set meta.bazelIntegration.enabled = false in repo config to disable Bazel hints"
+      },
+      "targetConventions": {
+        "build": "bazel build //...",
+        "coverage": "bazel coverage //...",
+        "description": "Recommended target naming (not assumed to exist). These are illustrative patterns; actual targets are repo-defined.",
+        "format": "bazel run //tools/format:check",
+        "lint": "//tools/lint:lint or bazel test //... with lint aspects",
+        "test": "bazel test //..."
+      }
+    },
     "complexityChecks": {
       "description": "When supported by the stack, run cyclomatic complexity or similar metrics in CI as a warning-only check initially.",
       "enabledByDefault": true