Analyze a repo

Use Chat when you already have a repository or a concrete question.

Best for focused decisions

Repo analysis works best when the prompt includes the repository and the decision you are trying to make.

Example prompts

Analyze mastra-ai/mastra and explain fit, risks, and alternatives.

Is this repo mature enough for a production prototype?

A good answer should include repository evidence, risks, alternatives, and actions such as Save or Watch.

Ask for the repo and the decision context.

Let the agent fetch metadata, README, releases, and activity.

Compare the repo against your Memory and the stated use case.

Save or Watch the repo if it deserves follow-up.

Answer part	Why it matters
Fit	Explains why the repo matches or misses your actual workflow.
Evidence	Shows which tool results informed the answer.
Risks	Surfaces maintenance, scope, license, or adoption concerns.
Alternatives	Prevents one-repo tunnel vision.
Action	Moves the decision into Save, Watch, or a follow-up question.

Avoid vague prompts

“Is this good?” gives the agent too little context. Ask about adoption, alternatives, migration, production risk, or fit for a specific stack.