From moltbloat
Diff your ecosystem against a previous snapshot — see what changed, what was added, what was removed
How this skill is triggered — by the user, by Claude, or both
Slash command
/moltbloat:changelogThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<Purpose>
<Use_When>
<Do_Not_Use_When>
/moltbloat:audit/moltbloat:why/moltbloat:snapshot first
</Do_Not_Use_When>Load the baseline snapshot
cat ~/.moltbloat/baseline.json 2>/dev/null
If no baseline exists, tell the user:
No baseline snapshot found. Run
/moltbloat:snapshotto save the current state, then run/moltbloat:changelogafter your next change to see a diff.
Stop here if no baseline.
Collect current state
Run these scans in parallel:
Plugins:
cat ~/.claude/plugins/installed_plugins.json 2>/dev/null
Claude Code version:
claude --version 2>/dev/null || echo "unknown"
MCP servers: Scan settings.json + plugin .mcp.json files.
Skills: Count per plugin from cache directories.
Agents: List from ~/.claude/agents/ and plugin cache.
Rules: List from ~/.claude/rules/.
Diff current vs baseline
Compare each category:
Plugins:
MCP servers:
Skills:
Agents:
Rules:
Claude Code version:
Generate report
# Moltbloat Changelog
**Baseline taken**: <timestamp from baseline.json>
**Current scan**: <now>
**Claude Code**: <old version> → <new version> (or "unchanged")
## Plugins
| Change | Plugin | Details |
|--------|--------|---------|
| + Added | <name> | v<version>, installed <date> |
| - Removed | <name> | was v<version> |
| ↑ Upgraded | <name> | v<old> → v<new> |
| ↓ Downgraded | <name> | v<old> → v<new> |
(If no changes: "No plugin changes since baseline.")
## MCP Servers
- Added: <list>
- Removed: <list>
(If no changes: "No MCP changes since baseline.")
## Skills
- Total: <old count> → <new count> (<+/- delta>)
- <list notable additions/removals if any>
## Agents
- Added: <list>
- Removed: <list>
## Rules
- Added: <list>
- Removed: <list>
## Summary
- <N> total changes since baseline (<date>)
- Run `/moltbloat:snapshot` to update the baseline to current state
- Run `/moltbloat:audit` for a full health check
Done
Read-only. Suggest /moltbloat:snapshot to update the baseline if the user is happy with the current state.
npx claudepluginhub jcgruesome/moltbloat --plugin moltbloatGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.