spipe

Implements MD5, SHA-1, and SHA-2 family checksums in pure Rust.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SPipe helps you write clear BDD-style test specifications that stay maintainable and automatically produce documentation instead of becoming scattered or undocumented test prose.

Core Features & Use Cases

  • BDD test authoring with built-in describe/context/it/expect constructs and guidance on naming, structure, and single-assertion intent.
  • Docstring-first specification format so generated docs capture feature context, scenarios, and expected behavior.
  • Built-in matcher usage for expressive assertions like equality, containment, and numeric comparisons, aligned with SPipe expectations.

Quick Start

Create a new spec file using the provided SPipe template, then write a describe block with a module-level docstring, and run tests to verify it.

Frequently Asked Questions about spipe

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

FAQPage Schema
How do I generate documentation from BDD test specifications?

You generate documentation from BDD test specifications by using a docstring-first format on describe, context, and it blocks, ensuring your test suite automatically produces maintainable docs instead of scattered prose.

What is the best way to structure BDD specs for regular and slow tests?

The best way to structure BDD specs for regular and slow tests is to apply describe/context/it constructs with module-level docstrings and single-assertion intent, explicitly annotating required system-test coverage for slow or skipped scenarios.

Can I use standard assertion matchers for BDD test writing?

For BDD test writing in this format, you should use built-in SPipe matchers for expressive assertions like equality, containment, and numeric comparisons, aligned with the expected syntax rather than standard assertion libraries.

Does writing BDD specs require module-level docstrings?

Yes, writing BDD specs in this format requires module-level docstrings and placing docstrings on describe, context, and it blocks so the generated documentation accurately captures feature context and scenario behavior.

How do I handle pending and skipped tests in BDD specifications?

You handle pending and skipped tests in BDD specifications by authoring them across the standard describe/context/it structure with appropriate annotations, ensuring required system-test coverage is maintained without losing documentation context.