npx claudepluginhub humansintheloop-dev/humansintheloop-dev-workflow-and-tools --plugin idea-to-codeThis skill uses the workspace's default tool permissions.
When running test scripts or any command that may produce large output (e.g. end-to-end tests, integration tests, build scripts):
Enforces protocol for safe terminal command execution: announce intent, read output, detect errors, poll status, stop on failures. Use for any run_command.
Provides workflow for building production-ready bash scripts with defensive patterns, error handling, logging, Bats testing, and ShellCheck linting. For automation, sysadmin, deployment, and CI/CD scripts.
Debugs bash scripts using set -x, custom PS4 prompts, conditional logging, function tracing, and execution profiling techniques.
Share bugs, ideas, or general feedback.
When running test scripts or any command that may produce large output (e.g. end-to-end tests, integration tests, build scripts):
logs/ directory exists in the project root.gitignore (either logs/ or *.log)Redirect both stdout and stderr to a file under logs/, and run in the background:
./build-and-test-all.sh > logs/build-and-test.log 2>&1
Use run_in_background: true on the Bash tool so you can monitor progress immediately rather than waiting for completion.
Keep commands simple. Avoid compound commands with &&, quoted flag characters, or other complexity that may be rejected by the Bash tool permission system. Run each command as a separate Bash call.
tail -30 logs/build-and-test.log
docker ps --format "table {{.Names}}\t{{.Status}}"
tail or Grep on the log file to find the error:
Grep with pattern="FAILED|error|Exception" path="logs/build-and-test.log" output_mode="content"
TEST-*.xml files rather than parsing log output — they contain full stack tracesThis prevents the Bash tool from truncating output and losing important error details.