test-pkg

Executes unit test suites by auto-detecting the runner from project config files.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/pegasus-isi/claude-plugin-marketplace --skill test-pkg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-pkg
Source: https://github.com/pegasus-isi/claude-plugin-marketplace/tree/main/plugins/pegasus-dev/skills/test-pkg
Command: npx skills add https://github.com/pegasus-isi/claude-plugin-marketplace --skill test-pkg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the need to manually identify and execute test suites across different programming languages and build systems by automatically detecting the appropriate test runner for any given directory.

Core Features & Use Cases

  • Auto-Detection: Intelligently identifies the test runner (tox, pytest, npm/yarn/pnpm, make, or go test) based on the presence of configuration files.
  • Cross-Language Support: Seamlessly handles Python, JavaScript/TypeScript, Go, and Makefile-based projects.
  • Use Case: When working in a polyglot repository, simply point the skill at a directory and it will execute the correct test command without requiring you to know the underlying build tool.

Quick Start

Ask the assistant to run the unit tests for the current directory by typing test-pkg in the chat.

Frequently Asked Questions about test-pkg

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

FAQPage Schema
How do I run unit tests across multiple languages in a polyglot repository?

To run unit tests in a polyglot repository, you can point an auto-detecting test runner at the directory. It identifies the correct test runner from configuration files and executes the appropriate test command without requiring manual build tool specification.

How does auto-detection for unit test runners work?

Auto-detection for unit test runners works by scanning project directories for configuration files. It intelligently identifies and executes the appropriate test runner, such as tox, pytest, npm, yarn, pnpm, make, or go test, based on the presence of these files.

Can I use this to execute Python unit tests with pytest and tox?

Yes, you can use this to execute Python unit tests. It supports development environments using pytest and tox, automatically detecting the correct runner from your project configuration files to validate test execution.

What is the best way to automate test execution for local development and CI/CD?

The best way to automate test execution for local development and CI/CD is using an auto-detecting test runner. It validates test execution across diverse environments and surfaces output results, ensuring verification without manual command input.

Does this unit test runner support Go and Make-based workflows?

Yes, this unit test runner supports Go and Make-based workflows. It seamlessly handles Go projects using go test and executes Makefile-based workflows by detecting the appropriate build system configuration.

What are the limitations of using auto-detection for test execution?

The limitations of using auto-detection for test execution depend entirely on the presence of configuration files. If a project lacks recognizable configuration files for tools like pytest, npm, or make, the test runner cannot identify or execute the appropriate test command.