Is your
AI code pakka
One disease, three symptoms — wasted tokens, shipped bugs, lost decisions. Pakka treats all three. A small, opinionated harness that wraps Claude Code with compression, gating, and recall.
Three primitives.
One harness.
Each command earns its place by removing a category of failure. No flags, no config. Auto-invoked from the conversation when needed.
compress.
the dietCondenses prompts & responses across turns. Fewer tokens in, fewer tokens out — without losing the load-bearing context.
gate.
the second opinionExit-code evidence before "done." Reviewer + security + architect + performance agents, anchored to the spec — no more vibes-based merges.
recall.
the medical recordCross-session memory for decisions. Ask pakka "why did we drop Redis?" three weeks later and get the conversation back.
What you'll actually see.
A request comes in. Pakka quietly chains plan → review → gate. You ship when the gate is green, not when the model says "done."
Same task. Two timelines.
A 2-week sprint adding rate limiting to four endpoints. Numbers from a real engagement, names redacted.
Two lines. Zero config.
Uses your existing Claude Code auth. No keys, no env vars, no flags. Add the marketplace, install the plugin, you're done.
Shipped, not announced.
Recent versions. Each tagged in main, signed, pushed to the marketplace.