antonbabenko/agent-plugins / plugins/code-intelligence/skills/code-intelligence
code-intelligence
VerifiedUse when navigating or refactoring code with a language server - choosing between semantic (LSP), exact-text (rg), and fuzzy/semantic search; anchoring LSP calls by position; gating degraded results; and disclosing tool substitutions, in any language.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.2 KB |
| references/degradation-and-disclosure.md | markdown | 2.5 KB |
| references/lsp-calls.md | markdown | 2.4 KB |
| references/tool-precedence.md | markdown | 2.6 KB |
references/degradation-and-disclosure.md
View on GitHub# Degradation and Disclosure
What to prove before falling back, how to announce a fallback, and how to
prove a tool is really missing.
## Degradation Gate
First separate two cases:
- **No LSP at all**: the host exposes no language-server tool, or the server
will not start. This is genuine unavailability - the gate does not apply.
Disclose on the first line (see Disclosure Format) and use text search.
- **LSP callable, position-anchored call returns empty**: a degraded or
unindexed workspace can legitimately do this. Do not conclude "unavailable" -
run the gate.
Gate (second case only). Pass ALL three before claiming "LSP degraded, using
text search":
1. `documentSymbol` on an in-scope file returns symbols. The server is
responsive. This proves responsiveness ONLY, not complete reference
coverage.
2. The failing call was position-anchored, not symbol-name-only.
3. That anchored call still returned empty after a cold-start retry.
All three pass -> a disclosed text fallback is warranted. Any fails -> fix the
call or the setup; do not fall back yet.
Distinguish: a name-only call returning empty is a usage defect (gate fails at
2). A position-anchored call on a responsive server returning empty is genuine
degradation (gate passes).
## Disclosure Format
State any tool substitution OR omission on the FIRST line of the response:
`Intended: <tool>. Actual: <tool>. Reason: <why>. Impact: <completeness/confidence>.`
- Covers substitution (used a different tool) AND omission (skipped a step or
scope).
- First line, same response. A later closing summary is a rule violation - the
reader must see the caveat before the conclusion.
- One line, factual, no hedging. The impact clause states what confidence is
lost (e.g. "text matches only, may include comments/strings").
## Anti-Phantom-Shim Proof
Do not claim a tool is shimmed, aliased, replaced, or missing without proof.
Verify before asserting:
1. `type -a <tool>` - resolve what actually runs.
2. `ls -l <resolved-path>` - confirm the binary exists and is executable.
3. `<tool> --version` - confirm it prints the expected banner.
If it prints the expected version, the tool is real - investigate the
execution context (sandbox, PATH, shell) before any fallback. An unproven
"tool is missing" claim followed by a fallback is a verification failure, not
a sanctioned substitution.
If genuinely absent or aliased: prefer the LSP for semantic tasks; for exact
text use the host-approved text search; `git grep` / `grep` only as an
explicitly disclosed last resort, never the default substitute.
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: 321k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 321k | 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: 321k | 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: 321k | Updated | Claude CodeCodex | Verified | Install |