test-workflow

Automate BitBot test-workflow execution for Bash scripts with syntax checks and tests.

3|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ManuelKugelmann/BitBot --skill test-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-workflow
Source: https://github.com/ManuelKugelmann/BitBot/tree/main/.claude/skills/test-workflow
Command: npx skills add https://github.com/ManuelKugelmann/BitBot --skill test-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates BitBot's iterative development workflow, guiding you from implementation through testing, refinement, and ready-to-commit state, reducing manual steps and human error.

Core Features & Use Cases

  • Automated workflow steps: Fix line endings, check syntax, and run tests with a safe timeout.
  • Guided iteration: Encourages a loop of implement → test → fix → commit → push.
  • Quicks Start to CI readiness: Provides a repeatable pattern to accelerate code quality before committing.

Quick Start

Use the test-workflow script to validate your implementation file: .claude/skills/test-workflow/scripts/test-workflow.sh <file>

Implementation loop (practical usage):

  1. Make changes to the implementation file
  2. Run the workflow on the implementation file
  3. If tests fail, fix issues and re-run
  4. Once tests pass, commit and push

Frequently Asked Questions about test-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Bash script testing in my development workflow?

Automate Bash script testing by running the test-workflow script on your implementation file, which validates syntax, executes tests with a 60-second timeout, and reports results. This enforces a repeatable cycle of code changes, validation, and commit readiness without manual steps.

What does test-workflow do with line endings and syntax checks?

Test-workflow normalizes line endings from CRLF to LF, validates Bash syntax to catch errors before execution, then runs tests with a safe timeout. This prevents common issues and ensures scripts are ready for CI before committing.

Can I use test-workflow to guide my implementation and testing loop?

Yes. Test-workflow guides an iterative cycle: make changes to your implementation file, run the workflow to validate, fix issues if tests fail, then repeat until tests pass and you're ready to commit and push.

Does test-workflow work with scripts in specific directories?

Test-workflow applies to Bash scripts in the core/util and dev/tests directories. It's designed for BitBot's workflow, normalizing line endings, checking syntax, and running tests on implementation and test files in those locations.

What happens if tests timeout during test-workflow execution?

Test-workflow enforces a 60-second timeout on test runs to prevent hanging processes. If tests exceed this limit, the workflow reports the timeout, allowing you to identify slow or blocked tests and fix them before the next iteration.

Why normalize line endings before running tests?

Line ending normalization (CRLF to LF) prevents cross-platform script execution failures and ensures consistent behavior in CI environments. Test-workflow handles this automatically so line-ending differences don't cause unexpected test failures.