mroberts f5934181ec Move the code and terraform audits into the reviews plugin
Copy the standalone code-review and terraform-review skills into
plugins/reviews as audit-code and audit-terraform. The rename separates the
automated, linter-driven audits from the guided review-pr walkthrough that
already lived here.

Resolve bundled script paths through ${SKILL_DIR}, exported in a new step 0.
CLAUDE_PLUGIN_ROOT is not set in the Bash tool environment, so the obvious
substitution would have expanded to nothing and broken every collection
script invocation.

Replace the PLAN and DESIGN docs with READMEs written from the current
SKILL.md and scripts. The old docs had drifted badly: they named semgrep
where the code calls opengrep, scoped five review agents where there are
now eight, and predated Lua, PowerShell, and GitHub Actions support.

Add CONSISTENCY_NORMS to the audit-terraform agent inputs. The collection
script writes consistency_norms.json and the agent prompt declares it, but
SKILL.md never listed it, leaving the variable unsubstituted.

Drop the --ingest-verdicts instruction from both skills. review_stats.py
parses no arguments, so the ref-mode verdict template it told users to feed
back could never be read.

Point audit-terraform's smoke test at README.md and resolve its fixture
paths relative to the test file rather than an absolute home directory.

Tests: 197 passing (audit-code), 106 passing (audit-terraform).
2026-07-21 11:11:05 -05:00

mroberts — Claude Code plugin marketplace

Personal marketplace hosting multiple Claude Code plugins.

Install

claude plugin marketplace add ssh://[email protected]/mroberts/claude-plugin.git
claude plugin install guards@mroberts

Layout

.claude-plugin/marketplace.json   # index — every plugin must be listed here
plugins/
  guards/
    .claude-plugin/plugin.json
    hooks/hooks.json
    hooks/bash-guard.mjs

Adding a plugin

  1. mkdir -p plugins/<name>/.claude-plugin
  2. Write plugins/<name>/.claude-plugin/plugin.json with name, version, description.
  3. Add components: hooks/hooks.json, commands/, agents/, skills/ as needed.
  4. Append an entry to plugins[] in .claude-plugin/marketplace.json:
{ "name": "<name>", "source": "./plugins/<name>", "description": "...", "category": "productivity" }

A plugin absent from plugins[] is not installable, regardless of its directory.

  1. Push, then claude plugin marketplace update mroberts.

Plugins

Plugin Purpose
guards Enforces the hard constraints in ~/.claude/CLAUDE.md — jj-only VCS, no Claude attribution, build+test gate before push/tag, secret scrubbing on writes.

Note on guards

hooks/bash-guard.mjs is referenced via ${CLAUDE_PLUGIN_ROOT} and travels with the plugin. shush is referenced by absolute path (/home/mroberts/.local/bin/shush) because it is a separately installed binary, not a repo file — that path is machine-specific and will need changing on another host.

S
Description
My personal claude plugins
Readme
396 KiB
Languages
Python 91.6%
JavaScript 5.6%
Shell 2.8%