I open-sourced the 15 Claude Code skills I used for +100 projects in freelance
I have been using Claude Code in production for several months. We’ve developed a “/” command chain that has allowed us to move from “Claude writes code that works” to “Claude generates tickets that don’t require three follow-up requests for clarification.”
We’ve just open-sourced them: https://github.com/MisTraleuh/my-claude-skills
The main command is /do. A single command executes a 5-step pipeline: /todo → /dev → /verify-dev → /build → /test → /push
Each step has its own feedback loop (limited to 3 cycles per phase).
Does /verify-dev detect a logical flaw? It automatically creates -fix-N tickets, sends them back to /dev, then verifies again. Same process for compilation errors and failed functional tests. Green report or clear failure status: never a half-failed push.
On our production tickets, we’ve seen about 80% fewer follow-up requests and, most importantly, 60-65% better quality than with the base Claude Code ("Claude forgot to handle X", "this breaks the authentication flow", etc.) and review cycles cut in half
(These aren’t bogus stats... they’re facts based on over 2,000 commits)
Wondering what skills are missing from your daily workflow with Claude Code? Let me give you a few ideas