suchuanyi

If you're using BMAD (Breakthrough Method for Agentic AI Development), you know the pain: every story requires running through create → develop → test → review → fix → update status. For an Epic with 8 stories, that's potentially 40+ manual commands.

I wrapped this entire workflow into Claude Code Skills. Now one command delivers a complete Epic:

/bmad-epic-worktree

For a single story: /bmad-story-deliver

It handles: - Development implementation - QA automated testing - Code review - Auto-fix HIGH/MEDIUM issues - Update status to Done

Three modes available: 1. Fast mode - Quick iteration, tests run but failures don't block 2. Safe mode - Git worktree isolation, won't merge if tests fail 3. Batch mode - Deliver entire Epic with one command (my favorite)

For company projects, I recommend splitting the flow: manually review the story design first (since that determines what to build), then let automation handle the rest.

The core idea: automate the repetitive stuff, but keep human oversight where it matters.

I built a virtual pet that lives in your Claude Code status line and reflects your AI usage patterns.

  The pet's energy decays over time (~3 days from full to death), and you feed
  it by consuming tokens through Claude Code. As energy drops, the pet shows
  different expressions: (^_^) when happy, (o_o) when hungry, (u_u) when sick,
  and (x_x) when dead.

  What makes it interesting is the death mechanic - when your pet dies (energy
  hits 0), all your statistics reset to zero and you start completely fresh.
  It's like a gentle reminder of the ephemeral nature of our AI interactions.

  Setup is simple: just add `"command": "npx ccpet@latest"` to your Claude Code
  status line config. The pet persists across sessions and gives you a live view
   of your current session stats (input/output/cached tokens).

  It's written in TypeScript, fully tested, and published to npm. I found it
  surprisingly motivating to keep my "pet" alive while coding!

I built ccshell to solve the constant problem of forgetting shell command syntax. Instead of searching Stack Overflow for "how to batch rename files with timestamps" or "compress videos while maintaining quality", you just describe what you want:

  • ccshell "find all files larger than 100MB"
  • ccshell "convert all HEIC photos to JPEG"
  • ccshell "download all images from a webpage"

  It uses Claude Code CLI with intelligent prompt engineering to:
  - Automatically detect and install the right tools (via brew, etc.)
  - Show real-time progress and execution status
  - Handle complex, long-running tasks
  - Work safely with file operations

  Try it immediately without installation:
  npx ccshell "list all files in the current directory"

  Built for macOS initially, but the approach could work cross-platform. The
  three-tier strategy (local commands → tool installation → custom scripts)
  makes it surprisingly reliable.

  Would love feedback from the community on making shell interfaces more
  accessible!