القائمة
Analyze the impact of changing a function. Shows callers, dependencies, and affected files. Use when user asks what happens if they change or refactor something.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
End-to-end MCP server verification — spawn stdio server, list tools, invoke each one, verify response shape.
Set up a demo session — pick a sample repo, index it, open web UI, prep the narrative.
Run full lint + format + test + frontend build. Pre-commit / pre-release check.
Cut a release — bump version, update CHANGELOG, tag, push, create GitHub release, install local binaries.
Sprint / project status from knowledge graph. Show what's planned, in-progress, done.
Audit MCP tool set — count, descriptions, consolidation candidates, budget compliance.
| name | cs-impact |
| description | Analyze the impact of changing a function. Shows callers, dependencies, and affected files. Use when user asks what happens if they change or refactor something. |
| user-invocable | true |
| argument-hint | <function-name> |
Analyze what would be affected if a function is changed.
Use the impact_analysis MCP tool with function name: $ARGUMENTS
If no arguments given, ask which function to analyze.
Show results grouped:
