Eduardoarantes Claude Code Plugin Marketplace
Eduardo Arantes Claude Code Plugin Marketplace is a Claude Code plugin bundle for the Ship phase that focuses on Bowser QA agents, parallel validation, and git-backed issue workflows across seven plugins.
by eduardoarantes · github.com/eduardoarantes/claude-code-plugin-marketplace
Install seven plugins centered on Bowser QA agents, parallel pass/fail validation, screenshots, git worktrees, and issue workflows for production-ready TypeScript and Python shipping.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install eduardoarantes-claude-code-plugin-marketplace@eduardoarantes/claude-code-plugin-marketplaceBuilt 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:eduardoarantes/claude-code-plugin-marketplace") and the paste-ready config with skillselion.get_install_config("plugin:eduardoarantes/claude-code-plugin-marketplace").
What it does
Eduardo Arantes’s Claude Code marketplace bundles seven plugins aimed at builders who treat QA as a first-class ship gate rather than a manual browser session at the end. The ingest highlights Bowser QA agents, parallel execution, pass/fail summaries, screenshots, and markdown reports—patterns suited to indie SaaS and mobile-adjacent web apps where you need evidence before merge. Complementary plugins cover git worktrees, issue discovery, notifications, voice or input modalities where enabled, and team-style story workflows scaled down for one person wearing QA hat. Architecture and product keywords suggest the bundle also nudges structural decisions while validating stories. Register the marketplace when you are hardening releases: spin an isolated worktree, run agent-driven checks, collect artifacts, and feed failures back into issues without leaving Claude Code. Description text in catalog is minimal (“7 plugins”), so verify each plugin’s commands after install; tagging confidence reflects strong QA signals but limited per-plugin README in the snippet.
Highlights
- Bowser QA agent plugins with parallel validation runs and pass/fail aggregated reporting
- Screenshot capture and markdown-ready results for reproducing UI or flow defects
- Git worktree and issue-management commands to isolate fixes without trashing main
- Shared agent state and notification hooks so long QA series do not lose context
- TypeScript and Python oriented production workflows with architecture and story-level support
Why builders use it
You ship stories without repeatable agent-driven QA, so regressions surface late and you lack screenshots or pass/fail trails for solo retrospective.
After adding the marketplace, you can run parallel Bowser-style validations, capture screenshot evidence, and route failures into issues from isolated git worktrees.
At a glance
- Type - Plugin in Testing.
- Adoption - 0 installs, 2 stars, 0 votes.
FAQ
Who is eduardoarantes-claude-code-plugin-marketplace for?
It is for independent developers shipping web or agent-backed products who need Bowser-style QA automation, screenshots, and issue-linked validation in Claude Code.
When should I use eduardoarantes-claude-code-plugin-marketplace?
Use it before you mark a story production-ready, when you want parallel checks, visual artifacts, and git-isolated fix branches.
How do I add eduardoarantes-claude-code-plugin-marketplace to my agent?
Register eduardoarantes/claude-code-plugin-marketplace in Claude Code, install the bundle, enable Bowser QA and supporting plugins, then connect your git remote and issue tracker per each plugin README.
Comments
Share how you use eduardoarantes-claude-code-plugin-marketplace, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.