test

Run project test suites and summarize failures with exit status and error messages.

8|Updated May 18, 2026

Search Tags:#testing #debugging #qa #failure analysis #ci #tests

Ready to run

npx skills add https://github.com/lalulali/vespyr --skill test-lalulali

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test
Source: https://github.com/lalulali/vespyr/tree/main/.agents/skills/test
Command: npx skills add https://github.com/lalulali/vespyr --skill test-lalulali

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill gives you quick feedback on whether recent changes broke the project’s tests, without loading a heavier quality-assurance workflow.

Core Features & Use Cases

Test Command Detection: Finds the appropriate test command from common project files such as package.json, Makefile, or language-specific defaults.
Test Execution Summary: Runs the suite and returns a concise report with exit code, pass/fail counts, and the first important failure messages.
Use Case: Use it when you want a fast check after editing code, before opening a pull request, or when diagnosing a failing build.

Quick Start

Run the project’s tests and summarize any failures.

Frequently Asked Questions about test

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

FAQPage Schema

How do I run project tests and quickly summarize failure messages after editing code?▼

To run project tests and summarize failure messages, this Skill detects your repository's test command from files like package.json or Makefile, executes the suite, and reports the exit code, pass/fail counts, and truncated error messages for rapid feedback.

Can I use this for pre-commit checks across JavaScript, Python, Go, and Rust projects?▼

Yes, you can use this for pre-commit checks across JavaScript, Python, Go, Rust, and Make-based projects. It detects language-specific defaults to run the suite and deliver a concise report on failing tests without a heavier quality-assurance workflow.

What's the best way to get fast test results when diagnosing a failing build?▼

The best way to get fast test results when diagnosing a failing build is to trigger this Skill. It runs your project test suites and returns a concise summary of the exit status and the first important failure messages, bypassing heavier QA workflows.

Does this test runner support automatic detection of the test command from a Makefile?▼

Yes, this test runner supports automatic detection of the test command from a Makefile, as well as package.json and language-specific defaults. It uses these files to execute your tests and report pass/fail counts and error messages.

Why does the test summary only show truncated error messages instead of full logs?▼

The test summary shows truncated error messages to provide rapid feedback on failing tests. By focusing on the exit status, pass/fail counts, and the first important failure messages, it keeps the output concise for quick debugging sessions without overwhelming logs.

Do I need any external dependencies to run tests and summarize failures with this tool?▼

No, you do not need any external dependencies to run tests and summarize failures. It operates without dependencies by reading existing project files like Makefile or package.json to detect the test command and execute the suite directly.