Four MIT collections ported — growthOS, openclaw-marketing-skills, Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45 commands, each naming its origin in its own frontmatter so the tree can be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names appeared in more than one collection and none of the copies were identical; the longest wins, which lands on the more developed text where they genuinely diverge. A fifth collection is deliberately absent. awesome-growth-hacking-skills carries NO licence, which leaves its author every right by default — and it is a list of links rather than a collection of skills, so there is nothing in it to port and no permission to port it with. It is cited as a directory to read. THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing vendor SDKs, running OAuth flows of their own, and ending with long-lived credentials in JSON files under .agents/ and ~/.growthos/ at mode 600. That is a secret on a disk with no rotation path, protected from other users and not from the agent — and one auth implementation per skill. Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect` is the one home for the flow and the platform skills defer to it by provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a tool and a curl cannot disagree. Two had nothing real behind them and now say so. There is no search_console provider, so that skill names what does answer the same questions (google_analytics, google_bigquery) and states that the remedy is a provider in hanzoai/cloud rather than a vendor SDK here. And getxapi-connect was a wrapper around a paid reseller of X's public data with the vendor's key in an env var; it is `listen` now, on our own x connector — a skill named after a vendor makes the vendor the capability and dies with it. The skills referenced paths that only existed inside the source repo, so the shared material they read is ported to reference/ and the paths rewritten. Three skills need the growthOS APPLICATION rather than its data; per the estate's own split an application belongs in hanzoai/ads, social, email or sms as a cloud plugin, so those three say what they need instead of carrying an import that resolves to nothing. Third-party product names are out of our prose and kept in the notices, which is where the licence requires them and the only place they belong. A skill's persona names a role, not somebody else's product. Co-authored-by: Hanzo Dev <[email protected]>
8.6 KiB
Correctness taxonomy — thirteen lenses, with detection tells
Reference for the correctness sub-case — the core of the code-review skill. The performance and
security sub-cases have their own files alongside this one.
Overlapping diagnostic lenses, not a classification scheme and not a quota. Each entry says how you detect it, because a class name alone changes nothing about what a reviewer looks at.
Lenses 1 and 2 are the ones strong reviewers — human and machine — miss most often, and the only two that warrant an explicit forced probe rather than a read-through. Both are failures of looking, not of judgement: the code reads sensibly at each participant, and the defect exists only in the relationship between them.
1. Authority reconciliation
Follow a proposed value through validation, normalisation, negotiation or commit. Identify downstream state still derived from the proposal when the authority can legitimately return something different. Check that reconciliation happens before the first consequential use.
A requested value is not an applied value. Anywhere a system can say "I heard you, and here is what I actually did", the reply is the authority — and the request is not.
Probe: construct an execution where the effective answer differs from the requested one, then ask which stored state, which UI, which later call and which log line still carry the request.
2. Identity and correlation
Trace how an operation's result finds its originating entity. Establish the correlation key's uniqueness, stability and lifetime under overlapping operations, reordering, removal and reuse. A label, an index, a position or arrival order is suspicious exactly when one of those can fail.
Probe: run two operations concurrently and complete them out of order. Then remove one mid-flight and reuse its slot.
3. Freshness and generations
Mark every value captured before a yield, await, callback, timer or lock release. Determine what can change before it is used, and whether the operation still targets the intended entity and version. Check what the code actually does with a stale result — ignore, apply, or apply silently.
4. Lifecycle and derived state
Compare every reachable construction, replacement, restoration, reset, failure and termination path. Look for derived fields or cached decisions correctly re-established on one path and wrongly retained on another. Two paths that should end in equivalent state are an agreement like any other.
5. Atomicity and partial failure
Split multi-effect operations at each failure and cancellation point. Is partial state permitted, recoverable and accurately reported? Look for success reported before the required effects are durable.
6. Replay and effect cardinality
Follow retries, duplicate delivery, repeated callbacks and re-entry into effects. Compare the actual delivery guarantee against the required effect count — especially where an effect costs money, sends a message or mutates a shared total. Inspect deduplication scope, lifetime, and behaviour after partial success.
7. Composition and precedence
Trace independently produced pieces through merge, reduction, ordering and dispatch. Compare the real overwrite and selection rules against the intended authority or priority — including transformations applied after the merge that quietly re-order or re-key it.
8. Bounds, units and accounting
Follow counts, lengths, offsets, capacities and totals through every transformation. Check empty and boundary cases, overflow, rounding, and whether measurement and consumption use the same unit and representation.
9. Framing and incremental processing
Compare logical item boundaries against actual read, write, iterator and callback boundaries. Test split items, combined items, partial writes and early termination. Inspect buffering, flush and finalisation — especially the last item.
10. Representation and information loss
Compare the values a producer can emit against the distinctions a consumer relies on. Trace round-trips and derived outputs for distinctions that disappear. This is the highest-frequency class in every corpus examined - planted and natural - so give it more than one pass.
Three sub-shapes carry most of it:
- The nullish family. Pending, absent, empty, zero, false and failed are six different
states that collapse into each other with alarming ease. A failed read returning an empty result, a
never-started resource reported as broken, a guard that excludes
nullbut notundefined, an explicit null skipped as though the field were missing, a string"false"landing in a boolean, a sentinel like-1standing in for "no answer" and then being counted. Probe: for each value that can be missing, enumerate which of the six it can actually be, and check the consumer distinguishes the ones that matter. - Projection and field-set drift. A producer - a query, a DTO, a serialiser, a mapper - stops emitting a field, and consumers degrade silently rather than failing. Probe: diff the field set a producer actually selects against every field its consumers read, including nested projections and the fields a renderer touches. Also check for a field read under a name the producer never emits.
- Unresolved values stored as resolved ones. A promise, a future, a lazy handle or a still-loading state persisted or compared as though it were the settled value. Probe: anywhere a value has a "not ready yet" state, find who reads it without checking.
Then the ordinary axes: signed versus unsigned, canonical forms, precision, encoding, equality semantics.
Tell: a cast, an any, a non-null assertion or a suppressed warning at a boundary is where
contracts go to die - the annotation exists precisely because the two sides disagreed and someone
silenced the compiler rather than reconciling them. Treat every one of them on a boundary as a
candidate.
11. Ownership, completion and progress
Trace who may mutate, release, cancel and complete an operation or resource. Inspect exceptional exits and competing terminal paths for premature release, missing completion, deadlock, or use after ownership changed hands.
12. Decisions and dispatch
Enumerate the meaningful states and inputs for consequential predicates and dispatch tables. Compare branches against supported expectations: overlapping conditions, inverted tests, missing cases, and what the fallback actually does. Check the default a framework or language supplies when the code specifies nothing - an unstated default is still a decision.
Include reachability, not just correctness. Ask of each consequential branch whether any input can reach it, and of each scheduled or registered thing whether anything actually starts it. A predicate that can never be true, a handler never wired up, a writer whose output can never reach disk, and a job whose scheduler is never started are all defects that read as perfectly correct code. They are common in the wild and almost absent from planted corpora, so no checklist trained on planted bugs will prompt you to look.
13. Verification and observability
Follow what happens when each step fails, and ask what would make the failure visible. Look for checks that cannot fail, oracles that measure something other than the thing they claim to, exceptions swallowed into a success path, gates that skip their subject, and effects whose absence nothing would detect. A step that always passes is not a passing step.
Probe: for each guarantee the system claims, name the observation that would break if it stopped holding. If there is none, the guarantee is decorative.
This lens exists because of a gap in the evidence, and the gap is worth stating. A planted defect is detectable by construction - somebody planted it, so somebody can find it. Silent failure is therefore systematically absent from planted corpora and heavily represented in real fix histories, where "and nothing noticed" is a recurring phrase. Do not let a benchmark-shaped checklist talk you out of looking here.
Using these
- They overlap on purpose. One defect can be lens 1 and lens 3 at once; report the root cause once.
- Absence of findings under a lens is a valid result. Do not manufacture one to fill the table.
- Finding nothing under lenses 1 and 2 is worth a second look only if you never constructed their probes — a read-through reliably returns nothing here, which is exactly the failure mode.
- None of these is language- or framework-specific. If a lens seems inapplicable, say which property of the system makes it so.