一键导入
cs-callers
Find all callers of a function. Use when user asks who calls a function, wants to trace call chains, or asks about function usage.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Find all callers of a function. Use when user asks who calls a function, wants to trace call chains, or asks about function usage.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | cs-callers |
| description | Find all callers of a function. Use when user asks who calls a function, wants to trace call chains, or asks about function usage. |
| user-invocable | true |
| argument-hint | <function-name> |
Find all functions that call the given function using the find_callers MCP tool.
Function name: $ARGUMENTS
If no arguments given, ask which function to trace.
Show as a call tree:
handleRequest is called by:
<- routeHandler (src/routes.ts:45)
<- middleware (src/middleware.ts:12)
<- testHandleRequest (tests/routes.test.ts:8)
If no callers found, mention it might be a top-level entry point or unused.
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.