Describe the mess, get the fix
Committed to the wrong branch, messed up a rebase, or reset something you shouldn't have? Describe what happened in plain English and get the exact commands to recover safely.
I need help with a git situation. I'll describe what happened in plain English. Give me the exact git commands to fix it. For each command: (1) explain what it does, (2) warn me if it's destructive or rewrites history, (3) suggest a safer alternative if one exists. If my description is ambiguous, ask clarifying questions before giving commands. Never suggest a force push without explicitly flagging the risk. What happened: [describe your git situation here]
Tell your Claw what happened in plain English. It gives you the exact
git commands to fix it, explains what each command does, and flags any
history-rewriting or destructive step before you run it.
Meaningful commit messages from your diff, every time
Your Claw reads the staged diff and writes a commit message that actually describes what changed and why — in your team's format. Easy win, low setup, and a good starter recipe for day-to-day use.
Turn messy Jupyter notebooks into clean, reproducible scripts
Takes a Jupyter notebook with out-of-order cells, hidden state, and spaghetti code, and produces a clean .py script with proper structure, functions, error handling, and documentation. Also strips output for version control.
Turn worry into observations, next steps, and questions
Helps parents track developmental concerns in a structured way (what you observe, when it started, what contexts), and generates questions and next steps for pediatric visits or early intervention pathways.
Real sources, named experts, actual quotes
Deep research that finds primary sources with named individuals, community sentiment from Reddit/HN/X, and news coverage. No summaries of summaries — actual quotes with URLs.