Pixel-CLI/pixel / eval/arena/skills/pixel-question-evidence
pixel-question-evidence
VerifiedUse Pixel for bounded evidence when a code question asks for an exact symbol definition or export, or the files affected by a rename. Do not use for unrelated questions.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.6 KB |
| agents/openai.yaml | config | 155 B |
SKILL.md
View on GitHub---
name: pixel-question-evidence
description: Use Pixel for bounded evidence when a code question asks for an exact symbol definition or export, or the files affected by a rename. Do not use for unrelated questions.
---
# Retrieve evidence for code questions
Use one direct Pixel query for an exact lookup; a rename question runs the two queries named below and no more. Do not run `classify` for these recognizable question types.
For an exact definition or export, search the literal identifier with a bounded result count, then read the actual declaration and nearby initializer from the source file. Treat matches as leads; a search snippet or import does not prove what a symbol exports.
```sh
pixel search-content -F '<identifier>' --context 2 --limit 20 .
```
For a rename or cross-file impact question, ask for one shallow upstream impact result, then cross-check literal references so tests, imports, and other textual consumers are not missed by the graph:
```sh
pixel impact '<identifier>' . --direction upstream --depth 1 --no-refresh
pixel search-content -F '<identifier>' --context 1 --limit 100 .
```
Read the relevant source lines for each candidate file and report only imports or calls that the task asks about. A graph path is a lead, not proof of a call edge or a complete inventory. If Pixel is unavailable, the graph is missing or stale, or the results do not answer the question, stop querying Pixel and use a bounded native search and source read. Never refresh or build an index to answer one question. Keep multi-part requests intact and verify every requested fact from source.
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 |