Explorer un projet existant

Ce que contient l'archive

1 outil, prêt à déposer dans votre projet :

• codebase-explorer — Use this agent when the main agent encounters a non-trivial task (complexity > 3/10) that requires locating and understanding existing code, configurations, scripts, tests, or git history before proceeding. Examples include: adding a new feature that must integrate with existing architecture, debugging an issue that spans multiple files, refactoring code that has dependencies across the codebase, understanding how a specific functionality is currently implemented, or analyzing recent changes that might affect the current task. The agent should be invoked proactively when you recognize that proceeding without comprehensive codebase context would be inefficient or risky.\n\n\nContext: User asks to add Apple Sign In to an Expo app, which requires understanding existing authentication patterns.\nuser: "I need to add Apple Sign In to our Expo app"\nassistant: "This task requires understanding your existing authentication architecture. Let me use the codebase-explorer agent to map out the relevant code."\n\nassistant: "Based on the explorer report, I can see your current OAuth flow in src/auth/providers and the configuration in app.json. Here's how we'll integrate Apple Sign In..."\n\n\n\nContext: User reports a bug in a complex multi-file feature.\nuser: "The payment processing is failing intermittently"\nassistant: "I need to understand the full payment flow. Let me use the codebase-explorer agent to trace the relevant code paths and recent changes."\n\nassistant: "The explorer found the payment flow spans 8 files, and there was a recent change to the retry logic in commit abc123f. Let's investigate..."\n\n\n\nContext: User asks to refactor a feature with unknown dependencies.\nuser: "Can we refactor the user profile component to use hooks?"\nassistant: "Before refactoring, I should map all dependencies. Using the codebase-explorer agent to find all references and usage patterns."\n\nassistant: "The explorer found 23 files importing this component, including 5 tests. Here's a safe refactoring strategy..."\n