dailybothq/deepworkplan-skill · Archived

write-bats-test

Add or extend a bats-core test for the shell scripts, following the tests/ convention. Use when changing setup.sh or context.sh behavior.

First seen Jun 11, 2026

Installation

$ npx skills add dailybothq/deepworkplan-skill --skill write-bats-test

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dailybothq/deepworkplan-skill.

npx skills add dailybothq/deepworkplan-skill

Browse all from dailybothq/deepworkplan-skill

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 20
License LICENSE
Default branch main
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0
Allowed toolsBash, Read, Grep, Glob, Edit, Write

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,367 B
  • docs SUMMARY.md 160 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 37 installs

SKILL.md

Write Bats Test

Goal

Cover new or changed shell behavior with a bats-core test that matches the existing convention in tests/.

When to use

When setup.sh or skills/deepworkplan/shared/context.sh gains or changes behavior (a new flag, a new detection branch, a new output field).

Steps

  1. Read the existing tests to match style and helpers:

tests/setup-sh.bats, tests/context-sh.bats.

  1. Add @test cases for the new behavior. Use a throwaway HOME/temp dir for

any filesystem effect so the suite never touches the developer's ~/.claude.

  1. Keep assertions on observable contract: emitted JSON fields from

context.sh, created symlink names from setup.sh, exit codes.

  1. Run bats tests/ and iterate until green.

Validation

bats tests/ passes, including the new cases, and the suite leaves no artifacts outside its temp dirs.

Notes

Tests must run on bash 3.2. Prefer testing the public contract (flags, symlink names, JSON keys) over internal implementation so refactors don't churn the suite.