Agent skill

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.

majiayu000github.com/majiayu000GitHub ↗
claude-coderead-onlyMIT
Install
npx skills add majiayu000/claude-skill-registry --skill interrogate-on-changes --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 2 KB
Bundled scripts: none
Allowed tools: Bash(gitdiff:*)Bash(gitshow:*)Bash(ghprdiff:*)
Path: skills/analysis/interrogate-on-changes/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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:** `unstaged` (default), `staged`, `changes` (staged+unstaged), `commit <hash>`, `pr <number>`, or `range <ref1>..<ref2>` - **Mode:** `--quick` (minimal output) or `--skeptical` (extra validation) ## Gather Context Based on target, gather the code diff: ### Target: unstaged (default) ```bash git diff ``` ### Target: staged ```bash git diff --cached ``` ### Target: changes ```bash git diff HEAD ``` ### Target: commit <hash> ```bash git show <hash> ``` ### Target: pr <number> ```bash gh pr diff <number> ``` ### Target: range <ref1>..<ref2> ```bash git diff <ref1>..<ref2> ``` ## Execute Interrogation Apply the three core questions from the workflow to the gathered diff: 1. **What was the hardest decision?** 2. **What alternatives did you reject?** 3. **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

What's inside
Steps it walks through
  1. Workflow
  2. Input: $ARGUMENTS
  3. Gather Context
  4. Target: unstaged (default)
  5. Target: staged
  6. Target: changes
  7. Target: commit <hash>
  8. Target: pr <number>
  9. Target: range <ref1>..<ref2>
  10. Execute Interrogation
  11. Mode Behavior
  12. Output
Ships with 1 file
  • metadata.json
Commands it runs
git diff
git diff --cached
git diff HEAD
git show <hash>
gh pr diff <number>
git diff <ref1>..<ref2>
More from claude-skill-registry
All skills →
descriptive-statisticsSummarizing and visualizing data through measures of center, spread, shape, and position. Covers…Data & Analyticsperplexity-researcher-reasoning-proHighest level of research and reasoning capabilities for complex decision-making with significant…OtherretroBrutally honest engineering retrospective. Analyzes git history for what actually happened — not…Data & AnalyticsanalyzeUniversal multi-perspective analyzer for any topic, file, idea, or decision. Extract key points…Otherarize-prompt-optimizationINVOKE THIS SKILL when optimizing, improving, or debugging LLM prompts using production trace data…Data & Analyticscellxgene-contextGuide for integrating CellxGene Census single-cell data with ENCODE bulk experiments. Use when…Data & Analytics
About this skill
What does the dev:interrogate skill do?

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.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill interrogate-on-changes --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.