test

Detect the test framework and generate tests for a completed Mothership story.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/howdycarter/Mothership --skill test-howdycarter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test
Source: https://github.com/howdycarter/Mothership/tree/main/.claude/skills/test
Command: npx skills add https://github.com/howdycarter/Mothership --skill test-howdycarter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing tests for ONE completed story ensures reliable verification of its behavior and guards against regressions as the system evolves.

Core Features & Use Cases

  • Focused testing on a single completed story to validate its expected outcomes.
  • Regression protection by catching changes after story completion.
  • Use Case: After finishing a story, generate and run a focused test suite covering happy paths, edge cases, and error handling.

Quick Start

Run a focused test suite for the specified completed story to verify its behavior.

Frequently Asked Questions about test

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

FAQPage Schema
How do I automate tests for a completed story in CI-CD?

To automate tests for a completed story, this Skill identifies changed files and generates test suites covering happy paths, edge cases, and failure scenarios. It then runs the project's test command to verify behavior and prevent regressions.

What test frameworks are supported when automating story tests?

Story tests support jest, vitest, mocha, and playwright. The Skill detects the active test framework in your project to generate and run appropriate regression tests for completed features.

How do I write regression tests for Mothership stories?

Writing regression tests for Mothership stories involves locating changed files and generating test coverage for expected outcomes. This Skill applies to the Mothership workflow to validate finished stories and mark testing progress.

Does automated story testing cover edge cases and failure scenarios?

Automated story testing covers edge cases and failure scenarios alongside happy paths. By generating a focused test suite for a completed story, it ensures reliable verification of behavior and guards against future regressions.

What's the best way to ensure test coverage after finishing a story?

The best way to ensure test coverage after finishing a story is to run a focused test suite validating its expected outcomes. This involves detecting the test framework, generating tests, and running the project's test command.