SPipe Test Writing Skill

Author Simple BDD specs with describe, context, it, expect, and matchers.

Updated May 27, 2026
One-click install
npx skills add https://github.com/ormastes/Spipe --skill spipe-test-writing-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: SPipe Test Writing Skill
Source: https://github.com/ormastes/Spipe/tree/main/doc/00_llm_process/skill_command/skills/claude/lib/spipe
Command: npx skills add https://github.com/ormastes/Spipe --skill spipe-test-writing-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing reliable test specifications for the Simple BDD framework can be slow and inconsistent, especially when teams need consistent docstrings, matchers, and coverage annotations.

Core Features & Use Cases

  • Baked-in BDD primitives: Provides a consistent way to write specs using built-in describe/context/it/expect without imports.
  • Documentation-first spec structure: Enforces a required module-level docstring format and supports docstring-driven doc generation.
  • Coverage guardrails for system tests: Requires # @cover annotations for system tests so the test runner can verify layer coverage.

Use it when you need to create or standardize feature specs (including docstrings and matcher usage) for a Simple project, such as adding a new calculator feature with scenarios and assertions that document behavior.

Quick Start

Use the SPipe test writing instructions to create your spec file at test/my_spec.spl and then run bin/simple test test/my_spec.spl.

Frequently Asked Questions about SPipe Test Writing Skill

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

FAQPage Schema
How do I write Simple BDD specs with built-in matchers and contexts?

Writing Simple BDD specs involves using built-in describe, context, it, and expect blocks without imports, applying supported matchers and shared contexts to structure repeatable scenario authoring and assertions.

What is the required module-level docstring format for Simple BDD test files?

The required module-level docstring format for Simple BDD test files enforces a documentation-first spec structure, enabling consistent doc generation and standardized feature behavior documentation across your test suite.

How do I enforce test coverage for system tests in a Simple project?

To enforce test coverage for system tests in a Simple project, add optional # @cover annotations to your spec file, allowing the test runner to verify layer coverage during execution.

Can I use hooks and fixtures when authoring Simple BDD scenarios?

Yes, you can use hooks and fixtures when authoring Simple BDD scenarios to establish repeatable contexts and preconditions, ensuring consistent system test coverage and behavior-driven spec execution.

Does the Simple BDD framework require external imports for describe and expect blocks?

No, the Simple BDD framework provides baked-in primitives, meaning you use describe, context, it, expect, and supported matchers directly without needing any external or internal module imports.