explore
installsforks
How to install explore?
parcadei/continuous-claude-v3/explore
$npx -y skills add parcadei/Continuous-Claude-v3 --skill exploreMeta-skill for internal codebase exploration at varying depths (quick/deep/architecture)
SKILL.md
| 1 | # Explore - Internal Codebase Exploration |
| 2 | |
| 3 | Meta-skill for exploring an internal codebase at varying depths. READ-ONLY workflow - no code changes. |
| 4 | |
| 5 | ## Usage |
| 6 | |
| 7 | ``` |
| 8 | /explore <depth> [options] |
| 9 | ``` |
| 10 | |
| 11 | ## Question Flow (No Arguments) |
| 12 | |
| 13 | If the user types just `/explore` with no or partial arguments, guide them through this question flow. Use AskUserQuestion for each phase. |
| 14 | |
| 15 | ### Phase 0: Workflow Selection |
| 16 | |
| 17 | ```yaml |
| 18 | question: "How would you like to explore?" |
| 19 | header: "Explore" |
| 20 | options: |
| 21 | - label: "Help me choose (Recommended)" |
| 22 | description: "I'll ask questions to pick the right exploration depth" |
| 23 | - label: "Quick - fast overview" |
| 24 | description: "Chain: tldr tree → tldr structure (~1 min)" |
| 25 | - label: "Deep - comprehensive analysis" |
| 26 | description: "Chain: onboard → tldr → research → document (~5 min)" |
| 27 | - label: "Architecture - layers & dependencies" |
| 28 | description: "Chain: tldr arch → call graph → layer mapping (~3 min)" |
| 29 | ``` |
| 30 | |
| 31 | **Mapping:** |
| 32 | - "Help me choose" → Continue to Phase 1-4 questions |
| 33 | - "Quick" → Set depth=quick, skip to Phase 2 (scope) |
| 34 | - "Deep" → Set depth=deep, skip to Phase 2 (scope) |
| 35 | - "Architecture" → Set depth=architecture, skip to Phase 2 (scope) |
| 36 | |
| 37 | **If Answer is Unclear (via "Other"):** |
| 38 | ```yaml |
| 39 | question: "I want to understand how deep you want to explore. Did you mean..." |
| 40 | header: "Clarify" |
| 41 | options: |
| 42 | - label: "Help me choose" |
| 43 | description: "Not sure - guide me through questions" |
| 44 | - label: "Quick - fast overview" |
| 45 | description: "Just want to see what's here" |
| 46 | - label: "Deep - comprehensive analysis" |
| 47 | description: "Need thorough understanding" |
| 48 | - label: "Neither - let me explain differently" |
| 49 | description: "I'll describe what I need" |
| 50 | ``` |
| 51 | |
| 52 | ### Phase 1: Exploration Goal |
| 53 | |
| 54 | ```yaml |
| 55 | question: "What are you trying to understand?" |
| 56 | header: "Goal" |
| 57 | options: |
| 58 | - label: "Get oriented in the codebase" |
| 59 | description: "Quick overview of structure" |
| 60 | - label: "Understand how something works" |
| 61 | description: "Deep dive into specific area" |
| 62 | - label: "Map the architecture" |
| 63 | description: "Layers, dependencies, patterns" |
| 64 | - label: "Find where something is" |
| 65 | description: "Locate specific code/functionality" |
| 66 | ``` |
| 67 | |
| 68 | **Mapping:** |
| 69 | - "Get oriented" → quick depth |
| 70 | - "Understand how" → deep depth |
| 71 | - "Map architecture" → architecture depth |
| 72 | - "Find where" → quick with --focus |
| 73 | |
| 74 | ### Phase 2: Scope |
| 75 | |
| 76 | ```yaml |
| 77 | question: "What area should I focus on?" |
| 78 | header: "Focus" |
| 79 | options: |
| 80 | - label: "Entire codebase" |
| 81 | description: "Explore everything" |
| 82 | - label: "Specific directory or module" |
| 83 | description: "I'll specify the path" |
| 84 | - label: "Specific concept/feature" |
| 85 | description: "e.g., 'authentication', 'API routes'" |
| 86 | ``` |
| 87 | |
| 88 | If "Specific directory" or "Specific concept" → ask follow-up for the path/keyword. |
| 89 | |
| 90 | ### Phase 3: Output Format |
| 91 | |
| 92 | ```yaml |
| 93 | question: "What should I produce?" |
| 94 | header: "Output" |
| 95 | options: |
| 96 | - label: "Just tell me what you find" |
| 97 | description: "Interactive summary in chat" |
| 98 | - label: "Create a documentation file" |
| 99 | description: "Write to thoughts/shared/docs/" |
| 100 | - label: "Create handoff for implementation" |
| 101 | description: "Prepare context for coding agent" |
| 102 | ``` |
| 103 | |
| 104 | **Mapping:** |
| 105 | - "Documentation file" → --output doc |
| 106 | - "Handoff for implementation" → --output handoff |
| 107 | |
| 108 | ### Phase 4: Entry Point (Architecture only) |
| 109 | |
| 110 | If architecture depth selected: |
| 111 | |
| 112 | ```yaml |
| 113 | question: "Where should I start the analysis?" |
| 114 | header: "Entry point" |
| 115 | options: |
| 116 | - label: "Auto-detect (main, cli, app)" |
| 117 | description: "Find common entry points" |
| 118 | - label: "Specific function/file" |
| 119 | description: "I'll specify the entry point" |
| 120 | ``` |
| 121 | |
| 122 | ### Summary Before Execution |
| 123 | |
| 124 | ``` |
| 125 | Based on your answers, I'll run: |
| 126 | |
| 127 | **Depth:** deep |
| 128 | **Focus:** "authentication" |
| 129 | **Output:** handoff |
| 130 | **Path:** src/ |
| 131 | |
| 132 | Proceed? [Yes / Adjust settings] |
| 133 | ``` |
| 134 | |
| 135 | ### Depths |
| 136 | |
| 137 | | Depth | Time | What it does | |
| 138 | |-------|------|--------------| |
| 139 | | `quick` | ~1 min | tldr-explorer only - fast structure overview | |
| 140 | | `deep` | ~5 min | onboard + tldr-explorer + research-codebase + write doc | |
| 141 | | `architecture` | ~3 min | tldr arch + call graph + layer mapping + circular dep detection | |
| 142 | |
| 143 | ### Options |
| 144 | |
| 145 | | Option | Description | Example | |
| 146 | |--------|-------------|---------| |
| 147 | | `--focus "area"` | Focus on specific area | `--focus "auth"`, `--focus "api"` | |
| 148 | | `--output handoff` | Create handoff for next agent | `--output handoff` | |
| 149 | | `--output doc` | Create documentation file | `--output doc` | |
| 150 | | `--entry "func"` | Start from specific entry point | `--entry "main"`, `--entry "process_request"` | |
| 151 | |
| 152 | ## Examples |
| 153 | |
| 154 | ```bash |
| 155 | # Quick structure overview |
| 156 | /explore quick |
| 157 | |
| 158 | # Deep exploration focused on auth |
| 159 | /explore deep --focus "auth" --output doc |
| 160 | |
| 161 | # Architecture analysis from specific entry |
| 162 | /explore architecture --entry "cli" --output handoff |
| 163 | |
| 164 | # Quick focuse |
People who liked this also viewed
6 picksType
- lark-drive飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sSkillsJul 2026
- lark-sharedUse for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handlingSkillsJul 2026
- lark-whiteboard飞书画板：查询和编辑飞书云文档中的画板。支持导出画板为预览图片、导出原始节点结构、使用多种格式更新画板内容。 当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill。不负责：飞书云文档内容编辑（lark-doc）、文档内嵌电子表格/Base（lark-sheets / lark-base）。SkillsJul 2026
- lark-task飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。SkillsJul 2026
- lark-attendance飞书考勤打卡：查询自己的考勤打卡记录SkillsJul 2026
- lark-apps妙搭（Spark/Miaoda）应用开发与托管：应用创建、本地全栈开发、云端生成迭代、创意设计（UI mockup / 可交互原型 / 线框图 / 落地页 / 仪表盘 / 幻灯片 deck / 视觉探索）、AI相关能力和飞书平台能力或者其他外部能力集成、日志/Trace/监控指标/PV/UV 查询、环境变量管理、应用角色与成员管理、自动化触发器（定时/记录变更/Webhook/飞书审批）。当用户要SkillsJul 2026
