12 skills (repositories by thoughtbot) · sorted by popularity
Turn the working changes into one or more atomic commits with well-written messages. Use whenever the user runs /git-commit or asks to commit their work, wrap up a feature, or "commit what I have."
The English summary is being prepared. Showing the original description.
Take one new feature slice from idea to reviewed, committed code in a single guided pass — scope it into the smallest shippable slice, build it test-first with strict TDD, review and fix the diff, then commit it. Chains slice → test-driven-development → the built-in /code-review → git-commit. Not for reviewing an existing PR, upgrades, or open-ended design questions.
The English summary is being prepared. Showing the original description.
Socratic code review and refactoring session — whether it's your own code, a teammate's PR, or something you inherited. Leads you to see the issues through questions, names smells and moves precisely, then closes with a concrete plan.
The English summary is being prepared. Showing the original description.
Strict red-green-refactor TDD workflow for implementing features, fixing bugs, or changing behavior in Rails applications. Enforces the discipline of writing a failing test before any production code. Use whenever you want to implement with TDD — whether a new feature, a bugfix, a refactor, or any behavior change.
The English summary is being prepared. Showing the original description.
Pressure-test an assumption, decision, or inherited constraint — Socratic cross-examination that forces you to defend or abandon your position
The English summary is being prepared. Showing the original description.
Walk through the Designer/Developer wrap-up checklist for offboarding a client engagement — conversationally, one item at a time.
The English summary is being prepared. Showing the original description.
Discover how a codebase already handles a specific concern — search broadly, find every instance, and assess consistency. The "how does this app do X?" tool.
The English summary is being prepared. Showing the original description.
Explain what a piece of code does — a specific file, class, or method in close detail, or a user-facing flow as a concise system overview. What it does and why, not whether it's good.
The English summary is being prepared. Showing the original description.
Think out loud about a problem, decision, or approach — Socratic friction to help you find clarity, not sympathy
The English summary is being prepared. Showing the original description.
Turn a feature into well-defined, independently shippable slices — whether it's an epic that needs breaking apart or a single story that needs sharpening into a job story
The English summary is being prepared. Showing the original description.
Write a client update — identify what was done, what's next, and surface risks before they become surprises. End of day, start of day, or end of week.
The English summary is being prepared. Showing the original description.
Prepare to deliver difficult technical news to a client — a conversational prep session before the hard conversation happens
The English summary is being prepared. Showing the original description.