Stats
Actions
Tags
How this skill is triggered — by the user, by Claude, or both
Slash command
/devblock:startThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. Check `.devblock/devblock-ctl.sh` exists. If not, run install:
Check .devblock/devblock-ctl.sh exists. If not, run install:
bash <plugin-scripts-path>/devblock-ctl.sh install
Find the plugin scripts path by searching ~/.claude/plugins/cache/ for devblock*/scripts/devblock-ctl.sh.
Ask the user (via AskUserQuestion) for:
name | files | tests)Build JSON and call:
bash .devblock/devblock-ctl.sh init '<JSON>'
JSON format:
{
"current": {
"name": "Feature name",
"phase": "red",
"files": ["src/module.ts"],
"tests": ["tests/module.test.ts"],
"test_command": "npm test -- tests/module.test.ts"
},
"queue": []
}
Confirm session started. Begin writing failing tests immediately.
Note: If you need to edit outside the current phase, use
/devblock:skip— it requires a reason and user approval.
npx claudepluginhub nicchia-code/devblock --plugin devblockEnforces strict TDD for features/bugfixes: RED (write failing test), GREEN (minimal passing code), REFACTOR. Auto-detects runners like Jest, Vitest, Playwright, Mocha via package.json.
Enforces a test-first pipeline (red-green-refactor) with mandatory orchestration and adversarial test review. Invoke via /skill-tdd when building new features that need rigorous test coverage.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.