Esparkman Claude Rubycritic Skill
esparkman-claude-rubycritic-skill is a Claude Code plugin for the Ship phase that runs RubyCritic analysis to score complexity, detect smells, and prioritize Ruby and Rails refactors.
by esparkman · github.com/esparkman/claude-rubycritic-skill
Invoke the RubyCritic Claude skill so your agent can analyze Ruby and Rails code quality, surface smells, and prioritize refactors before you ship.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install esparkman-claude-rubycritic-skill@esparkman/claude-rubycritic-skillBuilt 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:esparkman/claude-rubycritic-skill") and the paste-ready config with skillselion.get_install_config("plugin:esparkman/claude-rubycritic-skill").
What it does
The esparkman Claude RubyCritic skill is a single-plugin bundle that teaches Claude Code to run Ruby-oriented static analysis through RubyCritic. Solo builders maintaining Rails or Ruby APIs often defer quality work until production pain; this skill turns RubyCritic’s reports—complexity, smells, branch comparisons, and high-churn hotspots—into an agent-guided review session you can run before merge or release. Its canonical home is Ship → review because the output is meant to change what you allow out the door, though the same runs support Operate → iterate when technical debt keeps resurfacing. The skill is analysis and prioritization, not automatic fixes; you still apply refactors and tests. Compared to a generic “clean up my code” prompt, it is anchored to measurable RubyCritic scores and Rails-friendly workflows.
Highlights
- Model-invoked Claude Code skill wrapping RubyCritic static analysis for Ruby and Rails.
- Reports complexity scores, code smells, and detailed per-file metrics.
- Compares branches and highlights high-churn areas for refactoring opportunities.
- Prioritizes problem areas so solo builders know what to fix first.
Why builders use it
Ruby solo founders cannot see which files are truly risky until bugs ship, and manual RubyCritic runs feel too heavy to repeat every sprint.
After adding the skill, Claude can invoke RubyCritic workflows that identify smells, compare branches, and rank refactor targets so you ship cleaner Ruby code.
At a glance
- Type - Plugin in Testing.
- Adoption - 0 installs, 14 stars, 0 votes.
FAQ
Who is esparkman-claude-rubycritic-skill for?
It is for Claude Code users working in Ruby or Rails who want structured RubyCritic insights without manually parsing HTML reports each time.
When should I use esparkman-claude-rubycritic-skill?
Use it before merging sizable changes, after high-churn features, or when planning refactors—not when you are only prototyping non-Ruby stacks.
How do I add esparkman-claude-rubycritic-skill to my agent?
Install the plugin from esparkman/claude-rubycritic-skill in Claude Code, ensure Ruby and RubyCritic are available in the project, and invoke the skill when reviewing Ruby files or branches.
Comments
Share how you use esparkman-claude-rubycritic-skill, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.