Pixel-CLI/pixel / eval/arena/skills/pixel-call-path
pixel-call-path
VerifiedTrace a named code entry to a named destination when the request asks how execution reaches that point; exclude generic explanations, text searches, and edits.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.2 KB |
| agents/openai.yaml | config | 154 B |
SKILL.md
View on GitHub---
name: pixel-call-path
description: Trace a named code entry to a named destination when the request asks how execution reaches that point; exclude generic explanations, text searches, and edits.
---
# Trace a named call path
Use only when the request identifies both endpoints, such as a route handler and a downstream function. If either endpoint is unclear, use native source search.
Run one query from the repository root. For ambiguous names, a Pixel UID is `<relative-file>#<qualified-name>#<kind>`, where kind is `function` or `method`:
```sh
pixel --metrics off call-path '<entry-uid>' '<destination-uid>' --json .
```
Treat the chain as a navigation lead. Open each source location and confirm every internal call edge; inspect branch conditions when the question needs them. If results are ambiguous or unhelpful, stop querying and use native search/source reading. A missing path is not proof that no source path exists.
Do not run install, build-index, or other maintenance commands to answer. This experiment assumes a prepared graph; call-path may ask Pixel's daemon to ensure it, so if the graph is missing or gets built/updated, stop using Pixel and fall back to native tools.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |