find_callers
openbooklet.com/s/findcallersopenbooklet.com/s/[email protected]GET /api/v1/skills/findcallers"Who calls this function/class?" â incoming call-graph edges. Use for impact ("what breaks if I change X") and to walk a bug up into its caller. Returns a compact list (name, file:line); call read for the bodies you care about.
LSP-compatible "go to definition" using the runtime's selected semantic provider. Use it when you have an exact source position from repository evidence and want the definition target without fanning out through raw grep. It deliberately uses the native LSP common denominator: a repository-relative
Static-index semantic route map backed by CodeNib's symbol graph, not a live LSP server. Use it early when a localization request names a symbol, error code, config field, API, or cross-file behavior and you need a compact map of likely endpoint, bridge/factory, provider/value, and type anchors.
Auto-indexed from sysevol-ai/CodeNib
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.