Ship the Claude Code plugin listing artifact (v0.1.6) - #14
Conversation
Make this repository the canonical, marketplace-conformant Claude Code distribution artifact instead of standing up a second plugin repo. The existing layout already matches the documented multi-plugin marketplace pattern and both manifests pass `claude plugin validate --strict`, so the work was content, not structure. - README leads with the settled positioning, documents the exact in-session install (`/plugin marketplace add DeliriumPulse/codetruss-plugins` then `/plugin install codetruss@codetruss`), shows a verbatim excerpt of a real `codetruss report latest` receipt, and separates what runs locally from what is hosted so no reader can infer local injection analysis. - Plugin and marketplace descriptions carry the same positioning, which is what the `/plugin` browser actually renders. - Skill instructions were re-checked command by command against the shipped CLI v0.2.30 tarball; every command and flag the skill uses exists in its `--help`. The v0.2.24 minimum is unchanged. - PLUGIN-SUBMISSION.md holds paste-ready answers for the Console community submission and the awesome-claude-code issue form, both of which are humans-only filings. - validate.mjs now pins the positioning line, the install commands, the 0.2.30 verification claim, the analyzer-count line, and the absence of bundled hooks or an MCP server in the Claude manifest. Verified: `npm test` green, `claude plugin validate . --strict` green, `claude plugin validate ./plugins/codetruss-claude --strict` green, and a clean-HOME `marketplace add` plus `install` against the public repo and against this working tree both succeed on Claude Code 2.1.218. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 51 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (10)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Makes this repository the canonical, marketplace-conformant Claude Code distribution artifact for the this-week channel ship, rather than standing up a second
codetruss-claude-pluginrepo. The existing layout already matches the documented multi-plugin marketplace pattern (.claude-plugin/marketplace.jsonat root, plugin underplugins/), and both manifests already passedclaude plugin validate --strict, so nothing structural had to change.What changed
/plugin marketplace add DeliriumPulse/codetruss-plugins,/plugin install codetruss@codetruss), shows a verbatim excerpt of a realcodetruss report latestreceipt, and adds a "What runs where" section separating the local passes (13 registry analyzers, scope, secrets, verification commands) from the hosted ones (SAST, symbol graph). Links to /benchmark and /cli./pluginbrowser renders.Verification
npm testgreennpm run release:verifygreen, archives byte-for-byte reproducibleclaude plugin validate . --strictgreenclaude plugin validate ./plugins/codetruss-claude --strictgreenclaude plugin marketplace add+claude plugin installsucceed against both the public repo and this working tree on Claude Code 2.1.218Every command the skill uses was re-checked against the shipped CLI v0.2.30 tarball (sha256
9c97f573...); all of them appear in its--help. The v0.2.24 minimum is unchanged.Deliberately not done
No plugin-bundled hooks. The channel-mechanics skeleton proposed shipping a
hooks/agent-runner.cjsthat shells out tocodetruss hooks dispatch claude. That subcommand exists but is absent fromcodetruss --help, and this repo's stated posture, its skill text, and its validation guardrails all delegate hook installation to the CLI's own tested installer. The skill drivescodetruss setup --hooks claude, which is the documented flow.🤖 Generated with Claude Code