A Claude Code plugin to streamline development focused on Ruby on Rails applications. The name was borrowed from the book Vibe Coding by Gene Kim and Steve Yegge where they compare the use of coding agents as having a sous chef helping us (the head chef) to achieve our vision.
I've been trying to use other frameworks like GSD and Openspec. Both are really good, but I feel they're extremely verbose and kill my usage in almost no time (I use the pro plan, so not many tokens to spare per session).
Thinking about these limitations I decided to aggregate the tools I built over time into a single plugin to help me develop apps in a predictable way while not burning all my tokens in minutes.
This is the main tech stack that I use. Yes, coding agents can help us write code in any language and stacks, but this one is a lightweight framework to help with a more specific sstack, allowing me to create focused tools and workflows.
As Rails users we are kind of accostumed with the omakase approach... so I created this plugin to be just like that: a set of conventions that I use in my projects. Sous Chef will help quickly prototyping and testing Rails applications with a predictable infracstructure.
Run these two commands inside Claude Code:
/plugin marketplace add fredericomozzato/sous-chef
/plugin install chef@sous-chef
Then bootstrap the plugin configuration:
/chef:setup
This adds the required hooks to ~/.claude/settings.json. Restart Claude Code or open /hooks once to activate.
The plugin is named Sous Chef, but I simplified the usage name to chef (less typing is always good).
Creates a GitHub issue following a structured workflow: gathers requirements, formats the title as [TYPE] Brief description (e.g. [FEAT] Add calculator page), determines the assignee interactively, writes a Markdown body with a problem description, definition-of-done checklist, and TDD execution instructions, then presents the draft for your approval before creating it.
Usage: /chef:create-issue — describe the issue when prompted, or include a description inline.
Fetches a GitHub issue and implements a full solution end-to-end: creates a properly-named branch off main, implements the feature or fix with 100% RSpec test coverage using TDD (red → green → refactor), runs pre-commit checks after each cycle, requests your review before opening a PR, then delegates to /chef:create-pull-request to finalize.
Usage: /chef:solve-issue 42 or /chef:solve-issue 42 use Turbo Streams to pass additional instructions.
Creates a pull request (or updates an existing PR description) with a full quality gate: runs bundler-audit (hard block on vulnerabilities), captures screenshots for UI changes, writes a description following the project template, waits for your explicit approval, then creates the PR via the GitHub MCP (fallback: gh CLI).
Usage: /chef:create-pull-request — invoke after your branch is ready to ship.
Bootstraps the plugin after installation. Merges the required SessionStart hook into ~/.claude/settings.json so handoff context loads automatically on every new session. Safe to run multiple times — existing config is preserved.
Usage: /chef:setup — run once after installing the plugin, then restart Claude Code or open /hooks to activate.
Saves a snapshot of the current session before stepping away. Dispatches a Haiku sub-agent to summarize git history, changed files, work done, work remaining, and key decisions into a handoff file at ~/.claude/progress/{project}/{branch}/session-NNN.md (100-line cap). Running it multiple times in the same session updates the same file; a new session creates the next numbered file. On the next session start, the file is injected automatically — no manual action needed.
Usage: /chef:handoff — invoke before ending a session on any active branch.
Runs RubyCritic against the app/ directory and compares the score against the project minimum stored in .rubycritic_minimum_score. PASS continues silently; IMPROVED auto-updates the minimum file (you commit it); FAIL soft-blocks and asks how to proceed. Produces the score table and optional Score Trade-off section for the PR description.
Usage: /chef:critic — called automatically as part of /chef:create-pull-request, or run standalone before opening a PR.