Claude Code Cookbook plugin
A Claude Code plugin: 39 commands for PRs, review, commits and specs, nine expert roles and hooks, in eight language versions
- 1,134 ★ on the repository
- Last commit
Broad access
Why this level
- The `/pr-create`, `/pr-fix` and `/semantic-commit` commands call `git` and `gh`: they create commits and pull requests and edit descriptions and labels
- The `/update-node-deps`, `/update-flutter-deps` and `/update-rust-deps` commands change a project's dependency files
- `/screenshot` captures macOS screenshots and `/search-gemini` sends queries through the Gemini CLI
Install
- Works in
Manual install
/plugin marketplace add wasabeef/claude-code-cookbookFirst step: add the repository as a plugin marketplace.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The `/pr-create`, `/pr-fix` and `/semantic-commit` commands call `git` and `gh`: they create commits and pull requests and edit descriptions and labels
- The `/update-node-deps`, `/update-flutter-deps` and `/update-rust-deps` commands change a project's dependency files
- `/screenshot` captures macOS screenshots and `/search-gemini` sends queries through the Gemini CLI
This is third-party code. Review the repository files before installing.
What it does
Claude Code Cookbook is a Claude Code plugin with 39 commands, nine expert roles and hooks. The commands cover a developer's working loop. `/pr-list` and `/pr-issue` list open pull requests and issues by priority, `/pr-create` analyzes changes through `git diff`, takes the template from `.github/PULL_REQUEST_TEMPLATE.md`, picks up to three labels and creates a draft, `/pr-fix` works through review comments, `/pr-checks` follows GitHub Actions and `/semantic-commit` splits large changes into semantic commits. For code quality there are `/refactor`, `/smart-review`, `/tech-debt`, `/analyze-dependencies`, `/analyze-performance` and `/design-patterns`. For planning there are `/plan`, `/spec`, `/ultrathink` and `/check-fact`, which checks claims against the code and documentation. Three commands update dependencies in Node.js, Flutter and Rust projects. Each command comes with examples and steps, and its header lists the tools it may use: `/semantic-commit`, for example, calls only `git`, reading and search. The roles (`analyzer`, `architect`, `backend`, `frontend`, `mobile`, `performance`, `qa`, `reviewer`, `security`) switch Claude to an expert profile. With the `--agent` flag a role works as a subagent in its own context, and `/multi-role security,performance --agent` runs several roles in parallel.
Who it is for. For Claude Code developers who want a ready set of commands for PRs, review, commits and specs without writing their own prompts.
Good fit when
- You need a draft pull request built from your changes with a description from the repository template and labels
- A large diff should be split into several semantic commits and you want to see the plan first with `--dry-run`
- You need a security or performance audit that a role subagent can run without cluttering the main context
- A specification built from requirements with `/spec` is needed before implementation
- It is time to update Node.js, Flutter or Rust dependencies step by step rather than with one blind command
Not a fit when
- You need commands in Russian: the set has no Russian version
- The repository is not on GitHub: the `/pr-*` commands work through `gh`
- You use another agent: the plugin is built for Claude Code only
- You need one narrow command: a set of 39 is better replaced by a small skill for that task
Example request
Split my changes into semantic commits, show the plan without committing first, then create a draft pull requestLimitations
- There is no Russian version. The plugin ships in Japanese, English, Korean, two Chinese variants, Spanish, French and Portuguese, and the English one is called `cook-en`. Commands are called with the plugin name as a prefix.
- Some commands need something external: `/search-gemini` calls the Gemini CLI, `/screenshot` is built for macOS and `screencapture`, and `/sequential-thinking` uses the Sequential Thinking MCP.
- The `.mcp.json` file at the repository root is a sample of eight servers. The GitHub token in it is a placeholder, and the file sits outside the `plugins/en` folder.
- The Apache-2.0 license is declared in the documentation and the plugin manifest, but the repository has no LICENSE file and GitHub does not detect a license.
- The `preserve-file-permissions.sh` hook saves and restores file permissions, requires `jq` and writes a debug log to `/tmp`. You wire it into `settings.json` by hand.
How to disable. Remove the plugin through the Claude Code plugin manager; `/plugin` lists what is installed. If you wired in the `preserve-file-permissions.sh` hook, delete its entries from `settings.json`.
FAQ
How do I create a pull request automatically from my changes in Claude Code?
`/pr-create` reads `git diff --cached`, takes the template from `.github/PULL_REQUEST_TEMPLATE.md`, picks up to three fitting labels and creates a draft, keeping the template's HTML comments. Once CI passes, `gh pr ready` moves it to ready for review.
How do I split large changes into semantic commits?
`/semantic-commit` divides changes into small commits and calls only standard `git`. The `--dry-run` flag shows the proposed split without committing, and `--lang` sets the message language.
How do I run an expert role as a separate subagent in Claude Code?
Call `/role security --agent`: the role gets its own context and does not clutter the main one. `/multi-role security,performance --agent` starts several roles at once. The `security` role header names the opus model and read, search and WebSearch tools.
How do I update a Node.js project's dependencies through Claude Code?
`/update-node-deps` may call `npm`, `npx`, `yarn` and `pnpm`, and read and edit files. You first look at `npm outdated`, then ask Claude to update the dependencies in `package.json`. Flutter and Rust have separate `/update-flutter-deps` and `/update-rust-deps` commands.
Is there a Russian version of the Claude Code Cookbook plugin?
No. The repository ships eight language plugins and Russian is not among them. Install the English one with `/plugin install cook-en@claude-code-cookbook` after adding the marketplace.
Discussion
No questions or reviews yet.
Related
PluginsA set of slash commands, skills and subagents for Claude Code: review, tests, security, releases, docs and GitHub to Linear sync
A set of 24 slash commands for the Claude Code CLI: commits, review, refactoring, tests and cleanup without repeating the same prompts
A Claude Code plugin marketplace by Frad LEE: Git and GitFlow, GitHub, refactoring, memory, research, image generation and interface work
Claude Code Skills and Agents
Claude Code Skills & Agents
A Claude Code plugin bundling skills and sub-agents: deep research, image generation, GitHub work, code review and model switching
Claude Code plugins with development recipes: agree on the outcome, design, implement with checks and run an independent review
A set of Claude Code utilities: background skills, expert agents, slash commands and prompt templates for development
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Repository stars | Main difference |
|---|---|---|---|
| Claude Code Cookbook (this entry) | no | 1,134 | |
| Claude Command Suite | no | 1,350 | commands are grouped into 25 namespaces with subagents and skills, including GitHub to Linear sync |
| CCPlugins | no | 2,773 | 24 commands for everyday development, the author warns that part of the first version is outdated |
| wshobson/commands | no | 2,641 | commands are split into tools for one task and workflows for multistep scenarios with several agents |
README in short
The documentation opens with the three parts: commands, roles and hooks. Then come command tables by group (pull requests, code quality, development tools, planning, dependencies), a role table with run examples, a diagram of the working loop and two install steps: add the marketplace, then pick the plugin for your language. The repository holds a plugin version per language with full command descriptions, a template for a new command, settings examples and scripts that check translations.