pyjinhx

Audit pyjinhx for dead code—removed API ghosts in code/docs/tests, symbols with no callers, obsolete backward-compat paths, unused parameters, and tests for deleted behavior. Use after refactors, API removals, or when the user asks to "sweep for dead code", "find unused code", or "remove leftovers". Read-only report.

Orchestrate a full structural code audit of pyjinhx using eight focused lenses (file responsibility, module placement, domain entities, state shape, duplication, indirection, public API, dead code). Use when the user asks to "audit the codebase", "sweep for quality", "review architecture", "audit reactive/", or before a large PR merge. Produces a merged read-only report; remediation is a separate pass unless requested.

Audit whether classes and module names match domain concepts—entities vs algorithms, ABC vs hub vs value object, procedural filenames vs type names. Use when naming new types, reviewing package structure, or asking "what should this be called". Read-only report.

Audit pyjinhx public API surface—pyjinhx.__all__, top-level exports vs canonical implementations, docs/reference/public-api.md alignment, tests/36_public_api_test.py. Use before releases, after refactors, or when removing deprecated symbols. Read-only.

Audit where mutable state lives in Python modules—module globals and ContextVars vs class classmethods, pure functions vs hubs, ABC vs coordinator split. Use when reviewing singletons, request scope, caches, or "should this be a class". Read-only.

Audit for duplicated workflows and parallel call sequences that will drift—same orchestration in two modules, duplicate parsing/validation, identical decorator and context-manager bodies. Use when reviewing refactors, merge conflicts, or "keep these in sync" code. Read-only report; documents intentional asymmetry.

Audit Python files for single responsibility—oversized modules, mixed concerns (parsing + algorithm + runtime in one file), misleading filenames, empty package __init__ without module maps. Use when a file feels crowded or before splitting a module. Read-only report.

Audit Python code for unnecessary indirection—thin wrappers, one-line factories, module functions that only delegate to classmethods, nested closures for capture, and internal re-export shims. Use when the user mentions indirection, wrappers, aliases, "just calls", or wants a delegation cleanup pass. Read-only report.

Audit Python package layering—which modules belong in core, reactive, integrations, or utils; framework-specific code in generic layers; forbidden upward imports. Use when asking "should this live in this file", moving adapters, or reviewing integration boundaries. Read-only report.