Help us improve
Share bugs, ideas, or general feedback.
From agent-dashboard
Deep-dive into a codebase question, failure, or architectural concern without making changes
npx claudepluginhub bjornjee/agent-dashboard --plugin agent-dashboardHow this skill is triggered — by the user, by Claude, or both
Slash command
/agent-dashboard:investigateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Investigate a codebase question or concern. **This is a read-only skill — do not modify any files.**
Explains, traces, audits, or explores code in read-only mode without modifying it. Answers questions like 'how does X work' or 'where is Y called' with evidence.
Explores codebase areas: maps files, traces data flows, identifies patterns and dependencies. For 'how does X work', architecture queries, or pre-change analysis.
Guides systematic codebase exploration through collaborative dialogue, starting with clarifying questions before investigating architecture, patterns, and implementation details.
Share bugs, ideas, or general feedback.
Investigate a codebase question or concern. This is a read-only skill — do not modify any files.
Question or concern: $ARGUMENTS
Follow these phases in order. Apply all project rules and conventions that are in your context.
git checkout maingit pull origin mainGate: The investigation scope is clear and bounded.
Use read-only tools only. Do not edit, write, or create any files.
git log --all -S "<term>" to find when relevant code was introduced or changed. Use git blame for context on specific lines.Explore broadly first, then narrow to the relevant areas. Take notes as you go.
Present a structured report to the user:
/fix to address the null check at src/auth.py:42", "run /refactor to extract the retry logic into a shared utility").Gate: The user has received a clear, actionable report. No files were modified.