interrogate

Installation
SKILL.md

Interrogate

Think from first principles about what the change is trying to achieve, then interrogate what was built before calling it done.

Target: $ARGUMENTS. Empty means the uncommitted diff (git diff HEAD); a ref means the diff since its merge-base.

Questions

Answer each in a line or two, against the actual diff, before touching anything. When a caller hands over a change record, its purpose line answers the first question.

  1. What is this change for? One sentence, from the user's point of view, without reference to the implementation.
  2. What is unnecessary, over-complicated, or resting on a weak assumption? Challenge each assumption: is it true, and is it needed?
  3. What can be deleted entirely? Files, functions, parameters, options, branches, tests, comments. Apply the deletion test: would removing it lose behaviour or information the user asked for?
  4. What becomes simpler once the deleted pieces are gone? A helper with two callers may now have one; a parameter may now have one value; a layer may now only forward.

Order of preference

Deleting over simplifying. Simplifying over optimizing. Optimizing over automating.

Installs
4
GitHub Stars
1
First Seen
Sep 29, 2026