ln-522-manual-tester

Execute bash-based manual test suites and document results for Linear integration.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/0xtaoist/taogate --skill ln-522-manual-tester-0xtaoist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ln-522-manual-tester
Source: https://github.com/0xtaoist/taogate/tree/main/ln-522-manual-tester
Command: npx skills add https://github.com/0xtaoist/taogate --skill ln-522-manual-tester-0xtaoist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual testing of Story ACs is time-consuming and error-prone; this skill provides executable bash scripts saved to tests/manual/ to standardize, repeat, and document per-Story validation.

Core Features & Use Cases

  • Creates reusable manual test suites per Story by organizing executable scripts under tests/manual/{NN}-{story-slug}/
  • Runs tests via a master runner (tests/manual/test-all.sh) and records results in tests/manual/results/
  • Documents outcomes in a Linear-friendly format, linking ACs to pass/fail status and edge cases

Quick Start

Run a full manual test suite by executing the master script to validate a Story's acceptance criteria.

Frequently Asked Questions about ln-522-manual-tester

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

FAQPage Schema
How do I automate manual acceptance testing for Story ACs?▼

Manual acceptance testing for Story ACs is automated using executable bash scripts stored under tests/manual/. The skill generates reusable test suites and records results for status tracking and artifact generation.

What's the best way to document manual test results for Linear integration?▼

Documenting manual test results for Linear integration is achieved by executing bash-based test scripts that link pass/fail statuses and edge cases directly to Story ACs in a Linear-friendly format.

How does the master test runner execute manual test suites?▼

The master runner executes manual test suites by running the tests/manual/test-all.sh script, which validates Story acceptance criteria and saves outcomes into the tests/manual/results/ directory.

Can I use these manual test scripts for both API and UI stories?▼

Manual test scripts apply across both API and UI stories, enabling consistent validation by organizing executable bash files into per-story directories under tests/manual/.

Do I need any special dependencies to run these bash-based manual tests?▼

Bash-based manual tests require no special dependencies, utilizing standard shell scripts to validate Story ACs and generate documentation artifacts.

How are reusable manual test suites organized per story?▼

Reusable manual test suites are organized per story by structuring executable scripts into dedicated directories named tests/manual/{NN}-{story-slug}/ for consistent validation.