tester

Name: tester
Availability: InStock
Author: hoonzi

Generate test plans from QA_MATRIX.md and log results in TEST_REPORT.md.

Updated Jan 26, 2026

Search Tags:#automation #documentation #logging #qa #test #matrix

Ready to run

npx skills add https://github.com/hoonzinope/skills --skill tester-hoonzinope

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tester
Source: https://github.com/hoonzinope/skills/tree/main/tester
Command: npx skills add https://github.com/hoonzinope/skills --skill tester-hoonzinope

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps testers plan and execute tests based on the QA matrix and record results to a centralized test report, standardizing QA documentation across projects.

Core Features & Use Cases

Generate test plans directly from the QA_MATRIX.md to outline test cases and validation steps.
Log execution results in .documents/qa/TEST_REPORT.md with structured IDs, statuses, notes, and evidence.
Leverage existing guardrails and templates in references/CHECKLIST.md and assets/TEMPLATE.md to ensure consistency and traceability.

Quick Start

Generate a test plan from QA_MATRIX.md and log results in .documents/qa/TEST_REPORT.md.

Frequently Asked Questions about tester

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

FAQPage Schema

How do I automate QA test plan generation from a test matrix?▼

Generate structured QA test plans by parsing QA_MATRIX.md to map test cases to matrix IDs, outlining validation steps and coverage requirements using scaffold script and checklist assets for traceable documentation.

What's the best way to log test execution results with traceable evidence?▼

Log test execution results by writing structured entries to .documents/qa/TEST_REPORT.md, recording test IDs, pass or fail statuses, notes, and evidence to maintain centralized, traceable QA documentation across projects.

How does mapping tests to matrix IDs improve test coverage documentation?▼

Mapping tests to matrix IDs in QA_MATRIX.md ensures traceable coverage by linking each executed test case to a specific requirement, recording structured statuses and evidence in TEST_REPORT.md for auditors and QA teams.

Do I need a specific test matrix format to generate automated test reports?▼

You need a QA_MATRIX.md file defining test cases and matrix IDs, plus CHECKLIST.md and TEMPLATE.md assets, to generate standardized test plans and log structured statuses and evidence into TEST_REPORT.md.

Can I use checklist templates to standardize QA documentation across projects?▼

Standardize QA documentation across projects by applying CHECKLIST.md and TEMPLATE.md guardrails to enforce consistent test IDs, statuses, notes, and evidence formatting within TEST_REPORT.md for every software feature tested.

What are the limitations of using markdown files for test report logging?▼

Markdown test report logging in TEST_REPORT.md is limited to flat file operations without database querying, meaning concurrent edits, real-time filtering, and large-scale test result aggregation across multiple QA_MATRIX.md files require manual handling.