Skip to content

Prepare agent plugins for reviewed directories#2

Merged
DeliriumPulse merged 1 commit into
mainfrom
codex/plugin-submission-ready
Jul 14, 2026
Merged

Prepare agent plugins for reviewed directories#2
DeliriumPulse merged 1 commit into
mainfrom
codex/plugin-submission-ready

Conversation

@DeliriumPulse

@DeliriumPulse DeliriumPulse commented Jul 14, 2026

Copy link
Copy Markdown
Owner

Summary

  • position CodeTruss as a local acceptance gate instead of another AI reviewer
  • make OpenAI and Claude submission status explicit and accurate
  • bundle the approved brand mark and build byte-reproducible submission archives
  • add a validated tag-driven release workflow for both platform packages

Validation

  • npm test
  • npm run release:verify
  • claude plugin validate ./plugins/codetruss-claude
  • plugin-creator validate_plugin.py ./plugins/codetruss
  • git diff --check

Summary by CodeRabbit

  • New Features

    • Added reproducible release archives with checksums and verification.
    • Added automated release creation for tagged versions.
    • Added stronger validation for plugin metadata, branding assets, documentation, and release consistency.
    • Updated CodeTruss descriptions to emphasize local acceptance gates, verification, and receipts.
  • Documentation

    • Clarified marketplace availability, submission status, and release verification guidance.
  • Chores

    • Bumped the release version to 0.1.2 and excluded generated release artifacts from version control.

@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@DeliriumPulse, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 48 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9540d906-f8b3-4209-b575-f7799230f614

📥 Commits

Reviewing files that changed from the base of the PR and between 82e7f82 and 49a4600.

⛔ Files ignored due to path filters (1)
  • plugins/codetruss/assets/codetruss-mark-512.png is excluded by !**/*.png
📒 Files selected for processing (28)
  • .agents/plugins/marketplace.json
  • .claude-plugin/marketplace.json
  • .github/workflows/release.yml
  • .github/workflows/validate.yml
  • .gitignore
  • README.md
  • SECURITY.md
  • package.json
  • plugins/codetruss-claude/.claude-plugin/plugin.json
  • plugins/codetruss-claude/LICENSE
  • plugins/codetruss-claude/README.md
  • plugins/codetruss-claude/skills/codetruss/SKILL.md
  • plugins/codetruss-claude/skills/codetruss/agents/openai.yaml
  • plugins/codetruss/.codex-plugin/plugin.json
  • plugins/codetruss/LICENSE
  • plugins/codetruss/README.md
  • plugins/codetruss/skills/codetruss/SKILL.md
  • plugins/codetruss/skills/codetruss/agents/openai.yaml
  • scripts/build-release.mjs
  • scripts/validate.mjs
  • scripts/verify-release.mjs
  • skills/codetruss/SKILL.md
  • skills/codetruss/agents/openai.yaml
  • submission/PUBLISHER_CHECKLIST.md
  • submission/claude.md
  • submission/fixtures/README.md
  • submission/fixtures/setup.mjs
  • submission/openai.md
📝 Walkthrough

Walkthrough

Version 0.1.2 updates plugin metadata and descriptions, adds reproducible release archives with checksum verification, strengthens repository validation, and introduces tag-based GitHub release publishing.

Changes

Release metadata and packaging

Layer / File(s) Summary
Versioned plugin metadata
.claude-plugin/marketplace.json, package.json, plugins/*/.claude-plugin/plugin.json, plugins/codetruss/.codex-plugin/plugin.json
Versions, descriptions, keywords, interface metadata, and branding assets are updated for the local acceptance-gate release.
Reproducible release artifacts
scripts/build-release.mjs, scripts/verify-release.mjs, .github/workflows/*, .gitignore, README.md
Release archives and checksums are built from Git, rebuilt for byte comparison, verified in CI, and published from version tags.
Manifest and content validation
scripts/validate.mjs
Validation now checks canonical versions, branding assets, marketplace metadata, submission wording, and README marketplace status.
Skill and submission descriptions
skills/*, plugins/*/skills/*, submission/*
Skill, agent, and submission descriptions now document local acceptance gates, deterministic verdicts, and verifiable receipts.

Estimated code review effort: 3 (Moderate) | ~25 minutes

Sequence Diagram(s)

sequenceDiagram
  participant GitHubActions
  participant verify-release.mjs
  participant build-release.mjs
  participant Git
  participant GitHubRelease
  GitHubActions->>verify-release.mjs: run release verification
  verify-release.mjs->>build-release.mjs: build archives twice
  build-release.mjs->>Git: read plugin trees at release ref
  build-release.mjs-->>verify-release.mjs: return ZIP and checksum files
  GitHubActions->>GitHubRelease: publish verified tag and dist artifacts
Loading

Possibly related PRs

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title reflects the main intent of preparing the agent plugins for directory review, even though it omits release and validation details.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/plugin-submission-ready

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@scripts/build-release.mjs`:
- Around line 51-58: Update the archive generation around the git archive
invocation to obtain the commit date for the target ref and pass it through the
archive command’s --mtime option. Keep archiving the existing ${ref}:${tree}
tree while ensuring all generated file timestamps remain stable across repeated
runs.

In `@submission/claude.md`:
- Around line 22-24: Update the privacy claim in the project hook description to
state that code is not uploaded by default, while keeping provider review and
receipt sync identified as explicit opt-ins.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 8c9743bd-9fdb-41f7-bee0-00fae3d19222

📥 Commits

Reviewing files that changed from the base of the PR and between e4f2ab5 and 82e7f82.

⛔ Files ignored due to path filters (1)
  • plugins/codetruss/assets/codetruss-mark-512.png is excluded by !**/*.png
📒 Files selected for processing (19)
  • .claude-plugin/marketplace.json
  • .github/workflows/release.yml
  • .github/workflows/validate.yml
  • .gitignore
  • README.md
  • package.json
  • plugins/codetruss-claude/.claude-plugin/plugin.json
  • plugins/codetruss-claude/skills/codetruss/SKILL.md
  • plugins/codetruss-claude/skills/codetruss/agents/openai.yaml
  • plugins/codetruss/.codex-plugin/plugin.json
  • plugins/codetruss/skills/codetruss/SKILL.md
  • plugins/codetruss/skills/codetruss/agents/openai.yaml
  • scripts/build-release.mjs
  • scripts/validate.mjs
  • scripts/verify-release.mjs
  • skills/codetruss/SKILL.md
  • skills/codetruss/agents/openai.yaml
  • submission/claude.md
  • submission/openai.md

Comment thread scripts/build-release.mjs
Comment thread submission/claude.md Outdated
@DeliriumPulse
DeliriumPulse force-pushed the codex/plugin-submission-ready branch from 82e7f82 to b7bdcdd Compare July 14, 2026 23:06
@DeliriumPulse
DeliriumPulse force-pushed the codex/plugin-submission-ready branch from b7bdcdd to 49a4600 Compare July 14, 2026 23:10
@DeliriumPulse
DeliriumPulse merged commit 91ed019 into main Jul 14, 2026
2 checks passed
@DeliriumPulse
DeliriumPulse deleted the codex/plugin-submission-ready branch July 14, 2026 23:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant