noodlbox

Impact Detection

Analyze git changes to understand code impact

Analyze your uncommitted changes to see which symbols and documentation are affected before committing.

Parameters

ParameterTypeRequiredDescription
repositorystringYesRepository name (e.g., "owner/repo")
change_scopestringNoWhat to analyze (default: "unstaged")
base_refstringNoBase reference for "compare" scope (default: "HEAD")
include_contentbooleanNoInclude symbol code content (default: false)
pagenumberNoPage number for pagination (0-based, default: 0)

Change Scopes

ScopeWhat it comparesUse Case
unstagedIndex vs working treeSee impact before git add
stagedHEAD vs indexReview before committing
allHEAD vs working treeFull picture of uncommitted work
comparebase_ref vs working treeCompare against branch/commit

For compare scope, you must provide an explicit base_ref (e.g., "main", "develop", or a commit SHA). Using "HEAD" with compare will return an error - use all scope instead.

Usage

Ask your agent:

"What code is affected by my current changes?"

"Check the impact of my staged changes before I commit"

"Compare my changes against main branch"

Response

{
  "summary": {
    "changed_symbols_count": 3,
    "changed_files_count": 2,
    "total_impacted_symbols": 12,
    "total_lines_changed": 47,
    "affected_documents_count": 2,
    "message": null
  },
  "changed_symbols": [
    {
      "id": "sym_123",
      "name": "authenticateUser",
      "file_path": "src/auth/login.ts",
      "change_type": "Modified"
    }
  ],
  "changed_files": [
    {
      "path": "src/auth/login.ts",
      "has_symbols": true,
      "symbol_count": 2,
      "lines_added": 15,
      "lines_deleted": 5
    }
  ],
  "affected_documents": [
    {
      "id": "doc_001",
      "title": "Authentication Guide",
      "file_path": "docs/auth/README.md",
      "preview": "This document explains..."
    }
  ],
  "pagination": {
    "page": 0,
    "page_size": 10,
    "total_pages": 1,
    "has_more": false
  }
}

Understanding Results

FieldDescription
affected_documentsDocumentation linked to changed symbols (may need updating)
has_symbols: falseFiles with changes but no analyzed code (configs, docs, etc.)

Empty Results

When no code changes are detected, summary.message explains why:

  • No uncommitted changes: Working tree is clean
  • No symbols in changed files: Changes are in configs, docs, or unsupported languages

Change Types

TypeDescription
ModifiedSymbol content was changed
AddedNew symbol in a changed file
DeletedSymbol removed or file deleted

Common Workflows

Before staging:

"What's the impact of my unstaged changes?"

Before committing:

"Check impact of staged changes"

Before creating PR:

"Compare my changes against main branch"

On this page