Open-Sourced Claude Code Skills: A /do Pipeline That Cut Follow-Ups by 80%

A developer who has been using Claude Code in production for several months just open-sourced 15 custom skills on GitHub. The project, my-claude-skills, evolved from getting “Claude writes code that works” to “Claude generates tickets that don’t require three follow-up requests for clarification.”

The /do Command Pipeline

The main entry point is the /do command. It 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. If /verify-dev detects a logical flaw, it automatically creates -fix-N tickets, sends them back to /dev, then verifies again. The same process handles compilation errors and failed functional tests. The result is either a green report or a clear failure status — never a half-failed push.

Measured Results

Based on over 2,000 commits from production tickets, the developer reports:

• 80% fewer follow-up requests compared to base Claude Code
• 60-65% better quality — common issues like “Claude forgot to handle X” or “this breaks the authentication flow” dropped significantly
• Review cycles cut in half

The developer emphasizes these aren’t bogus stats — they’re facts from real usage across 100+ freelance projects.

Who It’s For

Developers using Claude Code for production work who want to reduce ticket ping-pong and enforce quality gates before push.