manual-testing

Orchestrate automated checks and manual QA for software changes.

5|2|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/petekp/agent-skills --skill manual-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manual-testing
Source: https://github.com/petekp/agent-skills/tree/main/skills/manual-testing
Command: npx skills add https://github.com/petekp/agent-skills --skill manual-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the verification workflow by guiding teams through automated checks and prompting human verification only when necessary.

Core Features & Use Cases

  • Automated verifications: compile/build checks, tests, linting, API responses, and file content validations.
  • Structured workflow: analyze context, classify steps, execute automated verifications, and collect user feedback.
  • On-demand human verification: prompts for outcomes when automatic checks cannot cover an edge case or validation requirement.

Quick Start

Describe the current feature to test and run the automated verifications, reporting any failures.

Frequently Asked Questions about manual-testing

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

FAQPage Schema
How do I combine automated tests with manual QA verification for software changes?

Combining automated tests with manual QA verification requires orchestrating build checks, linting, and test runners, then prompting for human validation only when automatic checks cannot cover edge cases. This structured workflow classifies steps, executes automated verifications, and collects user feedback to validate feature rollouts and bug fixes.

What is a manual testing workflow for features that lack sufficient automated test coverage?

A manual testing workflow for features with insufficient automated test coverage analyzes context, classifies execution steps, runs automated verifications like compile checks and API responses, and prompts on-demand human verification to validate user-facing requirements and collect structured feedback outcomes.

How do I verify API responses and file content during a feature rollout?

To verify API responses and file content during a feature rollout, you run automated verifications through integrated test runners and CLI tooling. The workflow classifies these checks, executes them against build scripts, and reports any validation failures for review.

Does this testing strategy work with existing build scripts and lints?

Yes, this testing strategy integrates directly with existing build scripts, test runners, lints, and CLI tooling. It orchestrates these automated verifications in a structured workflow and exports results, prompting human checks only when automated checks are insufficient for user-facing validation.

When should I use manual verification instead of fully automated testing?

You should use manual verification instead of fully automated testing when automatic checks cannot cover an edge case or specific user-facing validation requirement. The workflow prompts for human outcomes only when necessary, ensuring comprehensive QA for complex software changes where automated tests fall short.