claude-skills

After a code change, test it end-to-end (bash, browser, or computer use — whichever fits) and then run `/simplify` to review and clean up the changed code. Use to confirm a change works and is tidy before wrapping up.

Create a git commit and push it

Create a git commit

Ask the user for maximum clarifications before acting on a prompt. Use when the user wants to ensure all ambiguity is resolved before work begins.

Write or refresh a README that earns the reader's attention — short, honest, with a real visual. Tailored to the project type.

Greenfield product spec for an empty repo. Clarifies scope, then challenges the idea — checking whether it already exists and whether the pain is real — before writing a concise spec.md.

Create multiple git commits, one per concern, from changes in the working tree, then push them

Create multiple git commits, one per concern, from changes in the working tree

Exhaustively clarify a prompt until 100% confident — asks every question, confirms every assumption. Use for high-stakes or ambiguous tasks where you want zero guesswork before work begins. More aggressive than `clarify`.

Bump dependencies via npm-check-updates. Auto-apply and verify safe upgrades; for major-bump packages enter plan mode with per-package migration steps grounded in actual usage.

Run a comprehensive security review of the entire repository.

Discuss an idea or prompt before acting — provide feedback, propose multiple solutions, and surface trade-offs. Use when the user wants to think through an approach before committing to it.