New advertisers: 50% off your first month with code FIRSTMONTHSee slots

Curated Claude Code agents and skills for commits, code review, security audits, and session handoffs.

version
0.21.0
GitHub stars
114
View on GitHub

What it does

  • Adds 4 agents (git-committer, code-simplifier, security-auditor, thermo-nuclear-code-quality-review) and 6 skills, including squad-review and socratic-tutor
  • Covers commit authoring, behavior-preserving refactors, explainer generation, prototyping, and session handoffs for unfinished work
  • Runs squad-review as a six-lens review where a verifier tries to refute every finding before it reaches you
  • Designed for developers who want a fast single-pass review, a slower verified review, or a harsh maintainability audit as separate options

Essential agents and skills for Claude Code workflows - git commits, code simplification, security audits, verified multi-lens code review, thermo-nuclear code-quality review, Socratic tutoring, prototyping, diff explainers, and session handoffs.

Add marketplace

/plugin marketplace add nicknisi/claude-plugins

Run it inside Claude Code once, then install the plugin below.

Install

/plugin install essentials@nicknisi

Run it inside Claude Code after adding the marketplace.

Files

Discovered from source

Explain Diff

Create a rich, interactive HTML explanation of a code change. The reader may be a teammate encountering the codebase for the first time or the author checking their own understanding — the document should serve both.

Resolve the change

Pin down exactly what to explain before writing anything:

  • PR number or URL — gh pr diff <number> for the diff, gh pr view <number> for the title, description, and discussion
  • Branch — git diff <base>...<branch> against the repo's default branch
  • Commit — git show <sha>
  • Nothing specified — the working tree (git diff HEAD); if clean, the current branch against the default branch

Then explore beyond the diff: read the touched files in full, their callers, and the subsystem they belong to. The Background section lives or dies on your understanding of the surrounding system, not just the delta.

Sections

The explanation has four sections, in this order:

  1. Background — Explain the existing system this change slots into. The reader's familiarity is unknown, so layer it: a deep background for beginners (marked as skippable for readers who already know the system), then a narrower background directly relevant to the change.

  2. Intuition — Explain the core idea of the change: what problem existed, what insight the change embodies, why this approach. Focus on the essence, not the full details. Use concrete examples with toy data, and use figures and diagrams liberally.

  3. Code — A high-level walkthrough of the changes. Group and order them for understanding — by concept or data flow — not by file order in the diff.

  4. Quiz — Five interactive multiple-choice questions testing whether the reader understood the substance. Medium difficulty: answerable only by someone who actually understood the change, but no gotchas. On click, reveal whether the answer was correct with a short explanation either way — the feedback is where the learning happens.

Output format

Produce a single self-contained HTML file:

  • All CSS and JavaScript inline, no external requests (CDNs, fonts, images) — the file is opened locally and must work offline.
  • One long page with section headers and a table of contents. Don't use tabs for the top-level structure.
  • Basic responsive styling so it reads well on a phone.
  • Save it outside the repo so it stays out of version control, with the filename starting with today's date so the files stay time-sorted: /tmp/YYYY-MM-DD-explanation-<slug>.html.
  • When done, open it in the browser (open <path> on macOS) and tell the user the path.

Writing style

Write with the clarity and flow of Martin Kleppmann — engaging, classic style, with smooth transitions between sections. Use callouts for key concepts, definitions, and important edge cases.

Diagrams

  • Pick a small number of diagram families and reuse them throughout to explain different cases — a repeated visual form makes each new instance easier to parse. Useful families:
    • A simplified version of the UI the user sees in the app, for explaining UI changes.
    • A system diagram showing data flow or communication between components — always populated with example data.
  • Build diagrams from simple HTML and CSS, and lists from HTML lists. Never use ASCII art — it breaks under responsive layouts and proportional fonts.
  • Use <pre> tags for code blocks. If a custom-styled div is used instead, its CSS must include white-space: pre or pre-wrap, or the browser will collapse every newline into a single line. Before saving the file, scan each code block in the HTML source and confirm its whitespace handling.

Readme

Essentials

Agents and skills that earn their place in day-to-day Claude Code work.

Installation

/plugin marketplace add nicknisi/claude-plugins
/plugin install essentials@nicknisi

Agents

Dispatched via the Task tool, each in its own context window.

AgentWhat it does
git-committerSemantic commits with pre-commit validation. Triggers proactively when you commit.
code-simplifierRefactors for readability without changing behavior. Preserves public APIs.
security-auditorInvariant-binding analysis across trust boundaries. Critical/high findings only, with exploit flows. Explicit requests only.
thermo-nuclear-code-quality-reviewLoads the thermo-nuclear rubric and applies it to a diff in an isolated context.

Skills

SkillUse it when
explain-diffYou want a rich, shareable HTML explainer for a diff, PR, or branch — with diagrams and a quiz.
handoffWrapping a session with unfinished work. Writes a portable doc the next session can pick up.
prototypeA design question needs answering in code before you commit to the real implementation.
socratic-tutorYou 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-reviewA thorough review before merging. Six lenses, then every finding attacked by a verifier — only what survives reaches you.
thermo-nuclear-code-quality-reviewYou 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.

Details

Marketplace
nicknisi/claude-plugins
Source
plugins/essentials
Author
Nick Nisi
Category
Community
Keywords
git, commit, semantic-commit, security, audit, vulnerability, code-review, squad-review, verified-review, socratic-tutor, teach, learning, simplify, refactor, maintainability, code-quality, thermo-nuclear, code-judo, handoff, context, session, prototype, spike, poc, explain-diff, explain, diff, walkthrough

More from nicknisi/claude-plugins

All 11

Similar to essentials

More Git & Version Control