Ext Ops Panel
Open dashboard
Comparison

clean-code-assistant vs kamae-ts

clean-code-assistant is a plugin bundle for AI coding tools published by DinoQuinten. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). kamae-ts is a plugin bundle for AI coding tools published by Kosui Iwasa. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-24. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceclean-code-assistantkamae-ts
Claude Code: claude-plugins-community Listed
Version: 0.5.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Community marketplace iwasa-kosui/kamae-ts Not listed Listed
Version: 1.4.0
Forks (GitHub): 2
Stars (GitHub): 55
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

clean-code-assistant vs kamae-ts
Factclean-code-assistantkamae-ts
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)55 (better)
Forks (GitHub) (differs)0 (worse)2 (better)
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)172
LicenceMITMIT
Repository (differs)github.com/dinoquinten/cleancode-assistantgithub.com/iwasa-kosui/kamae-ts
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-22

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

clean-code-assistant

In its own words, on Claude Code: claude-plugins-community:

Enforces clean code principles across your project and fixes the code for you - not just flags what's wrong. Ships with 14 plain-language rules (formal textbook names in parentheses for experts), 13 skills, a background reviewer agent that appends non-blocking suggestions after every edit, and a plan-mode hook that reminds Claude to factor clean code into every plan. Every detection skill supports both report-only mode and a fix mode that applies the changes directly. Multi-platform: generates matching configs for Cursor (.cursorrules) and Codex CLI (AGENTS.md) from one source of truth. Based on Code Complete 2nd Ed., The Art of Clean Code, and OOP vs. Functional Programming.

kamae-ts

In its own words, on Community GitHub marketplaces:

Server-side TypeScript design and review skills with rules-based user customization

How to run each

clean-code-assistant As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install clean-code-assistant@claude-community

kamae-ts As a Claude Code plugin

Claude Code
/plugin marketplace add iwasa-kosui/kamae-ts
/plugin install kamae-ts@kamae-ts

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: clean-code-assistant · What it can do: kamae-ts · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built