skills.rest
Lia-Creative
Lia-CreativeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

tester

Execute test plans against merged builds and report per-case verdicts with evidence.

1|Updated Jun 30, 2026
Search Tags:#testing#quality assurance#qa#test plan#bug reporting#test execution#verdict
One-click install
npx skills add https://github.com/Lia-Creative/lia-plugins --skill tester-lia-creative
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tester
Source: https://github.com/Lia-Creative/lia-plugins/tree/main/lia-tools/skills/tester
Command: npx skills add https://github.com/Lia-Creative/lia-plugins --skill tester-lia-creative

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Test plans often get executed loosely — cases skipped, verdicts given without evidence, failures never filed — which makes the resulting report untrustworthy as a gate input. This Skill enforces disciplined execution of a written case set against a real build so every case produces a checkable verdict. ## Core Features & Use Cases - Faithful plan execution: Runs every case exactly as written with its concrete inputs, routing improvised ideas to rogue notes instead of altering the plan. - Evidence-backed verdicts: Records pass, fail, or blocked per case by index with observed evidence such as screenshots, values, or log lines, and forbids silent skipping. - Bug filing from failures: Converts each failure into a bug report with steps-to-repeat lifted from the case, deduplicating against the epic's open bugs. - Use Case: After a build merges, hand the case set and build version to this Skill and receive a run report with verdicts, filed bug ticket ids, and named blocked cases for the testing lead's gate decision. ## Quick Start Run the test plan against the current merged build and give me a verdict with evidence for every case.

Frequently Asked Questions about tester

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

FAQPage Schema
How do I execute a test plan against a build?▼

Confirm the build, version, and stage first, then run every case exactly as written with its concrete inputs. Record a pass, fail, or blocked verdict per case by index with the observed evidence attached.

What should a test execution report include?▼

A run report should include the build, version and stage, every case with its verdict and evidence, filed bug ticket ids, blocked cases with reasons, and any rogue candidates noticed but not chased.

How do I file bugs from failed test cases?▼

File each failure with steps-to-repeat taken directly from the case's own steps and inputs, attach the evidence, and cite the case index and criterion. Check the epic's open bugs first and add evidence to an existing ticket if the symptom is already reported.

What happens when a test case cannot be run?▼

Mark the case as blocked and name what blocked it, such as a missing account, unreachable environment, or undeployed dependency. Silently skipping a case is forbidden because the report is read as coverage.

Can I fix bugs found during test execution?▼

No. Fixing anything during the run makes you the builder and disqualifies your own retest. Bugs go back to the lane that built the feature, and fixes are verified in a separate run.

Related Skills

Explore More Software Engineering Skills→
ai-analyst-labai-analyst-lab
16

experiment-brief

Generate experiment briefs with hypothesis, metrics, guardrails, and feasibility estimates.

Official
Advanced
happier-devhappier-dev
1.4k

happier-release-validation-review

Review Happier release-validation worktrees and emit a promotion verdict.

Official
Advanced
citypaulcitypaul
723

find-gaps

Reviews plans, acceptance criteria, and design mocks to surface missing states and unverifiable criteria.

Community
Advanced
outfitter-devoutfitter-dev
2

cli-testing

Run automated Navigator CLI tests with bun and navigator-server.

Official
Intermediate