shadow-frog

Creates a shadow knowledge base from source code and markdown files for analysis and understanding.

18|4|Updated May 19, 2026
One-click install
npx skills add https://github.com/microsoft/ShadowFrog --skill shadow-frog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shadow-frog
Source: https://github.com/microsoft/ShadowFrog/tree/main/skills/shadow-frog
Command: npx skills add https://github.com/microsoft/ShadowFrog --skill shadow-frog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill integrates a shadow knowledge base to provide a deeper understanding of codebases, uncovering hidden bugs, edge cases, and design patterns.

Core Features & Use Cases

  • Shadow Knowledge Base: Stores behavioral insights and interactions within the codebase.
  • Cross-File Discoveries: Reveals interactions and dependencies across multiple files.
  • User Preferences and Conventions: Captures project-wide conventions and user preferences.
  • Quick Start: Invoke /shadow-frog-init to create the shadow, /shadow-frog-update to refresh it, or /shadow-frog-viewer to browse the shadow.

Quick Start

Use the shadow-frog-init command to create the shadow knowledge base for your project.

Frequently Asked Questions about shadow-frog

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

FAQPage Schema
How do I track cross-file dependencies and hidden bugs during codebase analysis?

A shadow knowledge base integrates behavioral insights and cross-file discoveries to reveal dependencies across multiple files. It uncovers hidden bugs and design patterns by mapping interactions within the codebase.

How do I capture and apply project-wide conventions and user preferences for code understanding?

Project-wide conventions and user preferences are captured within a shadow knowledge base to store behavioral insights. This integration applies recorded standards to improve code understanding and analysis across the source codebase.

What is the best way to integrate behavioral insights into source code analysis?

Integrating behavioral insights into source code analysis uses a shadow knowledge base represented by markdown files. This approach stores interactions and user preferences to uncover hidden edge cases and design patterns across the codebase.

How do I create and update a shadow knowledge base for my source codebase?

To create a shadow knowledge base, invoke the initialization command on your source codebase. You refresh the shadow knowledge base with the update command, or browse the stored behavioral insights using the viewer command.

Do I need markdown files to represent the shadow knowledge base for code analysis?

Yes, markdown files are required to represent the shadow knowledge base for code analysis. The source codebase uses these markdown files to store behavioral insights, cross-file discoveries, and user preferences.

When do I need a shadow knowledge base for codebase understanding?

A shadow knowledge base is needed for codebase understanding when uncovering hidden bugs, edge cases, and design patterns across files. It provides deeper context by integrating behavioral insights and cross-file discoveries into the source analysis.