Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By rbozydar
Python-specific development tools: 7 agents, 2 commands, 1 skill for Python code review, testing, and type checking
npx claudepluginhub rbozydar/rbw-claude-code --plugin python-backendGet alternative perspectives on plans and specifications from Google Gemini. Use when you want a second opinion from a different LLM on feature plans, architecture proposals, or project specifications.
Get code review feedback from Google Gemini. Use when you want a second opinion from a different LLM on code changes, identifying issues Claude might miss.
ALWAYS Use this agent when you need to write, review, or refactor Python code, with SOLID principles, asyncio patterns, and production-quality standards. This agent should be always invoked when writing Python code to ensure quality, or when explicitly asked to review or improve existing code. **Examples:** <example> Context: The user is asking for a new async function to fetch data from multiple APIs. user: "Write a function that fetches user data from three different API endpoints in parallel" assistant: "I'll implement that async function for you:" <function implementation provided> assistant: "Now let me use the python-coder agent to review this code for adherence to asyncio best practices and our coding standards." </example> <example> Context: The user has just written a Python class and wants it reviewed. user: "Can you review this Python class I wrote?" assistant: "I'll use the python-coder agent to provide a comprehensive code review." <commentary> Since the user is requesting a code review, use the python-coder agent to analyze the code against all Python best practices, SOLID principles, and the project's conventions. </commentary> </example> <example> Context: A new provider module was just added to the deep_research/providers/ directory. user: "I just added a new research provider, please take a look" assistant: "Let me use the python-coder agent to review your new provider implementation." <commentary> The user added new code to the providers module. Use the python-coder agent to verify it follows the ResearchProvider protocol, uses proper async patterns with fault isolation, and adheres to the project's architectural patterns. </commentary> </example> <example> Context: The user is refactoring code to fix a bug. user: "There's a race condition in the orchestrator, can you fix it?" assistant: "I'll analyze and fix the race condition:" <fix implementation provided> assistant: "Now let me use the python-coder agent to verify this fix follows proper asyncio synchronization patterns." </example>
Use this agent when you need to review Python code changes with an extremely high quality bar. This agent should be invoked after implementing features, modifying existing code, or creating new Python modules. The agent applies Kieran's strict Python conventions and taste preferences to ensure code meets exceptional standards. Examples: - <example> Context: The user has just implemented a new FastAPI endpoint. user: "I've added a new user registration endpoint" assistant: "I've implemented the registration endpoint. Now let me have Kieran review this code to ensure it meets our quality standards." <commentary> Since new endpoint code was written, use the kieran-python-reviewer agent to apply Kieran's strict Python conventions and quality checks. </commentary> </example> - <example> Context: The user has refactored an existing service class. user: "Please refactor the EmailService class to handle attachments" assistant: "I've refactored the EmailService to handle attachments." <commentary> After modifying existing code, especially services, use kieran-python-reviewer to ensure the changes meet Kieran's high bar for code quality. </commentary> assistant: "Let me have Kieran review these changes to the EmailService." </example> - <example> Context: The user has created new utility functions. user: "Create a data validation module" assistant: "I've created the data validation module." <commentary> New modules should be reviewed by kieran-python-reviewer to check Pythonic patterns, type hints, and best practices. </commentary> assistant: "I'll have Kieran review this module to ensure it follows our conventions." </example>
You are a senior ML/Data Science engineer with deep expertise in machine learning systems, data pipelines, and LLM integrations. You review code with a focus on correctness, reproducibility, and production-readiness.
This skill should be used when invoking the Gemini CLI for code review, plan review, or any prompt-based task. It provides correct invocation patterns emphasizing stdin piping and @ syntax over shell variable gymnastics.
This skill should be loaded when writing, reviewing, or refactoring Python code to apply strict coding standards directly in the current context without spawning a subagent. It provides comprehensive Python development standards covering SOLID principles, asyncio patterns, type hints, testing, and production-quality code.
Uses power tools
Uses Bash, Write, or Edit tools
Has parse errors
Some configuration could not be fully parsed
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
This skill should be used when the model needs to ensure code quality through comprehensive linting and formatting. It provides automatic linting workflows for orchestrators (format → lint → resolve via concurrent agents) and sub-agents (lint touched files before task completion). Prevents claiming "production ready" code without verification. Includes linting rules knowledge base for ruff, mypy, and bandit, plus the linting-root-cause-resolver agent for systematic issue resolution.
Python development ecosystem - uv, ruff, pytest, packaging, type checking
Python-specific development with type hints and idiomatic refactoring
Comprehensive Pytest testing framework skills for Python projects with fixtures, plugins, and advanced testing patterns.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Allow only safe read-only gh api commands
Block destructive git commands to prevent data loss
Run type checking after Python file edits
Block destructive file operations and supply chain attacks
Block Gemini 2.x models, enforce Gemini 3 models only
A Claude Code plugin marketplace with parallel Codex marketplace metadata for the plugins that already map cleanly onto Codex's current plugin model.
This project started as a fork of EveryInc/compound-engineering-plugin.
Add this marketplace to Claude Code:
/plugin marketplace add RBozydar/rbw-claude-code
Then browse and install plugins:
/plugin menu
Codex currently reads local marketplaces rather than remote GitHub marketplace
references. This repo now ships a repo-local Codex marketplace at
.agents/plugins/marketplace.json.
To use it:
git clone https://github.com/RBozydar/rbw-claude-code.git
cd rbw-claude-code
codex
/plugins
The current Codex marketplace exposes:
corepython-backenddeep-research-plusThe guard plugins remain Claude-only for now because current Codex plugin docs describe skills, apps, and MCP configuration, but not hook plugins.
If you use Poetry instead of uv for package management, install from the poetry-variant branch:
/plugin marketplace add RBozydar/rbw-claude-code#poetry-variant
This variant includes enforce-poetry instead of enforce-uv, suggesting poetry run and poetry add commands.
Due to a known Claude Code bug, plugin hooks are matched but not executed. Until this is fixed upstream, you need to manually configure hooks in your settings.
Navigate to the marketplace directory:
cd ~/.claude/plugins/RBozydar/rbw-claude-code
Run the setup script:
# Global hooks (apply to all projects) - default
./scripts/setup-hooks.sh
# Or project-specific hooks (run from within your project)
./scripts/setup-hooks.sh --project
To verify hooks are active:
/hooks
You should see the configured hooks listed (enforce-uv, conventional-commits, etc.).
Once hooks are installed, a SessionStart hook automatically checks if your
configured hooks are in sync with available plugin hooks. If hooks change
(e.g., after updating the marketplace), you'll see a warning at session start:
====================================================
rbw-claude-code: Hooks are out of sync!
====================================================
Plugin hooks have changed. Run to update:
./scripts/setup-hooks.sh --project
====================================================
You can also manually check sync status:
./scripts/setup-hooks.sh --check # Check global hooks
./scripts/setup-hooks.sh --check --project # Check project hooks
| Plugin | Description |
|---|---|
| core | Universal AI development tools: 29 agents, 18 commands, 16 skills |
| python-backend | Python-specific tools: 5 reviewers, 2 commands |
| deep-research-plus | Deep research workflows with optional GDELT MCP support |
| Plugin | Description |
|---|---|
| enforce-uv | Block bare python/pip/pytest commands, enforce uv |
| conventional-commits | Validate conventional commit format |
| python-format | Auto-format Python files with ruff after edits |
| python-typecheck | Run type checking after Python file edits |
| test-reminder | Remind to add tests when creating new Python files |
| Plugin | Description |
|---|---|
| protect-env | Block reading .env files to protect secrets |
| git-safety-guard | Block destructive git commands |
| safety-guard | Block destructive file ops and supply chain attacks |
Codex-compatible plugins in this repo currently are:
corepython-backenddeep-research-plusEach now ships a .codex-plugin/plugin.json, and the repo marketplace lives at
.agents/plugins/marketplace.json.
Hook-only plugins remain Claude-specific for now. Details: docs/codex-compatibility.md
For Codex-only local generation without hand-maintaining duplicate markdown, the repo now generates:
.codex/agents/ from Claude agents/.codex/prompts/ from Claude commands/Regenerate both from source:
uv run python scripts/generate_codex_agents.py
Install them into your Codex home:
./scripts/install-codex-agents.sh