Code Review
pluginStructured multi-agent review.
plugins/code-review/
Open component record →What anthropics/claude-code is—in plain language
Anthropic's agentic coding CLI plus official plugins containing reusable commands, subagents, hooks, skills, and MCP integrations.
Mental model: This repository provides a directly runnable command or package. You give the command an input, it performs the documented workflow, and it returns files, terminal output, a local interface, or a remote result.
InterfacesCLI, IDE integration, plugin, MCP
Primary languageNone documented
Typical useUse as the primary Claude coding environment; add plugins for feature development, code/PR review, security guidance, plugin authoring, and automation.
Your first 15 minutes
- Complete the linked Installation Guide and its verification step.
- Create a disposable test folder or use non-sensitive sample data.
- Run the small example below and observe what files, ports, or prompts appear.
- Read the result before approving writes, network calls, account access, or costs.
- Only then repeat the workflow with a real project.
Starter workflow
mkdir -p "$HOME/Developer/claude-sandbox"
cd "$HOME/Developer/claude-sandbox"
claudeComplete indexed functionality map
Each card below corresponds to a component identified in the repository research. Open a component record for its path, purpose, capabilities, dependencies, risks, and relationships.
Feature Dev
pluginExplore, architect, implement, and review features.
plugins/feature-dev/
Open component record →PR Review Toolkit
pluginSpecialist PR review agents.
plugins/pr-review-toolkit/
Open component record →Security Guidance
pluginPreToolUse security guidance hook.
plugins/security-guidance/
Open component record →Plugin Dev
pluginCreate/validate plugins, agents, skills, hooks, commands, MCP.
plugins/plugin-dev/
Open component record →Ralph Wiggum
pluginRepeated-agent loop with cancel/stop controls.
plugins/ralph-wiggum/
Open component record →Upstream feature-by-feature guide
These capabilities are derived from the current first-party README and supporting documentation. Names follow upstream terminology so you can search the source documentation precisely.
Upstream capability
Plugins
Upstream treats this as a distinct part of anthropics/claude-code. In plain language, use this area when your task concerns plugins. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Reporting Bugs
Upstream treats this as a distinct part of anthropics/claude-code. In plain language, use this area when your task concerns reporting bugs. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Connect on Discord
Upstream treats this as a distinct part of anthropics/claude-code. In plain language, use this area when your task concerns connect on discord. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Data collection, usage, and retention
Upstream treats this as a distinct part of anthropics/claude-code. In plain language, use this area when your task concerns data collection, usage, and retention. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Privacy safeguards
Upstream treats this as a distinct part of anthropics/claude-code. In plain language, use this area when your task concerns privacy safeguards. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
How to use the main workflows
Choose the smallest relevant function
Start with one capability card instead of asking the repository to do everything at once. This makes permissions, inputs, and output easier to understand.
Prepare a disposable input
Use a sample URL, copied repository, test document, or sandbox account. Keep production credentials and irreplaceable files out of the first run.
Run, observe, and stop
Watch Terminal output or the host application's activity view. If the behavior differs from the README, stop with Control + C or cancel inside the host before retrying.
Inspect the result
Check generated files, diffs, API responses, logs, or previews. Never assume “command finished” means the result is correct.
Save a repeatable recipe
Record the working command and non-secret configuration in your project's README. Store secrets in the documented environment file or password manager.
Copy-paste recipes from upstream documentation
These examples are selected from the repository's first-party documentation. Replace obvious placeholders, keep quotation marks intact, and run them only in the context indicated by the surrounding explanation.
Get started
curl -fsSL https://claude.ai/install.sh | bashConfiguration, accounts, and files
Configuration files
None documented
A configuration file changes behavior without changing source code. Make one change at a time and keep a backup before editing JSON, TOML, YAML, or environment files.
Important directories
plugins/
Paths identify where the relevant implementation or generated files live. Paths beginning with ~ are inside your home folder.
Credentials
Claude/Anthropic authentication
Prefer temporary, least-privileged credentials. Never commit .env, tokens, cookies, private keys, or session exports.
External services
None documented
Check pricing, data retention, rate limits, and account permissions before enabling optional integrations.
Safe operating habits
- Use test data first and keep a current backup or Git commit.
- Read commands before pasting. A README is useful evidence, not a substitute for judgment.
- Review agent-generated file changes with
git diffbefore committing. - Keep local services bound to
127.0.0.1unless you intentionally secure and expose them. - Do not give plugins or MCP servers broader filesystem, browser, GitHub, or cloud access than their current task requires.
- Confirm API costs and model names before running large batches.
- Stop and investigate repeated authentication failures instead of pasting a token into multiple places.
Reference and source trail
The manual reflects first-party files checked on August 18, 2026. It explains the indexed repository rather than promising that every optional third-party integration is available or safe.