From a90bcf749d277a4d81dfa0a162493c2860e68f05 Mon Sep 17 00:00:00 2001 From: "N. Taylor Mullen" Date: Mon, 19 Jan 2026 16:15:20 -0800 Subject: [PATCH] feat: add /introspect slash command (#17048) --- .gemini/commands/introspect.toml | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 .gemini/commands/introspect.toml diff --git a/.gemini/commands/introspect.toml b/.gemini/commands/introspect.toml new file mode 100644 index 0000000000..8fb03fa841 --- /dev/null +++ b/.gemini/commands/introspect.toml @@ -0,0 +1,16 @@ +description = "Analyze the influence of system instructions on a specific action." +prompt = """ +# Introspection Task + +Take a step back and analyze your own system instructions and internal logic. +The user is curious about the reasoning behind a specific action or decision you've made. + +**Specific point of interest:** {{args}} + +Please provide a detailed breakdown of: +1. Which parts of your system instructions (global, workspace-specific, or provided via GEMINI.md) influenced this behavior? +2. What was your internal thought process leading up to this action? +3. Are there any ambiguities or conflicting instructions that played a role? + +Your goal is to provide transparency into your underlying logic so the user can potentially improve the instructions in the future. +"""