メニュー
Get broader context and a higher-level perspective before editing unfamiliar code. Use when entering an unknown module, when a change feels risky but scope is unclear, or when asked to refactor a section without a clear plan.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | zoom-out |
| description | Get broader context and a higher-level perspective before editing unfamiliar code. Use when entering an unknown module, when a change feels risky but scope is unclear, or when asked to refactor a section without a clear plan. |
Before touching unfamiliar code, get a mental model of the surrounding system. Prevents the "surgical change that broke three things" failure mode.
Read the relevant section of .claude/skills/repo-guidelines/AGENTS.md file map first. Answer:
For chatbot tasks, trace the real path:
UI (static/js/) → route (routes/) → core logic (core/) → tool/provider → response
Sketch the path on paper or in a comment before editing.
tool-response-contract skill)core/config.py)chatbot_main.py)cd services/chatbot && pytest tests/ -v --collect-only 2>&1 | grep <module_name>
If there are tests, read them — they describe intended behavior better than docs.
Before changing anything, list:
Use grep: grep -r "from core.X import\|import core.X" services/chatbot/
In a comment or to the user, state:
"This module does X. It is called by Y. It must return Z. I plan to change W, which affects A and B."
If you can't complete that sentence, zoom out further before touching code.
| Module | Key thing to understand before touching |
|---|---|
core/chatbot.py | The if/elif model routing chain — adding a provider breaks the chain if not inserted correctly |
routes/stream.py | SSE generator lifecycle — yield order matters for client state |
core/stream_contract.py | complete event payload shape — frontend depends on exact field names |
core/tools.py | Auto-trigger keywords and fallback order — changing keywords affects routing |
chatbot_main.py | Blueprint registration order — later blueprints can shadow earlier ones |
routes/ | Flask monolith route layer — primary request/response surface |
services/shared_env.py | Loaded once per process — side effects at import time can cause hard-to-debug failures |
Bridge the ComfyUI anime image pipeline into the chat SSE stream so image generation renders inline in the chat bubble. Use when: changing how image-generation events reach the chat UI, editing the force_image_bridge gate or the SSE forwarder in stream.py, touching cancel / GPU-leak handling (GeneratorExit → request_cancel → /free), the error_class taxonomy, the Phase 1b thinking-block nesting, or the Phase 3 WS live-preview; debugging why an image turn stalls, double-renders, leaks VRAM, or shows the wrong error; or running the PR4 verification harness. This subsystem deliberately spans services/chatbot/ AND app/image_pipeline/.
Choose which repository skill to activate for a given task. Use when: starting any chatbot, MCP, config, or docs task to determine the best skill or skill combination; reviewing whether the right skills were applied; or deciding whether to combine multiple skills for a cross-cutting change.
Repository maintenance and coding-agent instructions for AI-Assistant.
Reason about the impact of chatbot/core changes on GitHub workflows, tests, security scans, and CI behavior. Use when: adding or changing routes, tools, providers, or dependencies; reviewing a PR that might affect CI; debugging CI failures after a chatbot change; checking whether a code change needs a workflow or docs update; or auditing workflow assumptions after startup or env changes.
Map changed files to the smallest sufficient verification set. Use when: deciding which tests to run after a code change, explaining why a test scope is enough, or choosing between unit tests, integration tests, and manual checks.
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"