analyze

Analyze code repositories read-only to provide evidence-based insights.

Updated May 25, 2026

Search Tags:#static analysis #code analysis #repository analysis #evidence-based #insight generation

Ready to run

npx skills add https://github.com/BetaS/swm-gis-workshop --skill analyze-betas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyze
Source: https://github.com/BetaS/swm-gis-workshop/tree/main/.codex/skills/analyze
Command: npx skills add https://github.com/BetaS/swm-gis-workshop --skill analyze-betas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides deep, read-only analysis of codebases, offering a grounded explanation of code behavior, architecture, and potential issues without altering the code.

Core Features & Use Cases

Read-Only Analysis: Delivers insights without modifying the codebase.
Evidence-Based Explanation: Ensures explanations are grounded in code evidence.
Ranked Synthesis: Provides a ranked list of explanations based on evidence strength.
Use Case: When a user needs to understand why a workflow behaves a certain way or how a feature is implemented across modules.

Quick Start

Run the analyze skill to investigate the cause of a recent failure in the 'networking' module.

Frequently Asked Questions about analyze

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

FAQPage Schema

How do I perform static analysis on a repository to understand code architecture?▼

Static analysis on a repository is performed through deep, read-only codebase investigation to provide evidence-based insights into code behavior and architecture without modifying the code. It delivers a ranked synthesis of explanations grounded in code evidence.

Can I use code analysis to find the cause of a workflow failure without altering the codebase?▼

Yes, code analysis can troubleshoot workflow failures safely because it operates in a read-only mode. It investigates the codebase to deliver grounded explanations of code behavior without modifying any files.

How do I analyze code to generate evidence-based insights for code review?▼

To analyze code for review, run the tool against the repository to generate evidence-based insights. It processes the codebase and outputs a ranked list of explanations based on the strength of the code evidence found.

What is the best way to understand how a feature is implemented across multiple modules?▼

The best way to understand feature implementation across modules is using deep repository analysis to generate evidence-based insights. This approach traces code behavior and architecture comprehensively without altering the codebase.

Do I need specific tools to run repository analysis for troubleshooting?▼

Yes, repository analysis requires access to the codebase and tools for static analysis to perform deep troubleshooting. These tools enable the read-only investigation needed to generate evidence-based insights.