JKamsker

GitHub-issue-graph protocol for a continuous, lens-sharded bug hunt. Use inside the dispatcher/explore workflows to record findings and coordinate parallel agents through GitHub issues - read the lens frontier, dedup against the graph and open PRs, log the investigation trail as lens comments, dispatch the red-test proof, and mark lens status. Pairs with the library-surprise-sweep technique skill, which finds and proves a single surprise.

Find and fix "library surprise" behavior where public APIs, attributes, generators, docs, or runtime contracts imply support but the implementation silently skips, lowers the wrong shape, misbehaves at runtime, or accepts unsupported input. Use when asked to harden a library, source generator, analyzer, RPC/marshalling layer, public abstraction, or plugin/runtime workflow by either adding first-class support or failing closed with explicit compiler diagnostics, analyzer errors/warnings, or validation errors.

Merge GitHub pull requests matching the sweep fixed queue, especially `is:pr is:open label:sweep:fixed`, into the current integration branch one at a time. Use when asked to create an aggregate PR that references every source PR with checkboxes, commit/push/close each source PR after merge, keep the checklist updated, make CI green, and address or rebut all CodeRabbit review findings with conversations resolved.

Research and implement repo-specific parity updates between JKToolKit.CodexSDK and the vendored upstream Codex CLI in `external/codex`. Use when `UPSTREAM_CODEX_VERSION.json` or `external/codex` changes, when a user asks what changed in codex-cli since the last parity pass, or when you need to audit and fix drift in exec-mode, app-server DTOs/parsers, docs, tests, or generated schema interop.

Initialize a git repository with CodeEnforcer. Use when setting up a new or existing repo with git, a local dotnet tool manifest, the CodeEnforcer CLI as a local tool by default, CodeEnforcer config files, and pre-commit hooks.