skills.rest
pekral
pekralCOMMUNITY
Explore all skills by this author →
Website𝕏@kral_petr_88GitHub

test-like-human

Validate pull requests through realistic user-centered automated testing scenarios.

Updated Aug 15, 2025
Search Tags:#automation#testing#pull request#GitHub#reporting#scenario coverage#user perspective
One-click install
npx skills add https://github.com/pekral/pekral.cz --skill test-like-human
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-like-human
Source: https://github.com/pekral/pekral.cz/tree/main/.claude/skills/test-like-human
Command: npx skills add https://github.com/pekral/pekral.cz --skill test-like-human

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents risky pull requests from reaching users by ensuring changes behave correctly in realistic, user-centered scenarios before merging.

Core Features & Use Cases

  • User-perspective PR validation: Tests a pull request by reading its intent, instructions, and expected outcomes as a real user would experience them.
  • Scenario-driven coverage: Extracts “Testing Recommendations” scenarios from the PR and ensures each scenario is covered by an automated test (writing one first when missing, while treating CI/build checks as already covered).
  • Trustworthy result reporting: Produces clear, human-readable outcomes that emphasize user-visible behavior rather than internal implementation details.

Quick Start

Ask the assistant to run the test-like-human skill for the published pull request, then generate a human-readable report with tested scenarios and an overall readiness verdict from a real user perspective.

Frequently Asked Questions about test-like-human

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

FAQPage Schema
How do I validate a pull request from a real user perspective?▼

To validate a pull request from a real user perspective, you extract the "Testing Recommendations" scenarios and execute each end-to-end using UI, API, backend logic, or CLI methods. This ensures changes behave correctly in realistic scenarios before merging.

What is scenario-driven testing for GitHub pull requests?▼

Scenario-driven testing for GitHub pull requests involves extracting testing recommendations and mapping each scenario to an automated test. If a test is missing, it writes one automatically, while treating existing CI and build checks as already covered.

How do I generate human-readable test reports for PR validation?▼

You generate human-readable test reports for PR validation by emphasizing user-visible behavior over internal implementation details. The process uses a template-only local report format and delegates tracker-facing output to pr-summary.

Does automated user-perspective testing replace standard technical checks?▼

Automated user-perspective testing does not replace standard technical checks, but rather complements them by treating CI and build checks as already covered. It focuses exclusively on exercising end-to-end scenarios extracted from the pull request.

What are the limitations of user-centered PR testing?▼

Limitations of user-centered PR testing include its restriction to pull requests where "Testing Recommendations" explicitly describe scenarios. It does not produce technical logs, and it relies on separate tools like pr-summary for tracker-facing output.

Related Skills

Explore More Software Engineering Skills→
chichexchichex
2

mini-grill

Clarify ambiguous user instructions with up to three targeted questions.

Community
Basic
CivicActionsCivicActions
2

summarize-commits

Synthesize raw git commit logs into structured summaries for PR descriptions.

Official
Intermediate
thuantan2060thuantan2060

bmad-qa-generate-e2e-tests

Generates API and E2E tests for existing features using detected frameworks and patterns.

Community
Intermediate
ewhauserewhauser
106

gh-fix-ci

Diagnose failing GitHub Actions CI checks by parsing PR checks and extracting failure context from logs.

Community
Advanced