Coryking Plugins — Code Quality skill for Claude Code

coryking-plugins

**A Claude Code marketplace for people who drive a fleet of agents and want to know what the hell those agents actually did.**

Three plugins, one install command. The one I get the most mileage out of, by a mile, is **cc-explorer** — my window into the pile of Claude Code transcripts I'd otherwise never read back. I use it to:

• Carry session context across conversations — pull what one session knew into wherever I'm working now.
• Run design and code reviews with a session that lived the work — clone a past session into a subagent and put it on the review.
• Mine my chat history for insights and data — find the decision, the realization, the moment things turned, even when I've forgotten which project it happened in.
• Watch how agents actually use the tools I write — see which MCP tools land, which fail, and where a subagent went sideways.
• Interrogate old sessions instead of grepping their transcripts — ask a past conversation what it meant, not just what it said.

The rest of the toolbox grew out of the same itch: tools to mine a project's history for evidence, to review the code these agents write, and to write better MCP servers.

/plugin marketplace add coryking/coryking-plugins

That registers the marketplace. Then enable whichever plugins you want (`/plugin`). Jump to **[Install](#install)** for the full path — including the one env var the session-interrogation feature genuinely needs.

---

What's in the box

Plugin	What it's for	The headline thing
project-mining	Read your own history back	cc-explorer (the star) + an evidence-mining orchestrator + an attention-reflection report
engineering-loop	Review code before you ship it	Parallel multi-persona code review, slimmed down for solo work
squabble	Argue over a design before you build it	An eight-role review panel with a debate loop that provably ends
mcp-authoring	Write MCP tools the