oss-maintainer

To check open-source project quality before a PR or release, run a structured review covering code simplicity, duplication, documentation currency, component-library compliance, and test coverage gaps. This process identifies architectural misalignment and documentation drift to ensure release readiness.

An OSS code review for architectural alignment checks code simplicity, duplication, and adherence to component-library compliance. It verifies that s-* classes, x-signals.* components, and Flux UI patterns are respected, ensuring the project follows established Signals patterns.

Verify documentation currency by running an OSS review that checks user docs, API docs, and PHPDoc against recent code changes. The review scopes changes across code, docs, and architecture to identify areas where documentation has drifted from implementation.

Run an OSS review for test coverage and code duplication after completing a significant feature or before a PR or release. You can also explicitly invoke it via /oss-review to enforce a structured workflow that identifies test coverage gaps and duplication.

Yes, you can use an OSS review to enforce component-library compliance for Flux UI. The review checks for correct usage of s-* classes and x-signals.* components, ensuring that submitted code adheres to required architectural patterns before integration.