CleanVibe: local Codex plugin for JS/TS code quality and architecture audits

[gh0styx]

Hi everyone,

I built CleanVibe, a local Codex plugin for TypeScript and JavaScript code quality / architecture audits after fast AI-assisted coding sessions.

Repository:
https://github.com/gh0styx/cleanVibe-codex

Prepared openai/plugins branch:
https://github.com/gh0styx/plugins/tree/add-cleanvibe

CleanVibe focuses on issues that often appear after rapid AI-assisted development:

• duplicated logic
• feature boundary drift
• growing file/component complexity
• missing nearby tests
• risky shortcuts and suppressions
• debug noise
• React hook/render/data-boundary risks
• Next.js app-router/client-server/fetch-cache risks

It runs locally only. It analyzes repository files, git diff output, and minimal snippets for evidence. It does not upload code and does not modify source files during audits.

Main workflows:

• cleanvibe-diff — audit current git diff and untracked JS/TS files
• cleanvibe-project — audit the full JS/TS project
• cleanvibe-index — build a lightweight architecture index
• cleanvibe-react — check React-specific risks
• cleanvibe-next — check Next.js-specific risks

The plugin includes:

• .codex-plugin/plugin.json
• skills/cleanvibe/SKILL.md
• skills/cleanvibe/agents/openai.yaml
• local analyzer scripts
• logo asset
• marketplace entry for .agents/plugins/marketplace.json

I tried opening a PR to openai/plugins, but the repository currently limits PR creation to collaborators:

An owner of this repository has limited the ability to open a pull request to users that are collaborators on this repository.

What is the recommended path for submitting community Codex plugins for review or inclusion?

I would appreciate feedback on:

1. Whether CleanVibe fits the Codex plugin model.
2. Whether the plugin structure matches current expectations.
3. Whether there is an official/community submission path for openai/plugins.
4. Any changes needed before it can be listed or reviewed.

Thanks.