Coxwave Claude Plugins
coxwave-claude-plugins is a Claude Code plugin marketplace for the Ship phase that bundles three Python-focused plugins for Ruff standards, specs, and hook-driven autofix during review.
by coxwave · github.com/coxwave/claude-plugins
Keep Python changes Ruff-clean and specification-shaped while Coxwave-style hooks autofix style and clarify vague requirements during Claude Code sessions.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install coxwave-claude-plugins@coxwave/claude-pluginsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:coxwave/claude-plugins") and the paste-ready config with skillselion.get_install_config("plugin:coxwave/claude-plugins").
What it does
coxwave-claude-plugins is a small Claude Code plugin collection built for an engineering team that wants Python changes to stay consistent under Ruff and clear written specs. Solo builders adopting the same rigor can install all three plugins to combine automated style checks, hook-driven autofix behavior, and structured clarification when requirements are fuzzy. Use it when you are shipping Python services or libraries and tired of agents proposing diffs that fail lint, skip type hints, or dodge explicit acceptance criteria. The keywords emphasize transformations through standards: enforce format, refine vague prompts into specifications, and surface actionable hints instead of generic advice. It is intentionally narrower than a full DevOps pack—no deploy plugins—so treat it as a ship-phase review layer on top of your build workflow. Intermediate familiarity with Ruff, Python project layout, and Claude Code hooks helps you tune autoruns without fighting the agent.
Highlights
- 3 plugins tailored to Coxwave engineering Python workflows
- Ruff-driven lint, import order, and format enforcement with autofix-oriented hooks
- Specification and requirements skills that question vague asks before coding
- Type-hint and pythonic style guidance with precise, actionable edit hints
- Hook-based autoruns that apply standards without manual CLI repetition
Why builders use it
Agent-generated Python often drifts from Ruff rules and vague tickets, forcing manual cleanup before merge.
After registration, hooks and skills push pythonic, lint-clean diffs and sharper specifications as the agent works.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 1 stars, 0 votes.
FAQ
Who is coxwave-claude-plugins for?
It is for Python developers using Claude Code who want Ruff enforcement, structured requirements, and autofix hooks aligned with Coxwave engineering practice.
When should I use coxwave-claude-plugins?
Use it while writing or reviewing Python when you need consistent style, type hints, and clarified specs before merge.
How do I add coxwave-claude-plugins to my agent?
Install plugins from coxwave/claude-plugins in Claude Code, enable the three bundled plugins, configure Ruff in your repo, and wire hooks for autoruns if documented.
Comments
Share how you use coxwave-claude-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.