By rp1-run
Generate and maintain project documentation including architecture diagrams, knowledge bases, and onboarding overviews using Mermaid diagrams and map-reduce analysis. Also performs security validation and strategic analysis with quantified trade-offs.
Maps system architecture patterns, layers, and integrations for architecture.md from pre-filtered files
Extracts domain concepts and terminology for concept_map.md from pre-filtered files
[DEPRECATED] Generates project overview data for index.md from pre-filtered files
Analyzes modules, components, and dependencies for modules.md from pre-filtered files
Extracts implementation patterns and idioms for patterns.md from pre-filtered source files
Performs thorough security validation of features including vulnerability scans, authentication/authorization verification, compliance assessment, and penetration testing.
Extract comment locations from code files for analysis. Use when cleaning comments, auditing code documentation, or analyzing comment patterns. Supports Python, JavaScript, TypeScript, Go, Rust, Java, C/C++, Ruby, PHP, Shell scripts. Trigger terms - comments, extract comments, code comments, comment analysis, documentation audit, comment cleanup.
Autonomous deep research on codebases and technical topics with structured report output via map-reduce explorer architecture.
Validates and repairs mermaid diagrams in markdown files. Scans for mermaid blocks, validates syntax, and auto-repairs common errors.
Synchronizes user documentation with knowledge base using two-phase map-reduce orchestration with scan and process phases.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
> stop prompting; start shipping
Professional development workflows for AI coding assistants.
21 commands. 18 specialized agents. Single-pass execution.
Works today with Claude Code. Experimental support for OpenCode and Codex CLI.
Single-pass execution — Constitutional prompts encode expert patterns with built-in rules. No iteration loops, no "let me revise that" — tasks complete in one shot.
Codebase awareness — Run knowledge-build once. Your architecture becomes context for every command. No generic advice — everything respects your patterns.
Lean context architecture — Progressive disclosure and subagent delegation keep your main thread focused. Complex work happens in specialized agents, results flow back clean.
Validate before you build — Hypothesis testing catches bad assumptions early. Design decisions get validated against your codebase before implementation begins.
Start anywhere — Full blueprints with charters and PRDs, or jump straight in with a vague idea. Structured when you need it, flexible when you don't.
# macOS / Linux (Homebrew)
brew install rp1-run/tap/rp1
# Windows (Scoop)
scoop bucket add rp1 https://github.com/rp1-run/scoop-bucket
scoop install rp1
# Or use the install script
curl -fsSL https://rp1.run/install.sh | sh
cd your-project
rp1 init
This will set up rp1 and install plugins for your AI assistant (Claude Code, OpenCode, or Codex CLI).
/knowledge-build # Generate your codebase knowledge base
/build user-auth
/pr-review "feature/auth"
/code-investigate "bug-123" "Login fails intermittently"
/code-check
| Batteries Included | Skills, subagents, and finely-tuned prompts ship out of the box. No assembly required. |
| Always Open Source | Fully pluggable into existing agentic tools. Your workflows, your control. |
| Visual-First | Heavily leans on visual language — diagrams, charts, and structured outputs for clarity. |
| Continuous Evolution | Keep improving and adapting as frontier models mature. Today's best, tomorrow's baseline. |
| Model/Tool Agnostic | No lock-in to any frontier lab or platform. Works with Claude Code, OpenCode, Codex CLI, and more coming. |
| Platform | Status |
|---|---|
| Claude Code | Available |
| OpenCode | Experimental |
| Codex CLI | Experimental |
| Cursor, Goose, Amp | Coming Soon |
See the documentation for architecture and contribution guides. Issues and PRs welcome!
Apache 2.0 — See LICENSE
Development workflow automation including feature development, code quality, and PR management
npx claudepluginhub rp1-run/rp1Create comprehensive documentation for code, APIs, and projects.
Project discovery, planning, and quality analysis system with parallel agents
Code documentation with automated doc generation, code explanation, and tutorial engineering
Development workflow automation including feature development, code quality, and PR management
Complete development toolkit - documentation, PRDs, design docs, debugging, PR workflows, and planning
Use this agent when you need to analyze a service or codebase component and create comprehensive documentation in CLAUDE.md files. This agent should be invoked after implementing new services, major refactoring, or when documentation needs updating to reflect the current codebase structure. Examples: <example>Context: The user has just implemented a new authentication service and wants to document it properly. user: 'I just finished implementing the auth service, can you document how it works?' assistant: 'I'll use the codebase-documenter agent to analyze the authentication service and create detailed documentation in CLAUDE.md' <commentary>Since the user has completed a service implementation and needs documentation, use the Task tool to launch the codebase-documenter agent to create comprehensive CLAUDE.md documentation.</commentary></example> <example>Context: The user wants to ensure a newly added API module is properly documented for the team. user: 'We need documentation for the new payment processing API I just added' assistant: 'Let me use the codebase-documenter agent to analyze the payment processing API and create proper documentation' <commentary>The user needs documentation for a new API module, so use the codebase-documenter agent to create CLAUDE.md files with setup instructions and architectural notes.</commentary></example>