converter-qa

Validate converter outputs across multiple muscles with 284 assertions.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/fabioc-aloha/tldr --skill converter-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: converter-qa
Source: https://github.com/fabioc-aloha/tldr/tree/main/.github/skills/converter-qa
Command: npx skills add https://github.com/fabioc-aloha/tldr --skill converter-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test harness that validates all converter outputs: md-to-word regression tests, md-to-eml structure validation, shared module unit tests, file size bounds, and output format verification.

Core Features & Use Cases

  • Validates end-to-end conversion quality across md-to-word and md-to-eml pipelines.
  • Verifies shared modules with comprehensive unit tests and enforces size/format constraints.
  • Supports pre-release quality gates by ensuring all registered assertions pass before releases.

Quick Start

Run the QA harness to execute all 284 assertions against the current converter changes.

Frequently Asked Questions about converter-qa

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

FAQPage Schema
How do I run regression tests for markdown to Word and EML conversion pipelines?

Run regression tests for md-to-word and md-to-eml pipelines using an automated QA harness that executes 284 assertions via Node.js. It validates end-to-end conversion quality, shared module unit tests, and file size bounds during development cycles.

What is automated QA testing for converter outputs and when is it needed?

Automated QA testing for converter outputs validates md-to-word and md-to-eml structural changes against regression suites. It is needed during development and pre-release cycles to verify shared module unit tests, file size bounds, and output format compliance before releases.

Can I validate markdown to EML and Word outputs without installing external testing dependencies?

Yes, you can validate converter outputs using a minimal zero-dependency Node.js framework. The QA harness runs 284 assertions to verify md-to-eml structure, md-to-word regression, and shared module unit tests without requiring external testing libraries.

How do I enforce pre-release quality gates for markdown converter changes?

Enforce pre-release quality gates by running the automated QA harness to ensure all 284 registered assertions pass. This verifies md-to-word and md-to-eml conversion outputs, shared modules, and file size constraints before releasing converter updates.

Does the Node.js QA harness support file size bounds and output format verification?

Yes, the Node.js QA harness supports file size bounds and output format verification. It enforces size constraints and validates md-to-word and md-to-eml output formats alongside shared module unit tests within its 284 assertion suite.

Why does my markdown to Word converter output fail shared module unit tests?

Markdown to Word converter outputs fail shared module unit tests when code changes introduce regressions detected by the QA harness. Running the 284 assertions verifies shared module integrity, output formats, and file size bounds to isolate failing converter logic.