analyze

Analyze repositories to produce evidence-backed explanations with file references and confidence levels.

1|Updated Mar 17, 2025
One-click install
npx skills add https://github.com/ozby/ingest-lens --skill analyze-ozby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze
Source: https://github.com/ozby/ingest-lens/tree/main/.codex/skills/analyze
Command: npx skills add https://github.com/ozby/ingest-lens --skill analyze-ozby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only, evidence-backed explanations of a codebase by analyzing multiple files and returning a ranked synthesis with explicit confidence and clear evidence-vs-inference boundaries.

Core Features & Use Cases

  • Ground truth from multiple sources: cross-file analysis that explains behavior with explicit file references.
  • Ranked syntheses: confidence-scored conclusions distinguishing facts from inferences.
  • Evidence-vs-inference separation: clear delineation between what is known and what is interpreted.

Quick Start

Ask to analyze the repository to produce a grounded, ranked explanation with file references and clear evidence-vs-inference boundaries.

Frequently Asked Questions about analyze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an evidence-backed explanation of a codebase's architecture?

To generate an evidence-backed codebase explanation, analyze the repository across multiple modules and dependencies. The resulting synthesis ranks conclusions by confidence and provides concrete file references to support architectural findings.

What is the best way to analyze cross-file impacts and behavior causality in a repository?

Analyzing cross-file impacts requires evaluating behavior causality across modules. This approach produces a ranked synthesis that distinguishes between known facts and interpreted inferences, supported by explicit file-level references.

Can I distinguish between actual evidence and inferred conclusions when analyzing code?

Yes, you can distinguish evidence from inference. The analysis enforces evidence-vs-inference separation, clearly delineating what is known from what is interpreted and assigning confidence levels to each conclusion.

Does this read-only codebase analysis modify my source files?

No, this read-only codebase analysis does not modify your source files. It safely inspects the repository to produce grounded, evidence-backed explanations of behavior and architecture without writing or altering code.

How do I get confidence-scored conclusions for complex multi-module dependencies?

To get confidence-scored conclusions for multi-module dependencies, analyze the repository architecture and behavior. The output provides a ranked synthesis with explicit confidence levels and grounded file references.

When do I need to use evidence-vs-inference boundaries for codebase synthesis?

You need evidence-vs-inference boundaries when evaluating complex codebases to avoid unsupported assumptions. This process ensures conclusions are grounded with concrete file references and clear confidence levels separating fact from interpretation.