/find-issue

​

What makes Deep Issues unique

• Predicts impact across your entire codebase, not just the changed files
• Identifies breaking changes before they reach production
• Traces dependency chains to find affected consumers
• Understands semantic changes beyond syntax modifications

​

API/MCP reference

​

Request format

{
  "tool": "issue",
  "parameters": {
    "input": [
      "@@ -10,7 +10,7 @@ router = APIRouter()",
      "",
      "[email protected](\"/foo\")",        // Original endpoint
      "[email protected](\"/foo/bar\")",    // Modified endpoint - potential breaking change
      " async def get_users()"
    ],
    "repositories": ["backend/api", "frontend/app"],  // Check impact across repos
    "session_id": "analysis-123"                      // Track conversation context
  }
}

​

Parameters

​

Recommended analysis strategies

• Include sufficient context - Provide several lines before and after changes for accurate analysis
• Specify affected repositories - Include all repos that might consume the changed code
• Group related changes - Analyze related modifications together for comprehensive impact assessment
• Use session_id for complex migrations - Chain multiple analyses for large refactoring projects
• Include semantic descriptions - Add comments about the intent of changes for better recommendations