القائمة
Run BitBot's iterative test workflow (implement → test → fix → commit → push). Use PROACTIVELY during development to ensure quality before committing.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Check bash script syntax without executing. Use before committing bash scripts or when verifying syntax correctness.
Return to normal stop behavior. Use PROACTIVELY after completing all tasks in continuous work mode, when work is committed and tests pass, or when reaching natural stopping point. User can invoke with /claude-allow-stop.
Enable continuous work mode. Use PROACTIVELY when user says "keep working", "don't stop", "finish everything", "complete all tasks". Automatically continues until work is complete. User can invoke with /claude-do-not-stop [reason].
Shared utility script for getting Claude PID and Session ID. Source this in other scripts to access CLAUDE_PID and SESSION_ID variables.
Start fresh with cleared history after task completion. Use PROACTIVELY when user says "done"/"finished", all tasks complete, or starting new unrelated work. Clears all history.
Compact context at natural breakpoints to free tokens and continue working. Use PROACTIVELY at phase boundaries, after commits, or when token usage >150k. Better than random auto-compact. Supports custom compaction prompts.
| name | test-workflow |
| description | Run BitBot's iterative test workflow (implement → test → fix → commit → push). Use PROACTIVELY during development to ensure quality before committing. |
Running BitBot test workflow...
This workflow supports the full development cycle:
Single file check (basic mode):
.claude/skills/test-workflow/scripts/test-workflow.sh <file>
Implementation loop (use this in practice):
Step 1: Fix Line Endings & Check Syntax
Step 2: Run Tests (if test file)
Step 3: Report Status
During iterative development (recommended):
# 1. Implement feature
vim core/util/feature.sh
# 2. Test implementation
.claude/skills/test-workflow/scripts/test-workflow.sh core/util/feature.sh
# 3. Create/update tests
vim dev/tests/test-feature.sh
# 4. Run test suite
.claude/skills/test-workflow/scripts/test-workflow.sh dev/tests/test-feature.sh
# 5. If tests fail, fix and repeat steps 2-4
# 6. Once all tests pass, commit
git add core/util/feature.sh dev/tests/test-feature.sh
git commit -m "Add feature with tests (all passing)"
git push
Quick single-file checks:
# After creating/modifying shell script
.claude/skills/test-workflow/scripts/test-workflow.sh core/util/new-script.sh
# After updating test file
.claude/skills/test-workflow/scripts/test-workflow.sh dev/tests/test-feature.sh
sparc/0-research/TESTING_PROCESS.md - Full testing guidelines.claude/skills/fix-line-endings-check-bash/ - Individual fix+check.claude/skills/run-with-timeout/ - Timeout wrapper