ss-bs-discovering-testing

Analyze repository test layout and draft a TESTING.md strategy.

Updated May 19, 2026
One-click install
npx skills add https://github.com/Emrebener/Sublime-Skills --skill ss-bs-discovering-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ss-bs-discovering-testing
Source: https://github.com/Emrebener/Sublime-Skills/tree/main/skills/project-bootstrap/ss-bs-discovering-testing
Command: npx skills add https://github.com/Emrebener/Sublime-Skills --skill ss-bs-discovering-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns an agent’s scattered understanding of how a codebase tests into a concrete, user-approved TESTING.md that documents the intended testing strategy and conventions.

Core Features & Use Cases

  • Scans your repository for real testing signals: detects test directories, runner configuration files, test naming patterns, CI test commands, coverage tooling, coverage gates, mocking frameworks, and fixture/factory conventions.
  • Runs an opinionated, evidence-cited diagnose pass (optional): when enabled, it surfaces up to a small set of testing-strategy gaps and smells, grounded in specific file paths and counts.
  • Creates or extends documentation safely: drafts docs for a create/replace flow, merges for extend, performs drift checks in audit mode, and writes atomically only after user approval.
  • Guides new projects without tests: if it finds too few tests, it switches to a starter-strategy Q&A instead of a scan-and-confirm workflow.

Quick Start

Ask your agent to run the ss-bs-discovering-testing skill inline via ss-bs-bootstrapping-project to draft docs/TESTING.md from the current repository.

Frequently Asked Questions about ss-bs-discovering-testing

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

FAQPage Schema
How do I generate a TESTING.md document for my repository?

It scans your repository for test directories, runner configuration, CI commands, and coverage setup, then drafts an actionable TESTING.md document after explicit user approval.

What is the best way to document an existing testing strategy and conventions?

The best way is to scan test layout, mocking style, and fixture conventions, optionally run an evidence-cited diagnose pass for gaps, and write an atomically updated TESTING artifact.

Can I create testing documentation for a new project with no existing tests?

Yes, for new projects with minimal or no existing tests it switches to a starter-strategy interactive Q&A instead of a scan-and-confirm workflow.

Does this testing documentation tool support continuous integration coverage gates?

Yes, it detects CI test commands, coverage tooling, and coverage gates within the repository configuration to accurately document your testing strategy.

How do I audit my repository for testing strategy drift?

You audit for drift by running the Skill in audit mode, which performs drift checks against existing documentation and surfaces gaps grounded in specific file paths and counts.

When should I not use an automated repository scan for testing documentation?

You should avoid an automated repository scan when your project has too few existing tests, as the workflow switches to a guided starter-strategy Q&A instead.