Перевод: оболочка страницы на русском; тело навыка (SKILL.md) пока на английском — это исходные инструкции агента.

Change Impact

Map git-diff blast radius via project index.

Метаданные навыка

Источник	Встроенный (установлен по умолчанию)
Путь	skills/software-development/change-impact
Версия	1.0.0
Автор	VibeOS
Лицензия	MIT
Платформы	linux, macos, windows
Теги	project, index, diff, impact, blast-radius
Связанные навыки	codebase-navigate, pr-ready, git-local-workflow, requesting-code-review

Справка: полный SKILL.md

к сведению

Ниже полное определение навыка, которое VibeOS загружает при активации. Это инструкции, которые видит агент.

Change Impact Skill

Estimate blast radius of local (or staged) edits using git + the Project Intelligence CLI — no new core tools. Drive everything with terminal.

Do not guess callers from memory; query the index and open hits with read_file.

When to Use

• Before a large commit / PR: “what else breaks?”
• After a refactor of a shared symbol or module
• When triage asks for risk of a branch vs main

Skip when: docs-only / config-only diffs with no code symbols.

Prerequisites

• Inside a git repo with a project root
• Prefer pack applied: vibeos pack apply project-intelligence --apply
• Index present (build if missing / stale)

How to Run

1. List changed paths:

git status --short
git diff --name-only
git diff --cached --name-only
# vs base (optional):
git diff --name-only origin/main...HEAD

Or use the helper (same skill directory):

python3 skills/software-development/change-impact/scripts/list_changed_paths.py
python3 skills/software-development/change-impact/scripts/list_changed_paths.py --base origin/main

2. Refresh index + diagnostics cache:

vibeos project index build
vibeos project diagnostics
vibeos project commands

3. For each important changed file / symbol name, find definitions and likely neighbors:

vibeos project index query <SymbolOrBasename>

Then open top hits with read_file. Use search_files only when the index misses (generated code, non-indexed languages).

4. Summarize for the user / Board comment:

• Paths touched (count + top risk files)
• Symbols queried + key callers/defs (path:line)
• Diagnostics error count (vibeos project diagnostics --show)
• Suggested verification command from vibeos project commands (primary_test)

Quick Reference

Goal	Command
Changed paths	git diff --name-only / helper script
Rebuild index	vibeos project index build
Symbol lookup	vibeos project index query <name>
Checker cache	vibeos project diagnostics
Test/lint cmds	vibeos project commands
Doctor	vibeos doctor --project

Procedure

1. Prefer staged diff when preparing a commit; else working tree; else origin/main...HEAD for a branch summary.
2. Query the index for public symbols you renamed or moved — cite path:line.
3. If diagnostics show new errors in untouched packages, call that out as pre-existing vs introduced (compare to base when possible).
4. Hand off to pr-ready when the user wants a go/no-go gate before PR.

Pitfalls

• Index skips node_modules/, release/, most dot-dirs — vendored hits absent.
• Basename queries can be noisy; prefer exact symbol names from the diff.
• Do not add a core “impact” tool — stay on CLI + terminal + read_file.

Verification

vibeos project index status
vibeos project diagnostics --show
vibeos doctor --project