Ryanbreen Breenix
Breenix is a Claude Code plugin bundle for the Ship phase that bundles systematic debugging, quality checks, and GitHub-integrated workflows for safer releases.
by ryanbreen · github.com/ryanbreen/breenix
Run systematic debugging, quality checks, GitHub Actions workflows, and test-oriented tooling from one Claude Code plugin bundle while you ship.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install ryanbreen-breenix@ryanbreen/breenixBuilt 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:ryanbreen/breenix") and the paste-ready config with skillselion.get_install_config("plugin:ryanbreen/breenix").
What it does
Ryanbreen Breenix is a Claude Code plugin collection described as a growing toolkit for builders who care about execution quality. The catalog lists three plugins with keywords spanning systematic debugging, test and quality workflows, GitHub Actions integration, migration and legacy cleanup, memory and kernel-flavored analysis, and optimization loops. Solo maintainers shipping CLI tools, APIs, or long-lived codebases can register the bundle when failures are intermittent, CI is flaky, or refactors need guarded steps. It is not a single happy-path generator; it biases toward diagnosis, checks, and structured workflows once you are close to release or hardening an existing repo. Expect intermediate familiarity with your test stack and GitHub automation. The bundle fits the Ship journey shelf under testing and review-adjacent work, while still supporting build-time debugging when you iterate locally before pushing.
Highlights
- Three-plugin breenix bundle combining development, debugging, and workflow-oriented capabilities
- Systematic debugging and failure analysis patterns instead of one-off printf guessing
- GitHub Actions and integration hooks for checks during delivery
- Coverage of optimization, migration, and legacy code paths common in maintainer work
- Kernel, memory, and loop-oriented analysis keywords for deeper performance and correctness hunts
Why builders use it
You keep shipping with brittle tests, opaque failures, and ad-hoc debugging that never becomes a repeatable workflow inside your agent sessions.
After install, you get three coordinated breenix plugins to structure debugging, quality analysis, and GitHub-oriented checks instead of reinventing the ritual every incident.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 7 stars, 0 votes.
FAQ
Who is ryanbreen-breenix for?
It is for indie builders and maintainers who debug production-adjacent issues, improve test quality, and wire GitHub Actions-style checks through Claude Code.
When should I use ryanbreen-breenix?
Use it when tests fail mysteriously, migrations risk regressions, or you want structured debugging and workflow authoring before you tag a release.
How do I add ryanbreen-breenix to my agent?
Add the ryanbreen/breenix plugin bundle from Skillselion or your Claude Code plugin registry, enable all three listed plugins, then call them during debug and ship prep sessions.
Comments
Share how you use ryanbreen-breenix, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.