test

Execute automated and manual tests and report go/no-go results.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/eumemic/dev-skills --skill test-eumemic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test
Source: https://github.com/eumemic/dev-skills/tree/main/skills/test
Command: npx skills add https://github.com/eumemic/dev-skills --skill test-eumemic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents shipping broken features by ensuring functionality is validated across expected and unexpected conditions.

Core Features & Use Cases

  • Test planning: Identify what to test based on recent changes or context so coverage matches the risk.
  • Systematic execution: Run automated and manual checks across happy paths, edge cases, and error scenarios.
  • No-remnant cleanup & decision reporting: Remove all test artifacts and produce a concise go/no-go report with scenario counts and critical issues.

Quick Start

Use the test skill to verify that the recently implemented feature works end to end, including edge and error cases, while cleaning up any files or logs created during testing.

Frequently Asked Questions about test

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

FAQPage Schema
How do I verify software changes and check release readiness before shipping?

To verify software changes, you validate features across expected and unexpected conditions using automated and manual tests, which produces a go/no-go report confirming release readiness. This ensures functionality behaves correctly before deployment.

What is the best way to plan and execute tests for recently implemented features?

The best way to plan and execute tests is to identify what to test based on recent changes, then run systematic checks across happy paths, edge cases, and error scenarios. This ensures coverage matches the risk profile of the feature.

How does systematic testing handle edge and error scenarios for bug verification?

Systematic testing handles edge and error scenarios by executing targeted checks that validate feature behavior under unexpected conditions. This proves bug fixes work correctly and prevents regressions across critical paths.

Do I need to clean up test artifacts and logs after running integration checks?

Yes, you need to clean up all test artifacts and logs after running integration checks to ensure no remnants affect the environment. This leaves the system clean while producing a concise go/no-go report with scenario coverage.

What limitations exist when relying on automated tests for post-fix confirmation?

Automated tests for post-fix confirmation may miss nuanced edge cases without manual checks, so combining both ensures thorough validation. The approach cleans artifacts but relies on accurate test planning to match true risk.

Can I use this testing approach for both bug verification and release readiness checks?

Yes, you can use this testing approach for bug verification and release readiness checks because it evaluates edge and error scenarios across happy paths. It generates go/no-go reports with critical issues for both contexts.