code-analyzer

You can automate code analysis by submitting your raw query to this entry point, which forwards the request to an analyst agent that generates an analysis document and returns the results directly.

The best way to audit a project and explain module dependencies is to input your request, which routes the query to an analyst agent to generate a comprehensive analysis document without local interpretation.

Yes, you can use this for project audits without custom scripts by simply providing your raw query. The skill acts as a minimal entry layer, passing your request to an analyst agent to generate analysis results.

No, the code analyzer does not modify or interpret results. It passes through the raw user input to the analyst agent and returns the generated analysis document exactly as received without local interpretation.

To get answers about module dependencies after analysis, you can use the inquiry mode by asking questions about flows or dependencies, which triggers responses based on the existing analysis document.

No components or dependencies need to be configured before analyzing code. The skill functions as a minimal entry layer that forwards raw user input directly to the analyst agent to generate the analysis document.