code-review
Pull request review checklist for finfocus. Lists the invariants a reviewer should check that linters and tests do not catch, such as secret redaction, stdout discipline, cache-key completeness, cost-math conventions, plugin module boundaries, MCP exposure, and test isolation.
Install
npx skills add https://github.com/rshade/finfocus/tree/main/.github/skills/code-review
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install rshade-finfocus@llmmart
git clone https://github.com/rshade/finfocus.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole rshade/finfocus collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
FinFocus Code Review
Use this skill when reviewing a pull request in this repository. General
conventions (build commands, testify, RunE, error wrapping, import order) are
in .github/copilot-instructions.md and .github/instructions/. This file
lists the project invariants that break silently, so a review should check
them explicitly.
Do not rely on a tool or Go version quoted in any prose file, including this
one. mise.toml pins every tool version (Go, golangci-lint, markdownlint,
actionlint, shellcheck) and go.mod holds the Go and finfocus-spec versions.
Read them from there, and flag a PR that changes a pin in one place but not
the files that mise.toml says must change with it.
Review Order and Severity
Review in this order, and label each comment with its severity:
- CRITICAL (block merge): secret or credential exposure, wrong cost output, corrupted output on stdout, data loss in the cache or history databases, broken plugin protocol compatibility.
- IMPORTANT (needs discussion): missing tests for a new path, a broken project invariant from this file, a mismatch with the linked issue or spec.
- SUGGESTION (non-blocking): simplification, naming, docs.
Use this comment shape:
**[SEVERITY] Area: short title**
What breaks, for which input or state.
**Suggested fix:** the smallest change, with code when it helps.
**Reference:** the rule in this skill, CLAUDE.md, or the spec.
How to Comment
- Report a defect only with a concrete failure scenario: the input or state, and the wrong output, leak, or crash it produces.
- Comment only on problems the PR introduces or makes reachable. Group findings that share one cause into one comment.
- Do not comment on formatting, import order, or anything golangci-lint, markdownlint, or actionlint already enforces.
- Passing CI is not evidence of correctness. Many rules below are not checked by any test.
- Do not flag a convention below as a bug when the code follows it on purpose. Several conventions look like errors at first glance (see "Intentional Conventions").
specs/**is planning material. Review it only for contradictions with the code in the same PR.CHANGELOG.mdis generated by release-please. Flag hand edits to it.
Review-Policy Changes
Copilot code review reads skills and instructions from the PR head branch, so
a PR can change the rules it is reviewed against. Treat changes to
.github/skills/, .github/copilot-instructions.md, .github/instructions/,
AGENTS.md, CLAUDE.md, .golangci.yml, and
.specify/memory/constitution.md as governance changes. Call out any change
that removes or weakens a review rule, a lint rule, or a coverage gate, and
ask for maintainer review of it. Never apply the PR's changed review rules to
the code in that same PR without saying so.
Spec Conformance
Most features have a Spec Kit folder specs/NNN-<name>/ whose number matches
the branch name. When the PR has one, or links an issue, read its
spec.md requirements and acceptance scenarios and check them against the
code. Flag a requirement the PR claims but does not implement, and behavior
the PR adds that the spec rules out. Use the GitHub MCP server to read a
linked issue.
Secrets Never Reach Plugins or Logs
- Resource properties reach plugins through tags (
ConvertToProto) andResourceDescriptor.attributes(engine.BuildAttributes). Both must drop credential-like keys throughisCredentialKey(internal/engine/flatten.go) and Pulumi secrets throughhistory.IsPulumiSecret. Flag any new path that copies properties into a request, a tag, a note, a log field, or a cache value without going through those helpers. Flag a second, separate credential or secret rule as well: there must be only one. - The scorer backend token (
SCORER_API_KEY) and any plugin credential must never appear in logs, errors, test fixtures, or committed files. - Recommendation scoring sends pseudonymized identifiers by default. Flag new
fields sent to a scorer that bypass
identifier_modeorfield_allowlist.
Stdout Is a Protocol
analyzer serveprints only the port number to stdout (Pulumi handshake). All other output from that path goes to stderr.- JSON and NDJSON output must contain only the document. Banners, budget boxes, warnings, and progress text in machine modes are bugs.
- Commands write through
cmd.Printf/cmd.OutOrStdout(), neverfmt.Printf, so tests and the MCP dispatcher can capture output. - A command with an output flag resolves it through
resolveOutputFormat(internal/cli/output_mode.go), which does not validate the value. The command must reject an unknown--outputitself, before it loads state or takes any early return on empty data. Otherwise an invalid value exits 0.
Cache Keys Must Cover Every Input
The projected, actual, Supports, recommendations, and score caches are
keyed by strings built in internal/engine. A cache hit after an input
changed returns a stale cost without any error. When a PR adds a new input
that can change a plugin answer (a request field, a tag, an attribute, a
flag such as --include-dismissed or --pricing-spec-fallback), check
that the matching cache key gains a suffix or digest for it. Check also that
runs without the input keep their existing key.
Cost Math
- Monthly hours are
730(hoursPerMonth).per_daypricing uses 30 days (daysPerMonth). Both are deliberate AWS conventions. Do not "fix" one to match the other. MTDCost(month to date) andMonthlyCost(full month) are different units. Subtracting one from the other without extrapolating first is a bug. Overview deltas come fromCalculateRowDelta, never inline arithmetic.row.CostDrift == nilis a normal state (early month, drift under 10%, new or deleted resource). Code that treats it as an error or dereferences it is a bug.- A replacement's
create-replacement,replace, anddelete-replacedsteps share a URN and must be collapsed into one entry, or the old resource is counted twice.
Intentional Conventions (Do Not Flag)
- Router fallback: a
$0.00result is valid and does not trigger fallback. Only nil or empty results do. - Cluster allocation is the opposite on purpose:
priceResourcestreatsMonthly <= 0as unpriced, because aws-public returns$0for unknown instance types. - A plugin pricing spec with a
$0rate is a priced result. - Router priority: a higher number means a higher priority.
GetExtrapolatedActualandForceExtrapolateActual(30-day) andCalculateCostDrift(calendar days) use different month lengths on purpose.
Providers
resourcetype.NormalizeProvider holds the only provider alias table
(aws-native to aws, azure-native/azurerm to azure,
google-native/google to gcp). Flag any code that splits a Pulumi type
token or lowercases a prefix to derive a provider instead of calling
resourcetype.ExtractProvider or NormalizeProvider.
Plugin Host and Plugins
- Every
cmd.Process.Kill()must be followed bycmd.Wait(), or the plugin becomes a zombie. - Core must not set the
PORTenv var for plugins. Plugins take--portorFINFOCUS_PLUGIN_PORT(pluginsdk.EnvPort). Env var names and gRPC metadata keys come frompluginsdkconstants, not string literals. - Every directory under
plugins/with its owngo.modis a separate module and must not importgithub.com/rshade/finfocus/internal/...or.../pkg/.... A PR that adds such a module must also add it to thecheck-plugin-boundariestarget in theMakefile. - Plugin-specific domain knowledge belongs in the plugin. Flag core changes that special-case one plugin's resource types or behavior instead of adding a generic channel.
- A finfocus-spec version bump must update
go.modin the root and in every nested plugin module to the same version. When it movespluginsdk.SpecVersion, it also needs ahops.goentry and anagent-skills/finfocus-plugin-upgrade/references/to-vX.Y.Z.mdguide.
Plugin RPC Contract
Core is the gRPC client of plugins built against older and newer finfocus-spec versions. Check that:
- Every new plugin call has a deadline.
GetPricingSpecusesperResourceTimeout(5s). An RPC with no deadline can hang a whole cost run on one stuck plugin. - New request fields are optional enrichment. A plugin built against an older
spec ignores unknown fields, so core must not depend on a plugin reading
them. Existing fields that older plugins rely on (such as the injected
sku/region/provider/resource_typetags on actual-cost requests) stay in place. - In projected and actual cost aggregation, a plugin error does not abort
processing other resources. It becomes a per-resource
ERROR:note, aPLUGIN_ERROR/TIMEOUT_ERRORcode, or a fallback to the next plugin. cost history collectis an intentional exception: an unpriced result or result error fails the checkpoint so an inaccurate total is never stored.- A
SupportsRPC error and the SDK's "not implemented" reason fail open (the plugin stays offered). - A failed plugin RPC keeps the plugin's own reason. Engine call sites wrap
the error with
pluginStatusError(internal/engine/engine.go), which renders it as<Code>: <message>(for exampleInvalidArgument: region is required for GetProjectedCost) throughpluginRPCErrorand still answersstatus.Code. Flag a new plugin call path that returns the raw gRPC error (rpc error: code = ... desc = ...), replaces it with a generic message, or wraps it with%vinstead of%w, which drops the status. Plugin text copied into a note (a decline reason, the first plugin error in anERROR:note, a pricing-spec failure) goes throughtruncateDeclineReason, which keeps at most 160 bytes (maxDeclineReasonLen) without splitting a rune and appends.... - Pre-flight validation failures become
VALIDATION:placeholders and never reach the plugin. - New batched requests stay under the gRPC message limit. Projected
BatchCostsplits chunks atmaxBatchRequestBytes(3 MiB); attributes overpluginsdk.MaxAttributesBytesare dropped with a warning. - Plugin handlers return gRPC status codes that mean what the spec says
(
InvalidArgumentfor bad input,Unauthenticatedfor a missing key,Unimplementedfor an unsupported RPC), notInternalorUnknownfor an expected failure.
Go Traps Not Caught by Lint
contextcheckis disabled in.golangci.yml. Flag a function that receives acontext.Contextand then callscontext.Background()orcontext.TODO(), because cancellation and the trace ID stop there.- Production code mutates proto messages and slices in place (for example
Engine.GetBudgetson a shared*pbc.Budget). Flag code that hands out a shared message or a sub-slice and then mutates it, or appends to a slice it does not own. - Writing to a nil map panics. Check maps built from optional proto or config fields before the first write.
- Goroutines that fan out plugin calls must stop on context cancellation and must not write shared maps or slices without a lock.
Packages and Commands
internal/historymust not importinternal/engineorinternal/ingest.- New CLI commands must make an MCP decision: either exposed (and listed in
internal/cli/testdata/mcp/tools.golden) or excluded throughapplyMCPExclusions. Excluding a command withHiddenis a bug, because ax-go then prunes the whole subtree. - Do not redefine a flag an ancestor already owns: ax-go's
--format,--dry-run, and--yes; the root's persistent--debugand--project-dir; and thecostcommand's persistent--exit-on-threshold,--exit-code,--notify,--budget-scope, and--stack. Cobra rejects the duplicate at runtime. A command outsidecost, such asoverview, may declare its own budget and stack flags. Accessibility flags (--plain,--no-color) are local to each output command, andaddAccessibilityFlagsadds only the ones a command lacks. - Budget CLI overrides (
--exit-on-threshold,--exit-code) must not be written ontoconfig.GetGlobalConfig(). - Pulumi plan parsing must read
newStateforinputsandtype. - Keys prefixed with
__in Pulumi inputs are SDK internals and must be filtered from user-facing output.
Tests
- Tests use testify
requireandassert, never manualif ... t.Errorf. - Tests that run a mutating command (
dismiss,snooze,config set, and similar) must sett.Setenv("FINFOCUS_HOME", t.TempDir()). Without it they write to the real~/.finfocusand become order-dependent. t.Parallel()is expected, except in tests that uset.Setenv,t.Chdir, swap package-level variables, build a root command (NewRootCmd*), or write and then execute a script or binary (ETXTBSY). Those carry//nolint:paralleltest // <reason>.- A parent test that starts parallel subtests must use
t.Cleanup, notdefer. Table-driven parallel subtests must build their fixtures inside the subtest, because production code mutates proto messages in place. - Integration tests run commands through
helpers.CLIHelper, which usesax.Execute. A directcli.NewRootCmd().Execute()does not mount the global flags. - E2E tests must run the real
finfocusbinary and must never stub cost values. - A
internal/tuichange that alters layout needs updated golden files.assert.Containson rendered output alone is not enough. - Every new error return needs a test that triggers it.
Completeness
The constitution (.specify/memory/constitution.md) forbids TODOs, stubs,
and placeholder implementations in merged code. Flag any TODO, FIXME,
panic("not implemented"), or a function that returns a zero value where the
PR description promises behavior.
Files (finfocus)
-
SKILL.md 13.9 KB
--- name: code-review description: Pull request review checklist for finfocus. Lists the invariants a reviewer should check that linters and tests do not catch, such as secret redaction, stdout discipline, cache-key completeness, cost-math conventions, plugin module boundaries, MCP exposure, and test isolation. --- # FinFocus Code Review Use this skill when reviewing a pull request in this repository. General conventions (build commands, testify, `RunE`, error wrapping, import order) are in `.github/copilot-instructions.md` and `.github/instructions/`. This file lists the project invariants that break silently, so a review should check them explicitly. Do not rely on a tool or Go version quoted in any prose file, including this one. `mise.toml` pins every tool version (Go, golangci-lint, markdownlint, actionlint, shellcheck) and `go.mod` holds the Go and finfocus-spec versions. Read them from there, and flag a PR that changes a pin in one place but not the files that `mise.toml` says must change with it. ## Review Order and Severity Review in this order, and label each comment with its severity: 1. **CRITICAL** (block merge): secret or credential exposure, wrong cost output, corrupted output on stdout, data loss in the cache or history databases, broken plugin protocol compatibility. 2. **IMPORTANT** (needs discussion): missing tests for a new path, a broken project invariant from this file, a mismatch with the linked issue or spec. 3. **SUGGESTION** (non-blocking): simplification, naming, docs. Use this comment shape: ```markdown **[SEVERITY] Area: short title** What breaks, for which input or state. **Suggested fix:** the smallest change, with code when it helps. **Reference:** the rule in this skill, CLAUDE.md, or the spec. ``` ## How to Comment - Report a defect only with a concrete failure scenario: the input or state, and the wrong output, leak, or crash it produces. - Comment only on problems the PR introduces or makes reachable. Group findings that share one cause into one comment. - Do not comment on formatting, import order, or anything golangci-lint, markdownlint, or actionlint already enforces. - Passing CI is not evidence of correctness. Many rules below are not checked by any test. - Do not flag a convention below as a bug when the code follows it on purpose. Several conventions look like errors at first glance (see "Intentional Conventions"). - `specs/**` is planning material. Review it only for contradictions with the code in the same PR. - `CHANGELOG.md` is generated by release-please. Flag hand edits to it. ## Review-Policy Changes Copilot code review reads skills and instructions from the PR head branch, so a PR can change the rules it is reviewed against. Treat changes to `.github/skills/`, `.github/copilot-instructions.md`, `.github/instructions/`, `AGENTS.md`, `CLAUDE.md`, `.golangci.yml`, and `.specify/memory/constitution.md` as governance changes. Call out any change that removes or weakens a review rule, a lint rule, or a coverage gate, and ask for maintainer review of it. Never apply the PR's changed review rules to the code in that same PR without saying so. ## Spec Conformance Most features have a Spec Kit folder `specs/NNN-<name>/` whose number matches the branch name. When the PR has one, or links an issue, read its `spec.md` requirements and acceptance scenarios and check them against the code. Flag a requirement the PR claims but does not implement, and behavior the PR adds that the spec rules out. Use the GitHub MCP server to read a linked issue. ## Secrets Never Reach Plugins or Logs - Resource properties reach plugins through tags (`ConvertToProto`) and `ResourceDescriptor.attributes` (`engine.BuildAttributes`). Both must drop credential-like keys through `isCredentialKey` (`internal/engine/flatten.go`) and Pulumi secrets through `history.IsPulumiSecret`. Flag any new path that copies properties into a request, a tag, a note, a log field, or a cache value without going through those helpers. Flag a second, separate credential or secret rule as well: there must be only one. - The scorer backend token (`SCORER_API_KEY`) and any plugin credential must never appear in logs, errors, test fixtures, or committed files. - Recommendation scoring sends pseudonymized identifiers by default. Flag new fields sent to a scorer that bypass `identifier_mode` or `field_allowlist`. ## Stdout Is a Protocol - `analyzer serve` prints only the port number to stdout (Pulumi handshake). All other output from that path goes to stderr. - JSON and NDJSON output must contain only the document. Banners, budget boxes, warnings, and progress text in machine modes are bugs. - Commands write through `cmd.Printf` / `cmd.OutOrStdout()`, never `fmt.Printf`, so tests and the MCP dispatcher can capture output. - A command with an output flag resolves it through `resolveOutputFormat` (`internal/cli/output_mode.go`), which does not validate the value. The command must reject an unknown `--output` itself, before it loads state or takes any early return on empty data. Otherwise an invalid value exits 0. ## Cache Keys Must Cover Every Input The projected, actual, `Supports`, recommendations, and score caches are keyed by strings built in `internal/engine`. A cache hit after an input changed returns a stale cost without any error. When a PR adds a new input that can change a plugin answer (a request field, a tag, an attribute, a flag such as `--include-dismissed` or `--pricing-spec-fallback`), check that the matching cache key gains a suffix or digest for it. Check also that runs without the input keep their existing key. ## Cost Math - Monthly hours are `730` (`hoursPerMonth`). `per_day` pricing uses 30 days (`daysPerMonth`). Both are deliberate AWS conventions. Do not "fix" one to match the other. - `MTDCost` (month to date) and `MonthlyCost` (full month) are different units. Subtracting one from the other without extrapolating first is a bug. Overview deltas come from `CalculateRowDelta`, never inline arithmetic. - `row.CostDrift == nil` is a normal state (early month, drift under 10%, new or deleted resource). Code that treats it as an error or dereferences it is a bug. - A replacement's `create-replacement`, `replace`, and `delete-replaced` steps share a URN and must be collapsed into one entry, or the old resource is counted twice. ## Intentional Conventions (Do Not Flag) - Router fallback: a `$0.00` result is valid and does not trigger fallback. Only nil or empty results do. - Cluster allocation is the opposite on purpose: `priceResources` treats `Monthly <= 0` as unpriced, because aws-public returns `$0` for unknown instance types. - A plugin pricing spec with a `$0` rate is a priced result. - Router priority: a higher number means a higher priority. - `GetExtrapolatedActual` and `ForceExtrapolateActual` (30-day) and `CalculateCostDrift` (calendar days) use different month lengths on purpose. ## Providers `resourcetype.NormalizeProvider` holds the only provider alias table (`aws-native` to `aws`, `azure-native`/`azurerm` to `azure`, `google-native`/`google` to `gcp`). Flag any code that splits a Pulumi type token or lowercases a prefix to derive a provider instead of calling `resourcetype.ExtractProvider` or `NormalizeProvider`. ## Plugin Host and Plugins - Every `cmd.Process.Kill()` must be followed by `cmd.Wait()`, or the plugin becomes a zombie. - Core must not set the `PORT` env var for plugins. Plugins take `--port` or `FINFOCUS_PLUGIN_PORT` (`pluginsdk.EnvPort`). Env var names and gRPC metadata keys come from `pluginsdk` constants, not string literals. - Every directory under `plugins/` with its own `go.mod` is a separate module and must not import `github.com/rshade/finfocus/internal/...` or `.../pkg/...`. A PR that adds such a module must also add it to the `check-plugin-boundaries` target in the `Makefile`. - Plugin-specific domain knowledge belongs in the plugin. Flag core changes that special-case one plugin's resource types or behavior instead of adding a generic channel. - A finfocus-spec version bump must update `go.mod` in the root and in every nested plugin module to the same version. When it moves `pluginsdk.SpecVersion`, it also needs a `hops.go` entry and an `agent-skills/finfocus-plugin-upgrade/references/to-vX.Y.Z.md` guide. ## Plugin RPC Contract Core is the gRPC client of plugins built against older and newer finfocus-spec versions. Check that: - Every new plugin call has a deadline. `GetPricingSpec` uses `perResourceTimeout` (5s). An RPC with no deadline can hang a whole cost run on one stuck plugin. - New request fields are optional enrichment. A plugin built against an older spec ignores unknown fields, so core must not depend on a plugin reading them. Existing fields that older plugins rely on (such as the injected `sku`/`region`/`provider`/`resource_type` tags on actual-cost requests) stay in place. - In projected and actual cost aggregation, a plugin error does not abort processing other resources. It becomes a per-resource `ERROR:` note, a `PLUGIN_ERROR`/`TIMEOUT_ERROR` code, or a fallback to the next plugin. - `cost history collect` is an intentional exception: an unpriced result or result error fails the checkpoint so an inaccurate total is never stored. - A `Supports` RPC error and the SDK's "not implemented" reason fail open (the plugin stays offered). - A failed plugin RPC keeps the plugin's own reason. Engine call sites wrap the error with `pluginStatusError` (`internal/engine/engine.go`), which renders it as `<Code>: <message>` (for example `InvalidArgument: region is required for GetProjectedCost`) through `pluginRPCError` and still answers `status.Code`. Flag a new plugin call path that returns the raw gRPC error (`rpc error: code = ... desc = ...`), replaces it with a generic message, or wraps it with `%v` instead of `%w`, which drops the status. Plugin text copied into a note (a decline reason, the first plugin error in an `ERROR:` note, a pricing-spec failure) goes through `truncateDeclineReason`, which keeps at most 160 bytes (`maxDeclineReasonLen`) without splitting a rune and appends `...`. - Pre-flight validation failures become `VALIDATION:` placeholders and never reach the plugin. - New batched requests stay under the gRPC message limit. Projected `BatchCost` splits chunks at `maxBatchRequestBytes` (3 MiB); attributes over `pluginsdk.MaxAttributesBytes` are dropped with a warning. - Plugin handlers return gRPC status codes that mean what the spec says (`InvalidArgument` for bad input, `Unauthenticated` for a missing key, `Unimplemented` for an unsupported RPC), not `Internal` or `Unknown` for an expected failure. ## Go Traps Not Caught by Lint - `contextcheck` is disabled in `.golangci.yml`. Flag a function that receives a `context.Context` and then calls `context.Background()` or `context.TODO()`, because cancellation and the trace ID stop there. - Production code mutates proto messages and slices in place (for example `Engine.GetBudgets` on a shared `*pbc.Budget`). Flag code that hands out a shared message or a sub-slice and then mutates it, or appends to a slice it does not own. - Writing to a nil map panics. Check maps built from optional proto or config fields before the first write. - Goroutines that fan out plugin calls must stop on context cancellation and must not write shared maps or slices without a lock. ## Packages and Commands - `internal/history` must not import `internal/engine` or `internal/ingest`. - New CLI commands must make an MCP decision: either exposed (and listed in `internal/cli/testdata/mcp/tools.golden`) or excluded through `applyMCPExclusions`. Excluding a command with `Hidden` is a bug, because ax-go then prunes the whole subtree. - Do not redefine a flag an ancestor already owns: ax-go's `--format`, `--dry-run`, and `--yes`; the root's persistent `--debug` and `--project-dir`; and the `cost` command's persistent `--exit-on-threshold`, `--exit-code`, `--notify`, `--budget-scope`, and `--stack`. Cobra rejects the duplicate at runtime. A command outside `cost`, such as `overview`, may declare its own budget and stack flags. Accessibility flags (`--plain`, `--no-color`) are local to each output command, and `addAccessibilityFlags` adds only the ones a command lacks. - Budget CLI overrides (`--exit-on-threshold`, `--exit-code`) must not be written onto `config.GetGlobalConfig()`. - Pulumi plan parsing must read `newState` for `inputs` and `type`. - Keys prefixed with `__` in Pulumi inputs are SDK internals and must be filtered from user-facing output. ## Tests - Tests use testify `require` and `assert`, never manual `if ... t.Errorf`. - Tests that run a mutating command (`dismiss`, `snooze`, `config set`, and similar) must set `t.Setenv("FINFOCUS_HOME", t.TempDir())`. Without it they write to the real `~/.finfocus` and become order-dependent. - `t.Parallel()` is expected, except in tests that use `t.Setenv`, `t.Chdir`, swap package-level variables, build a root command (`NewRootCmd*`), or write and then execute a script or binary (ETXTBSY). Those carry `//nolint:paralleltest // <reason>`. - A parent test that starts parallel subtests must use `t.Cleanup`, not `defer`. Table-driven parallel subtests must build their fixtures inside the subtest, because production code mutates proto messages in place. - Integration tests run commands through `helpers.CLIHelper`, which uses `ax.Execute`. A direct `cli.NewRootCmd().Execute()` does not mount the global flags. - E2E tests must run the real `finfocus` binary and must never stub cost values. - A `internal/tui` change that alters layout needs updated golden files. `assert.Contains` on rendered output alone is not enough. - Every new error return needs a test that triggers it. ## Completeness The constitution (`.specify/memory/constitution.md`) forbids TODOs, stubs, and placeholder implementations in merged code. Flag any `TODO`, `FIXME`, `panic("not implemented")`, or a function that returns a zero value where the PR description promises behavior.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.