chore: add vortex-coder and vortex-reviewer subagents#185
Merged
Conversation
Port the two-agent coder/reviewer pattern from zstd-java, retargeted to vortex-java: FFM zero-copy memory model, core/reader/writer module boundaries, hot-loop vectorization rules, untrusted-input parse contract, and Rust-interop integration tests as ground truth — all per CLAUDE.md. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Port the two-agent coder/reviewer pattern from
zstd-java, retargeted to vortex-java.What
vortex-coder— implements features/fixes/tests across core/reader/writer. Encodes the project's FFM zero-copy memory model (ctx.arena().allocate, nonew byte[]decode output), module boundaries (writernever depends onreader), hot-loop vectorization rules (no per-element modulo/division), encoding/extension add patterns, build commands, and test conventions — all fromCLAUDE.md.vortex-reviewer— read-only diff review prioritizing correctness/memory-safety: arena/segment lifetime, the untrusted-input parse contract (malformed →VortexException, route throughIoBounds.slice), hot-loop regressions, module boundaries, Rust-interop ground-truth tests, then style/build gates.Why
The zstd-java agents are zstd-specific (native sentinels,
zstd-jnicorpus); copied verbatim they'd describe the wrong project. Shared conventions (style, javadoc, BDD tests) carry over; domain specifics are swapped for vortex (columnar format,vortex-jniperf competitor, Rust correctness oracle).🤖 Generated with Claude Code