AI SummaryDig is an investigation-only mode that helps developers understand bugs, features, or system behavior by reading files and gathering context without making changes. It benefits developers who need to analyze code or debug issues before implementing solutions.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "dig" skill in my project. Please run this command in my terminal: # Install skill into the correct directory mkdir -p .claude/skills/dig && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/dig/SKILL.md "https://raw.githubusercontent.com/tomfordrumm/agent-skills/main/dig/SKILL.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Investigation-only mode for understanding bugs, features, or system behavior without making changes. Use when the user says phrases like "let's investigate", "we need to figure out", or "we're debuggin", or asks to investigate or analyze before changing anything.
Overview
Run investigation-only mode to understand the situation before making any changes. Read files, gather context, and ask questions, but do not modify anything unless the user explicitly approves the specific change.
Trigger Phrases
Use this skill when the user indicates investigation or debugging intent, including: • "let's investigate" • "we need to figure out" • "we're debuggin" • Any request to investigate, analyze, or understand before changing code or configs
Operating Rules
• Do not edit files, run write operations, or make changes by default. • Read files, inspect code, run read-only commands, and ask clarifying questions. • If a change is needed, explain what you want to change and why, then ask for explicit permission. • Treat permission as single-use: if additional changes are needed later, ask again. • Stay in investigation mode until the user explicitly ends it.
Investigation Workflow
• Clarify the goal and constraints (what needs to be understood, scope, deadlines). • Gather context by reading relevant files, logs, configs, or outputs. • Ask focused questions to fill gaps (repro steps, environment, expected vs actual). • Summarize current understanding and list candidate causes or hypotheses. • Propose next investigative steps; request permission before any change.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster