Deep Explorer: Git-Based Codebase Exploration

Execute this skill to explore and understand how a codebase works, using Git to efficiently track changes between explorations.

Execution Instructions

When invoked, you will:

0. Resolve scope and context — invoke context skill (always), then preflight if confidence is low
1. Verify Git repository - Ensure codebase is a Git repository
2. Determine exploration type - Full (first run) or Delta (incremental)
3. Detect changes - Use Git to find what changed since last exploration
4. Execute exploration - Explore entire codebase (full) or changed areas (delta)
5. Generate report - Comprehensive exploration or delta change report
6. Save baseline - Store current commit reference for next exploration

Dependency Check

Before executing any step, verify all required skills are present:

[skills-root]/context/SKILL.md
[skills-root]/preflight/SKILL.md
[skills-root]/domain-registry/README.md

Where [skills-root] is the parent of this skill's directory. Resolve with ls ../ from this skill's location.

If any required file is missing → stop immediately and output:

⚠ Missing required skills for deep-explorer:

  {missing-skill}
    Expected: {skills-root}/{missing-skill}/SKILL.md

Install the missing skill(s):
  git clone https://github.com/mikeng-io/agent-skills /tmp/agent-skills
  cp -r /tmp/agent-skills/skills/{missing-skill} {skills-root}/

Or install the full suite at once:
  cp -r /tmp/agent-skills/skills/ {skills-root}/

All dependencies present → proceed to Step 0.

Step 0: Scope & Context Resolution

Context (always required):

Invoke Skill("context") first. It identifies what to explore, confirms artifact type, and establishes domain focus:

context_report:
  artifact_type: ""  # code | financial | marketing | creative | research | mixed
  domains: []        # matched domain names from domain-registry
  routing: ""        # routing recommendation (informational for explorer)
  confidence: ""     # high | medium | low

Preflight (conditional — triggered by context confidence):

Invoke Skill("preflight") only if context_report.confidence == "low" OR one or more signals remain unresolved:

• The repository or directory to explore is not clearly identified
• The exploration intent is ambiguous (full map vs. specific area?)
• Domains or focus areas cannot be inferred

Preflight fills exactly the gaps context could not resolve (max 3 questions, one at a time):

scope_clarification:
  artifact: ""       # repository or directory to explore
  intent: "explore"
  domains: []        # focus domains for exploration (supplements context_report.domains)
  constraints: []    # specific areas to prioritize or exclude
  confidence: ""     # high | medium

If context_report.confidence == "high" → skip preflight entirely.

Merge into working scope:

working_scope:
  artifact: ""            # repository or directory to explore
  domains: []             # from context_report, supplemented by preflight
  constraints: []         # areas to prioritize or exclude
  context_summary: ""     # combined description for explorer agent prompts

Use working_scope to focus exploration agents on relevant domains and files.

Step 0: Verify Git Repository (Optional)

Check if the codebase is a Git repository to determine exploration mode:

# Check if Git repository
if ! git rev-parse --is-inside-work-tree 2>/dev/null; then
  # Git not available — proceed with full filesystem exploration
  EXPLORATION_TYPE="full"
  GIT_AVAILABLE=false
else
  # Verify Git is functional (has at least one commit)
  if ! git rev-parse HEAD 2>/dev/null; then
    EXPLORATION_TYPE="full"
    GIT_AVAILABLE=false
  else
    GIT_AVAILABLE=true
  fi
fi

If not a git repository:

• Set EXPLORATION_TYPE="full" (no delta mode without git)
• Proceed with file system exploration instead
• Note in report: "Git not available — full filesystem exploration mode"

Step 1: Determine Exploration Type

Check if previous exploration exists to determine strategy:

# Check for previous exploration
LAST_EXPLORATION=".outputs/exploration/latest-exploration.json"

if [ -f "$LAST_EXPLORATION" ]; then
  # Previous exploration exists
  EXPLORATION_TYPE="delta"
  BASELINE_COMMIT=$(jq -r '.baseline_commit' "$LAST_EXPLORATION")
  BASELINE_TIMESTAMP=$(jq -r '.baseline_timestamp' "$LAST_EXPLORATION")
else
  # No previous exploration
  EXPLORATION_TYPE="full"
  BASELINE_COMMIT=$(git rev-parse HEAD)
  BASELINE_TIMESTAMP=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
fi

Exploration Types:

FULL Exploration:

• First run (no baseline)
• Explore entire codebase
• Establish baseline for future delta explorations

DELTA Exploration:

• Subsequent runs (baseline exists)
• Detect changes using Git
• Re-explore only changed areas
• Generate delta report with impact analysis

Step 2: Detect Changes (Delta Only)

For delta exploration, use Git to detect all changes:

Committed Changes

# Get baseline commit from last exploration
BASELINE=$(jq -r '.baseline_commit' .outputs/exploration/latest-exploration.json)
CURRENT=$(git rev-parse HEAD)

# Find committed changes since baseline
git diff --name-status $BASELINE $CURRENT > committed_changes.txt

# Categorize changes
MODIFIED=$(git diff --name-only --diff-filter=M $BASELINE $CURRENT)
ADDED=$(git diff --name-only --diff-filter=A $BASELINE $CURRENT)
DELETED=$(git diff --name-only --diff-filter=D $BASELINE $CURRENT)
RENAMED=$(git diff --name-only --diff-filter=R $BASELINE $CURRENT)

Uncommitted Changes

# Working directory changes (modified but not staged)
UNCOMMITTED_MODIFIED=$(git diff --name-only HEAD)

# Staged changes (committed to index but not committed)
STAGED=$(git diff --name-only --cached)

# Untracked files (new files not in Git)
UNTRACKED=$(git ls-files --others --exclude-standard)

Combine All Changes

changes_detected:
  committed:
    status: stable
    files:
      - modified: [list from git diff]
      - added: [list from git diff]
      - deleted: [list from git diff]
      - renamed: [list from git diff]

  uncommitted:
    status: work_in_progress
    files:
      - modified: [list from git diff HEAD]
      - staged: [list from git diff --cached]
      - untracked: [list from git ls-files --others]

total_changes: <count>
exploration_scope: [list of unique files to re-explore]

Change Categorization:

• Committed changes → Stable, unlikely to change
• Uncommitted changes → Work in progress, may change
• Untracked files → New additions, not yet in Git

Step 3: Execute Exploration

Full Exploration (First Run)

Spawn explorer sub-agents with dependency-aware execution for optimal efficiency:

Dependency-Aware Execution Strategy:

Exploration has natural dependencies - some tasks must complete before others:

• Architecture analysis needs structure and technology information first
• Workflow tracing needs structure and dependency information first
• Technology and dependency analysis both need structure first

Task Definitions with Dependencies:

tasks:
  # Wave 1: Foundation (must run first)
  - id: structure
    description: "Analyze directory structure"
    agent: "structure-explorer"
    depends_on: []

  # Wave 2: Technology and dependency analysis (need structure)
  - id: technology
    description: "Identify technologies and frameworks"
    agent: "technology-explorer"
    depends_on: [structure]

  - id: dependencies
    description: "Map dependencies and imports"
    agent: "dependency-explorer"
    depends_on: [structure]

  # Wave 3: Architecture and workflows (need structure + tech/deps)
  - id: architecture
    description: "Analyze architectural patterns"
    agent: "architecture-explorer"
    depends_on: [structure, technology]

  - id: workflows
    description: "Trace workflows and data flows"
    agent: "workflow-explorer"
    depends_on: [structure, dependencies]

execution:
  mode: dag-orchestrated
  waves:
    wave_1: [structure]                     # 1 task
    wave_2: [technology, dependencies]      # 2 tasks in parallel
    wave_3: [architecture, workflows]       # 2 tasks in parallel
  capability: high

Why This Order Matters:

1. Structure first - You can't analyze architecture without knowing what files exist
2. Tech and deps together - Both analyze different aspects of structure independently
3. Architecture and workflows last - Both benefit from having structure + context

Performance Benefit:

• Sequential execution: ~15 seconds (5 tasks × 3s avg)
• Dependency-aware parallel: ~9 seconds (1 wave of 1 + 2 waves of 2)
• Speedup: 1.7x

Explorer Agent Templates:

Structure Explorer Agent

Capability: high

You are a STRUCTURE EXPLORER. Analyze the repository structure and organization.

## Your Task
1. Map directory hierarchy using Glob and ls
2. Count files by type (extensions)
3. Identify organizational patterns
4. Find configuration files
5. Analyze naming conventions

## Output Format (JSON)
{
  "agent": "structure-explorer",
  "directory_structure": {
    "total_directories": 24,
    "total_files": 188,
    "hierarchy": "..."
  },
  "file_distribution": {
    "typescript": 145,
    "javascript": 23,
    "json": 12,
    "markdown": 8
  },
  "organizational_patterns": [
    "Feature-based organization",
    "Separation of concerns",
    "Test files colocated with source"
  ],
  "configuration_files": [
    "package.json",
    "tsconfig.json",
    ".eslintrc.js",
    "docker-compose.yml"
  ]
}

Technology Explorer Agent

Capability: high

You are a TECHNOLOGY EXPLORER. Inventory the technology stack.

## Your Task
1. Detect languages from file extensions
2. Identify frameworks from package.json, requirements.txt, etc.
3. Find build tools (Makefile, scripts, etc.)
4. Extract dependencies and versions

## Output Format (JSON)
{
  "agent": "technology-explorer",
  "languages": [
    {"name": "TypeScript", "file_count": 145, "primary": true},
    {"name": "JavaScript", "file_count": 23, "primary": false}
  ],
  "frameworks": [
    {"name": "Express.js", "version": "^4.18.0", "purpose": "web server"},
    {"name": "React", "version": "^18.2.0", "purpose": "frontend"}
  ],
  "build_tools": ["npm", "webpack", "docker"],
  "dependencies": {
    "production": {...},
    "development": {...}
  }
}

Architecture Explorer Agent

Capability: high

You are an ARCHITECTURE EXPLORER. Identify architectural patterns and structure.

## Your Task
1. Analyze project structure (MVC, microservices, etc.)
2. Identify module organization
3. Detect design patterns used
4. Assess separation of concerns

## Output Format (JSON)
{
  "agent": "architecture-explorer",
  "project_structure": "Layered architecture",
  "layers": [
    {"name": "API Layer", "location": "src/api/"},
    {"name": "Business Logic", "location": "src/services/"},
    {"name": "Data Layer", "location": "src/models/"}
  ],
  "design_patterns": [
    {"pattern": "Factory", "location": "src/factories/"},
    {"pattern": "Repository", "location": "src/repositories/"},
    {"pattern": "Dependency Injection", "implementation": "constructor-based"}
  ],
  "separation_quality": "high"
}

Workflow Explorer Agent

Capability: high

You are a WORKFLOW EXPLORER. Trace code flows and entry points.

## Your Task
1. Find entry points (main files)
2. Trace key workflows
3. Map data flow patterns
4. Identify integration points

## Output Format (JSON)
{
  "agent": "workflow-explorer",
  "entry_points": [
    {"file": "src/index.ts", "purpose": "Application bootstrap"}
  ],
  "key_workflows": [
    {
      "name": "User Authentication",
      "flow": [
        "src/api/auth/routes.ts",
        "src/services/auth.service.ts",
        "src/repositories/user.repository.ts",
        "Database"
      ]
    }
  ],
  "data_flow_patterns": ["Request-Response", "Event-driven"],
  "integration_points": ["Database", "External APIs", "Cache"]
}

Dependency Explorer Agent

Capability: high

You are a DEPENDENCY EXPLORER. Map component relationships and dependencies.

## Your Task
1. Analyze import/export patterns
2. Map component dependencies using Grep
3. Identify external dependencies
4. Assess module coupling

## Output Format (JSON)
{
  "agent": "dependency-explorer",
  "import_patterns": {
    "relative_imports": 145,
    "absolute_imports": 23,
    "external_imports": 67
  },
  "component_dependencies": {
    "api/": ["services/", "middleware/", "utils/"],
    "services/": ["repositories/", "models/"]
  },
  "coupling_analysis": {
    "level": "low",
    "circular_dependencies": []
  }
}

Domain-Aware Agent Selection (optional enhancement): If domain-registry is available, read domain-registry/domains/technical.md to identify additional domain-specific explorers relevant to the detected technology stack.

Aggregate Results:

After all explorer agents complete, aggregate their findings into comprehensive report.

Delta Exploration (Incremental)

Spawn parallel file analyzer sub-agents for each changed file/directory:

Parallel Execution Strategy:

# Group changes by directory or file
change_groups:
  - src/auth/ (3 files changed)
  - src/api/ (2 files changed)
  - src/config/ (1 file changed)

# Spawn one agent per group
spawn_in_parallel:
  - File Analyzer: src/auth/*
  - File Analyzer: src/api/*
  - File Analyzer: src/config/*

execution:
  mode: parallel
  max_concurrent: 10
  capability: high

File Analyzer Agent Template:

Capability: high

You are a FILE ANALYZER for delta exploration. Analyze changed files and their impact.

## Files to Analyze
{list_of_changed_files_in_this_group}

## Change Types Detected
{committed/uncommitted status for each file}

## Your Task

For each changed file:

1. **Read file content** using Read tool
2. **Analyze change type:**
   - Modified: Compare with previous, identify what changed
   - Added: Document new component
   - Deleted: Note removal and document what it was
   - Renamed: Track move and update references

3. **Trace impact** using Grep:
   - What components depend on this file?
   - What does this file depend on?
   - Are there breaking changes?
   - What tests are affected?

4. **Flag stability:**
   - Committed → ✅ Stable
   - Uncommitted → ⚠️ Work in progress

## Output Format (JSON)
{
  "agent": "file-analyzer-{group}",
  "files_analyzed": [
    {
      "file": "src/auth/oauth2.ts",
      "change_type": "added",
      "stability": "committed",
      "status": "✅ Stable",
      "analysis": {
        "type": "Authentication Module",
        "purpose": "OAuth2 authentication flow",
        "exports": ["OAuth2Strategy", "authenticate()"],
        "imports": ["express", "passport-oauth2"],
        "dependencies": {
          "imports": ["express", "passport"],
          "imported_by": ["src/api/auth/routes.ts"]
        },
        "impact": [
          "Replaces src/legacy/old-auth.ts",
          "Used by src/api/auth/routes.ts",
          "Affects login workflow"
        ],
        "breaking_changes": [
          "Session-based auth no longer supported"
        ],
        "affected_tests": [
          "tests/auth/oauth2.spec.ts (new)",
          "tests/api/auth.spec.ts (modified)"
        ]
      }
    }
  ]
}

Aggregate Results:

After all file analyzer agents complete, aggregate their findings:

• Combine all file analyses
• Cross-reference impacts
• Identify system-wide changes
• Generate delta report

Step 4: Generate Report

Full Exploration Report Structure

# Full Codebase Exploration Report

**Exploration Type:** Full (baseline)
**Repository:** {repository_name}
**Explored At:** {timestamp}
**Baseline Commit:** {commit_hash}
**Total Files:** {file_count}

---

## Repository Structure

### Directory Hierarchy

project/ ├── src/ │ ├── api/ │ ├── services/ │ └── utils/ ├── tests/ ├── config/ └── docs/

### File Distribution
- TypeScript: 145 files
- JavaScript: 23 files
- JSON: 12 files
- Markdown: 8 files
- Total: 188 files

---

## Technology Stack

### Languages
- TypeScript (primary)
- JavaScript (configuration)
- Shell scripts (deployment)

### Frameworks & Libraries
- Express.js (web server)
- React (frontend)
- Jest (testing)
- Prettier/ESLint (code quality)

### Build Tools
- npm (package management)
- Webpack (bundling)
- Docker (containerization)

### Dependencies
**Production:**
- express: ^4.18.0
- react: ^18.2.0
- ...

**Development:**
- jest: ^29.0.0
- typescript: ^5.0.0
- ...

---

## Architecture Analysis

### Project Structure
**Pattern:** Layered architecture with clear separation

**Layers:**
1. API Layer (`src/api/`)
2. Business Logic (`src/services/`)
3. Data Layer (`src/models/`)
4. Utilities (`src/utils/`)

### Design Patterns
- Factory Pattern: `src/factories/`
- Repository Pattern: `src/repositories/`
- Dependency Injection: Constructor-based
- Middleware Pattern: `src/middleware/`

---

## Entry Points & Workflows

### Main Entry Point
**File:** `src/index.ts`
**Purpose:** Application bootstrap
**Key Operations:**
1. Load configuration
2. Connect to database
3. Initialize Express app
4. Start server

### Key Workflows

**User Authentication Flow:**

src/api/auth/routes.ts → src/services/auth.service.ts → src/repositories/user.repository.ts → Database

**API Request Flow:**

Express Middleware → Rate Limiting → Authentication → Route Handler → Service Layer → Repository Layer → Response

---

## Component Relationships

### Module Dependencies

**api/ depends on:**
- services/
- middleware/
- utils/

**services/ depends on:**
- repositories/
- models/
- utils/

**Coupling Analysis:**
- Low coupling between layers ✅
- Clear dependency direction ✅
- Minimal circular dependencies ✅

---

## Configuration

### Environment Variables
- `PORT`: Server port (default: 3000)
- `DATABASE_URL`: Database connection string
- `JWT_SECRET`: Authentication secret
- `NODE_ENV`: Environment (development/production)

### Config Files
- `package.json`: Dependencies and scripts
- `tsconfig.json`: TypeScript configuration
- `.eslintrc.js`: Linting rules
- `docker-compose.yml`: Container orchestration

---

## Testing Strategy

### Test Organization

tests/ ├── unit/ # Unit tests ├── integration/ # Integration tests └── e2e/ # End-to-end tests

### Coverage
- Unit tests: 87%
- Integration tests: 65%
- E2E tests: 12 scenarios

---

## Baseline Metadata

```json
{
  "exploration_type": "full",
  "baseline_commit": "abc123",
  "baseline_timestamp": "2026-01-30T14:30:00Z",
  "repository": "deep-verify",
  "files_analyzed": 188,
  "directories": 24
}

This exploration establishes the baseline for future delta explorations.

### Delta Exploration Report Structure

```markdown
# Delta Codebase Exploration Report

**Exploration Type:** Delta (incremental)
**Repository:** {repository_name}
**Baseline:** Commit {baseline_commit} ({baseline_date})
**Current:** Commit {current_commit} + uncommitted changes
**Time Span:** {days} days
**Explored At:** {timestamp}

---

## Change Summary

**Git Statistics:**
- {n} files modified (committed)
- {n} files added (committed)
- {n} files deleted (committed)
- {n} files renamed (committed)
- {n} files modified (uncommitted) ⚠️
- {n} files staged (uncommitted) ⚠️
- {n} files untracked (uncommitted) ⚠️

**Total:** {n} files changed

**Affected Areas:**
- `src/auth/` - OAuth2 implementation
- `src/api/` - New endpoints
- `src/config/` - Database changes

---

## Committed Changes (Stable)

### ✅ src/auth/oauth2.ts (Added, Committed)
**Commit:** def456
**Status:** ✅ Committed (stable)
**Type:** Authentication Module
**Purpose:** OAuth2 authentication flow

**Structure:**
```typescript
export class OAuth2Strategy {
  authenticate(): Promise<User>
  refresh(): Promise<Token>
}

Dependencies:

• Imports: express, passport-oauth2
• Exports: OAuth2Strategy, authenticate()

Impact:

• Replaces src/legacy/old-auth.ts
• Used by src/api/auth/routes.ts
• Affects login workflow

✅ src/middleware/rate-limit.ts (Added, Committed)

Commit: def456 Status: ✅ Committed (stable) Type: Middleware Purpose: API rate limiting

Structure:

export const rateLimiter: RateLimitMiddleware

Configuration:

• Max: 100 requests per 15 minutes
• Applies to all API routes

Impact:

• All /api/* endpoints now rate-limited
• Frontend may need retry logic

✅ src/legacy/old-auth.ts (Deleted, Committed)

Commit: def456 Status: ✅ Committed (stable) Type: Authentication (legacy) Reason: Replaced by OAuth2 module

Impact:

• All references migrated to src/auth/oauth2.ts
• Session-based auth no longer supported
• Breaking change for old clients

Uncommitted Changes (Work in Progress)

⚠️ src/api/routes.ts (Modified, Uncommitted)

Status: ⚠️ Work in progress (unstaged) Type: API Routes

Changes Detected:

• Added 3 new endpoints
• Integrated rate limiting middleware
• Updated error handling

Impact:

• New authentication flow endpoints
• All routes now rate-limited

Warning: Changes not committed - may still change

⚠️ src/utils/helpers.ts (New File, Untracked)

Status: ⚠️ Not tracked by Git Type: Utility Functions

Structure:

export function formatDate(date: Date): string
export function validateEmail(email: string): boolean

Impact:

• Used by src/api/routes.ts
• Not yet in repository

Warning: New file not added to Git

Architecture Changes

New Patterns Introduced

• OAuth2 authentication pattern (committed)
• Middleware-based rate limiting (committed)
• Centralized error handling (uncommitted ⚠️)

Removed Patterns

• Legacy session-based auth (committed)
• Per-route auth checks (committed)

Structural Changes

• Added src/middleware/ directory
• Reorganized src/auth/ structure
• Removed src/legacy/ directory

Impact Analysis

Authentication System

Status: ✅ Stable (committed) What Changed: OAuth2 replaces session-based auth

Affected Components:

• Login flow (rewritten)
• Session management (removed)
• User model (added OAuth fields)
• API endpoints (new auth middleware)

Breaking Changes:

• Old /login endpoint removed
• Session cookies no longer used
• API clients must use OAuth2 tokens

API Layer

Status: ⚠️ Partially stable (mixed committed/uncommitted) What Changed: Rate limiting + new endpoints

Stable (Committed):

• Rate limiting middleware deployed
• Configuration complete

Unstable (Uncommitted):

• New endpoints not yet committed
• Error handling still being refined

Recommendation: Complete and commit API changes

Dependency Changes

New Dependencies

• passport-oauth2 (for OAuth2)
• express-rate-limit (for rate limiting)

Removed Dependencies

• express-session (replaced by OAuth2)

Recommendations

For Committed Changes:

1. ✅ Review OAuth2 security implementation
2. ✅ Test rate limiting in production
3. ✅ Verify legacy auth removal is complete
4. ✅ Update API documentation

For Uncommitted Changes:

1. ⚠️ Complete src/api/routes.ts integration
2. ⚠️ Add src/utils/helpers.ts to Git
3. ⚠️ Commit or stash work in progress
4. ⚠️ Run tests before committing

Next Exploration Baseline

{
  "exploration_type": "delta",
  "baseline_commit": "def456",
  "baseline_timestamp": "2026-01-30T16:45:00Z",
  "previous_baseline": "abc123",
  "changes_analyzed": {
    "committed": 3,
    "uncommitted": 2,
    "total": 5
  }
}

Next delta exploration will use commit def456 as baseline.

---

## Step 5: Save Baseline & Report

## Artifact Output

Save to `.outputs/exploration/{YYYYMMDD-HHMMSS}-exploration-{slug}.md` with YAML frontmatter:

```yaml
---
skill: deep-explorer
timestamp: {ISO-8601}
artifact_type: exploration
domains: [{domain1}, {domain2}]
verdict: PASS | FAIL | CONCERNS        # if applicable
context_summary: "{brief description of what was reviewed}"
session_id: "{unique id}"
---

Also save JSON companion: {timestamp}-exploration-{slug}.json

No symlinks. To find the latest artifact:

ls -t .outputs/exploration/ | head -1

QMD Integration (optional, progressive enhancement):

qmd collection add .outputs/exploration/ --name "deep-explorer-artifacts" --mask "**/*.md" 2>/dev/null || true
qmd update 2>/dev/null || true

Output Structure:

.outputs/exploration/
├── 20260125-103000-exploration-full.md
├── 20260125-103000-exploration-full.json
├── 20260130-164500-exploration-delta.md
└── 20260130-164500-exploration-delta.json

Configuration (Optional)

Default configuration works for most projects, but can be customized:

# .outputs/exploration/config.yaml

exploration:
  # Delta exploration scope
  include_uncommitted: true
  max_file_size: 1048576  # 1MB limit per file
  ignore_patterns:
    - "node_modules/**"
    - "*.lock"
    - "dist/**"
    - "build/**"

  # Analysis depth
  trace_dependencies: true
  analyze_imports: true
  detect_patterns: true

  # Output format
  include_code_samples: false
  max_sample_lines: 10

Environment Variables:

export DEEP_EXPLORER_OUTPUT_DIR=".outputs/exploration/"
export DEEP_EXPLORER_INCLUDE_UNCOMMITTED="true"

Notes

• Git Optional: Git enables delta tracking; without it, full filesystem exploration mode is used
• Baseline Tracking: First run establishes baseline, subsequent runs use delta (when git available)
• Uncommitted Changes: Detected and flagged as work in progress
• No Git Commits: Does not commit exploration reports to Git
• Flexible: Works with dirty working directory
• Efficient: Only re-explores changed areas on delta runs
• Multi-Model: For cross-model codebase analysis, see deep-council