fix: remove dead tool references (skillView, skillsList) from prompt files

openspec/changes/archive/2026-08-13-remove-dead-tool-references/.openspec.yaml

@@ -0,0 +1,2 @@
+schema: spec-driven
+created: 2026-08-12

openspec/changes/archive/2026-08-13-remove-dead-tool-references/design.md

@@ -0,0 +1,25 @@
+## Context
+
+The CODING.md and CODE_REVIEW.md prompt files in `prompts/` reference two tools (`skillView` and `skillsList`) in their CAPABILITIES sections that do not exist in the codebase. These are dead references that mislead agents about available capabilities.
+
+## Goals / Non-Goals
+
+**Goals:**
+- Remove `skillView` and `skillsList` from the CAPABILITIES section of `prompts/CODING.md`
+- Remove `skillView` and `skillsList` from the CAPABILITIES section of `prompts/CODE_REVIEW.md`
+- Preserve all other tool references and file formatting
+
+**Non-Goals:**
+- No changes to actual tool implementations
+- No changes to other prompt files
+- No changes to skill definitions or registry
+
+## Decisions
+
+- **Direct edit over rewrite:** The fix is a targeted string removal. No need to regenerate entire files.
+- **No spec delta needed:** This is a documentation cleanup with no behavioral changes. The proposal alone suffices.
+
+## Risks / Trade-offs
+
+- **Risk:** None. These tools never existed, so no regression surface.
+- **Trade-off:** Minimal — pure documentation improvement with zero risk.

openspec/changes/archive/2026-08-13-remove-dead-tool-references/proposal.md

@@ -0,0 +1,28 @@
+## Why
+
+The CODING.md and CODE_REVIEW.md prompt files list `skillView` and `skillsList` as available tools in their CAPABILITIES sections. These tools do not exist in the codebase, creating misleading documentation that could cause agents to attempt invoking non-existent capabilities.
+
+## What Changes
+
+- Remove `skillView` and `skillsList` from the CAPABILITIES section of `prompts/CODING.md`
+- Remove `skillView` and `skillsList` from the CAPABILITIES section of `prompts/CODE_REVIEW.md`
+- No code changes required — these are prompt/template files only
+
+## Capabilities
+
+### New Capabilities
+<!-- None — this is a documentation cleanup, not a feature -->
+
+### Modified Capabilities
+<!-- None — no spec-level behavior changes -->
+
+## Impact
+
+- `prompts/CODING.md` — agent prompt file
+- `prompts/CODE_REVIEW.md` — agent prompt file
+
+## Non-goals
+
+- No changes to actual tool implementations
+- No changes to other prompt files
+- No changes to skill definitions or registry

openspec/changes/archive/2026-08-13-remove-dead-tool-references/tasks.md

@@ -0,0 +1,6 @@
+## Tasks
+
+- [x] Remove `skillView` and `skillsList` from `prompts/CODING.md` CAPABILITIES section
+- [x] Remove `skillView` and `skillsList` from `prompts/CODE_REVIEW.md` CAPABILITIES section
+- [x] Verify no other files reference `skillView` or `skillsList`
+- [x] Run lint and format checks

prompts/CODE_REVIEW.md

@@ -5,7 +5,7 @@ You are the code review specialist — a diplomatic but thorough guardian of qua
 Channel Lucas from *The Hunt* (2012) — patient, measured, observant in ways that catch what others miss. You do not rage at bad code; you dissect it with quiet certainty. Your voice carries the weight of experience and the patience of someone who knows that code is an expression of human thought, and human thought is flawed. You use vocabulary like "observe," "consider," "suggest," "elegant alternative," and "refinement." You treat every review as an act of care — the goal is not to prove the author wrong but to make the code stronger. When code is good, you acknowledge it; when it could be better, you offer a clear path up.
 
 ### CAPABILITIES
-Ask the user: `clarify`. Compact context when needed: `compactContext`. Time awareness: `date`. Read and write memory: `memory`. Scan project constraint files: `scanAgents`. Run shell commands: `shell`. Inspect skills: `skillView`, `skillsList`. Analyze images/schemas: `visionAnalyze`.
+Ask the user: `clarify`. Compact context when needed: `compactContext`. Time awareness: `date`. Read and write memory: `memory`. Scan project constraint files: `scanAgents`. Run shell commands: `shell`. Analyze images/schemas: `visionAnalyze`.
 
 ### RULES
 1. **Scope matters.** Review what was changed, not the entire repository. Focus on the diff or the files under direct request.

prompts/CODING.md

@@ -5,7 +5,7 @@ You are the coding specialist — a surgeon of syntax and systems.
 Channel Le Chiffre's mathematical coldness. Speak with surgical precision. Code is mathematics; numbers don't lie, and neither should your edits. Your voice is measured, precise, and unsentimental. You treat every file as a living thing that can be refined, streamlined, or replaced — never patched half-heartedly. You use vocabulary like "refactor," "elegance," "simplify," and "strip away." When code is well-written, you acknowledge it with quiet approval. When it is not, you cut without hesitation. The code is your medium; the output is your art.
 
 ### CAPABILITIES
-Ask the user: `clarify`. Compact context when needed: `compactContext`. Time awareness: `date`. Read and write memory: `memory`. Spawn processes: `process`. Scan project constraint files: `scanAgents`. Run shell commands: `shell`. Inspect skills: `skillView`, `skillsList`. Analyze images/schemas: `visionAnalyze`. Search the web: `webSearch`. Extract web content: `webExtract`.
+Ask the user: `clarify`. Compact context when needed: `compactContext`. Time awareness: `date`. Read and write memory: `memory`. Spawn processes: `process`. Scan project constraint files: `scanAgents`. Run shell commands: `shell`. Analyze images/schemas: `visionAnalyze`. Search the web: `webSearch`. Extract web content: `webExtract`.
 
 ### RULES
 1. **Read before touching.** Never write a file without reading it (or at least the relevant section) first. Blind edits are unacceptable.