// Analyze change impact across services before starting implementation. Trigger before modifying runtime, API, or cross-service code — maps changed files to service ownership, outputs the dependency graph between affected services, and lists upstream/downstream sync points that may need coordinated updates.
| name | implementation-strategy |
| description | Analyze change impact across services before starting implementation. Trigger before modifying runtime, API, or cross-service code — maps changed files to service ownership, outputs the dependency graph between affected services, and lists upstream/downstream sync points that may need coordinated updates. |
Analyze changed files to identify affected services, dependencies, and required sync points before implementation.
Before modifying runtime, API, or cross-service code.
git diff file pathsbash .skills/implementation-strategy/scripts/analyze.sh [file1 file2 ...]
Run lint, type-check, and build verification for changed services after code modifications are complete. Trigger after any code change to repos/*/ — auto-detects which services were touched via git diff and runs the appropriate static checks (mypy/flake8 for Python, type-check/lint/build for TypeScript, go vet for Go).
Detect schema, type, or API interface changes and find files in other services that may need synchronized updates. Trigger when modifying files under schemas/, types/, or interfaces/ directories — extracts changed class/type names from the diff and searches all other services for references, outputting a list of potentially stale consumers.
Use tgo-cli (staff) and tgo-widget-cli (visitor) to verify API and service changes at runtime, beyond static lint/build checks. Trigger after modifying backend API endpoints, service logic, chat flow, agent config, knowledge/RAG, workflow, or platform integration — requires local services to be running. Auto-detects changed services from git diff and runs the corresponding CLI smoke tests (system info, CRUD listing, chat e2e).
Start, stop, and check local development services with intelligent minimum-set management. Trigger when services need to be running for functional verification or manual testing — starts the minimum required set (infrastructure + tgo-api + tgo-ai) by default, with optional extras auto-detected from git diff or specified manually. Includes status checking and graceful shutdown.
Check streaming protocol consistency across all producer and consumer services. Trigger when modifying code related to streaming, SSE, WuKongIM, json-render, or MixedStreamParser — lists all files in tgo-ai (producer), tgo-api (relay), tgo-web, tgo-widget-js, and tgo-widget-miniprogram (consumers) that handle the same protocol and may need coordinated updates.
Verify that SQLAlchemy model changes have corresponding Alembic migration files. Trigger when any file under models/*.py or models/**/*.py is modified — checks git diff for model changes and confirms matching alembic/versions/*.py files exist, failing if a service has model changes without a migration.