essentials — Claude Code plugin: what it does, how to install
essentials is a Claude Code plugin with specialized agents and skills for everyday development, from semantic commits to verified code reviews and session handoffs.
MIT ★ 114 updated 2026-08-11
/plugin marketplace add nicknisi/claude-plugins
/plugin install essentials@nicknisiWhat essentials does
The plugin equips Claude Code with dedicated agents and skills running in separate contexts via the Task tool. Tools like git-committer, code-simplifier, security-auditor, and thermo-nuclear-code-quality-review handle focused chores without cluttering your primary prompt history.
Review tasks are split by depth. Fast reviews stay with the default tool, while squad-review runs a multi-angle inspection where a verifier challenges every finding before surfacing it. Meanwhile, thermo-nuclear-code-quality-review evaluates diffs against an uncompromising maintainability rubric.
The security-auditor agent never triggers automatically. It runs solely on explicit demand, reporting high and critical severity items alongside concrete exploit paths.
What it helps with
- run verified multi-perspective code reviews before merging
- refactor complex code while preserving public interfaces
- generate semantic commits with pre-commit checks
- save unfinished session state for future continuation
Example prompts for the agent
- Run squad-review on the current branch before opening a PR
- Create a commit with git-committer after running validations
- Run handoff to export current context and pending tasks
How to install essentials
Plugin marketplace
/plugin marketplace add nicknisi/claude-plugins/plugin install essentials@nicknisiStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about essentials
How to install essentials in Claude Code?
First add the marketplace with /plugin marketplace add nicknisi/claude-plugins, then install the package by running /plugin install essentials@nicknisi.
What is the essentials plugin?
It provides specialized skills and agents for semantic git commits, code refactoring, vulnerability audits, and session transitions.
When should squad-review be used instead of regular review?
Use squad-review when preparing critical merges that require adversarial verification across multiple angles rather than a quick single pass.
Source text
essentials · MIT
# Essentials
Agents and skills that earn their place in day-to-day Claude Code work.
## Installation
```bash
/plugin marketplace add nicknisi/claude-plugins
/plugin install essentials@nicknisi
```
## Agents
Dispatched via the Task tool, each in its own context window.
| Agent | What it does |
| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
| `git-committer` | Semantic commits with pre-commit validation. Triggers proactively when you commit. |
| `code-simplifier` | Refactors for readability without changing behavior. Preserves public APIs. |
| `security-auditor` | Invariant-binding analysis across trust boundaries. Critical/high findings only, with exploit flows. Explicit requests only. |
| `thermo-nuclear-code-quality-review` | Loads the thermo-nuclear rubric and applies it to a diff in an isolated context. |
## Skills
| Skill | Use it when |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `explain-diff` | You want a rich, shareable HTML explainer for a diff, PR, or branch — with diagrams and a quiz. |
| `handoff` | Wrapping a session with unfinished work. Writes a portable doc the next session can pick up. |
| `prototype` | A design question needs answering in code before you commit to the real implementation. |
| `socratic-tutor` | You want to actually own a change, not skim it. Drills you with quizzes until you can explain the problem, the solution, and the edge cases. |
| `squad-review` | A thorough review before merging. Six lenses, then every finding attacked by a verifier — only what survives reaches you. |
| `thermo-nuclear-code-quality-review` | You explicitly want the harsh maintainability audit — abstraction quality, the 1k-line rule, code judo. Not for ordinary review; that's the built-in `code-review`. |
Three of these deliberately overlap and stay separate: the built-in `code-review` is the fast
single pass, `squad-review` is the slow verified one (12 agents), and `thermo-nuclear` is one harsh
maintainability lens. `explain-diff` writes an explainer to read or share; `socratic-tutor` quizzes
you live.
The `thermo-nuclear-code-quality-review` SKILL.md is the canonical rubric and the agent of the same
name loads it, so the rules live in exactly one place. Edit the rubric, not the agent.
`squad-review` reuses the `security-auditor` agent as its security lens for the same reason —
one security rubric, not two.
## Layout
```
essentials/
├── agents/*.md # frontmatter: name, description, tools, model
└── skills/<name>/
├── SKILL.md # frontmatter: name, description
├── scripts/ # executables the skill shells out to
└── references/ # loaded on demand, not upfront
```
Each component's own file is the source of truth for how it behaves — this README is only an
index. Skills that ship scripts treat the script's `--help` as the flag reference rather than
restating it in prose.
© Nick Nisi · MIT · nicknisi/claude-plugins