review-plugin

To audit a plugin for nested kernel compliance, run a review targeting the plugin name to automatically verify IDisposable implementation, IInternalCallTracker usage, ChatHistory parameters, logging, thread-safety, and proper registration against AnimalAL standards.

Yes, you can audit all nested plugins simultaneously by running the broad audit command. This checks every NestedKernel SK pattern for IInternalCallTracker, IDisposable, thread-safety, lazy initialization, and test coverage consistency across the entire project.

A nested kernel plugin review checks for IDisposable and IInternalCallTracker implementation, ChatHistory parameter usage, logging integration, error handling, description attributes, thread-safety, lazy initialization, registration, and test coverage conformity.

To get concrete improvement suggestions for AnimalAL plugin code, append the suggest-fixes flag to your plugin review command. This provides actionable feedback to correct deviations from nested kernel standards and shared test suite expectations.

Yes, reference implementations and shared test suites are required to validate plugin consistency. The review process compares your plugin against these references to verify correctness, safety, and maintainability during nested kernel usage.

You should run a plugin code review when auditing a plugin for conformance to AnimalAL project standards or preparing for a formal code review, ensuring correct IDisposable, logging, and thread-safety implementation before deployment.