Loading...
Loading...
Found 8 Skills
Analyze your SpecStory AI coding sessions in .specstory/history for yak shaving - when your initial goal got derailed into rabbit holes. Run when user says "analyze my yak shaving", "check for rabbit holes", "how distracted was I", or "yak shave score".
Install groove's Claude Code native shell hooks into .claude/settings.json. Enables deterministic session-end reminders, git activity capture, and managed-path protection.
Query Developer Experience (DX) data via the DX Data MCP server PostgreSQL database. Use this skill when analyzing developer productivity metrics, team performance, PR/code review metrics, deployment frequency, incident data, AI tool adoption, survey responses, DORA metrics, or any engineering analytics. Triggers on questions about DX scores, team comparisons, cycle times, code quality, developer sentiment, AI coding assistant adoption, sprint velocity, or engineering KPIs.
Surfaces relevant instincts during work. Use when starting a task to check if any learned behaviors apply.
Interactively debug source code — set breakpoints, step through execution line by line, inspect live variable state, evaluate expressions against the running program, and navigate the call stack to trace root causes. Use when a program crashes, raises unexpected exceptions, produces wrong output, when you need to understand how execution reached a certain state, or when print-statement debugging isn't revealing enough.
Use codanna MCP tools for semantic code search, call graphs, and impact analysis before grep/find.
Helps users discover and apply shared coding solutions when they ask "has anyone solved this", "search for a fix", "find a workaround", or want proven patterns before debugging from scratch. Uses `npx shareful-ai search` to find relevant shares, compare options, and recommend the best match.
[Utilities] Set coding experience level for tailored explanations