Claude-skill-registry dev:interrogate
Interrogate code changes to surface decisions, alternatives, and confidence levels. Use when user asks to "interrogate", "what decisions", "hardest part", "alternatives", or wants to understand the reasoning behind code changes.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/interrogate-on-changes" ~/.claude/skills/majiayu000-claude-skill-registry-dev-interrogate && rm -rf "$T"
manifest:
skills/data/interrogate-on-changes/SKILL.mdsource content
Interrogate Code Changes
Ask "why" instead of just reading code. Surfaces assumptions, decisions, and confidence levels.
Workflow
@context/workflows/interrogate.md
Input: $ARGUMENTS
Parse arguments to determine:
- Target:
(default),unstaged
,staged
(staged+unstaged),changes
,commit <hash>
, orpr <number>range <ref1>..<ref2> - Mode:
(minimal output) or--quick
(extra validation)--skeptical
Gather Context
Based on target, gather the code diff:
Target: unstaged (default)
git diff
Target: staged
git diff --cached
Target: changes
git diff HEAD
Target: commit <hash>
git show <hash>
Target: pr <number>
gh pr diff <number>
Target: range <ref1>..<ref2>
git diff <ref1>..<ref2>
Execute Interrogation
Apply the three core questions from the workflow to the gathered diff:
- What was the hardest decision?
- What alternatives did you reject?
- What are you least confident about?
Mode Behavior
- Default: Full explanations with confidence levels and structured tables
- --quick: Compact table with brief answers only
- --skeptical: Full output plus follow-up probes:
- "Walk me through the logic step by step"
- "What edge cases could break this?"
- "If this code has a bug, where is it most likely?"
Output
Format output per @context/workflows/interrogate.md#Output-Format based on selected mode.