mcpbeat

Bats Testing Patterns

dokhacgiakhoa/bats-testing-patterns

Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.

3k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
505
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill bats-testing-patterns

What comes with it

11 705 bytes besides the instruction
sub-skills/implementation-playbook.md

The instruction itself

7 sections, as written by the author

Bats Testing Patterns

Comprehensive guidance for writing comprehensive unit tests for shell scripts using Bats (Bash Automated Testing System), including test patterns, fixtures, and best practices for production-grade shell testing.

Use this skill when

  • Writing unit tests for shell scripts
  • Implementing TDD for scripts
  • Setting up automated testing in CI/CD pipelines
  • Testing edge cases and error conditions
  • Validating behavior across shell environments

Do not use this skill when

  • The project does not use shell scripts
  • You need integration tests beyond shell behavior
  • The goal is only linting or formatting

Instructions

  • Confirm shell dialects and supported environments.
  • Set up a test structure with helpers and fixtures.
  • Write tests for exit codes, output, and side effects.
  • Add setup/teardown and run tests in CI.
  • If detailed examples are required, open resources/implementation-playbook.md.

Resources

  • resources/implementation-playbook.md for detailed patterns and examples.

🧠 Knowledge Modules (Fractal Skills)

1. implementation-playbook

How to use it

Copy the folder

Take dokhacgiakhoa/bats-testing-patterns from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.