automate-tests

Name: automate-tests
Availability: InStock
Author: NESNILNEHC

Identify and execute repository test commands from documentation and CI manifests.

7|3|Updated Jan 23, 2026

Search Tags:#automation #testing #safety #test #ci #reproducible

Ready to run

npx skills add https://github.com/nesnilnehc/ai-cortex --skill automate-tests

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: automate-tests
Source: https://github.com/nesnilnehc/ai-cortex/tree/main/skills/automate-tests
Command: npx skills add https://github.com/nesnilnehc/ai-cortex --skill automate-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze and execute the correct test commands for a repository based on evidence from docs, CI configs, and build manifests, with safety guardrails to prevent disruptive actions.

Core Features & Use Cases

Discover a test plan from repository sources (README.md, CI workflows, and build manifests) and identify the primary test entry points.
Choose commands according to mode (fast, ci, full) and stated constraints, ensuring deterministic, safe execution.
Execute tests with explicit user confirmation for installs, network access, or services, and produce a structured, evidence-backed report.
Support multi-stack repositories (e.g., backend/frontend) and provide guidance to re-run individual stacks in a controlled order.

Quick Start

Provide the repository path, select a mode, and confirm constraints to begin running the safest matching tests.

Frequently Asked Questions about automate-tests

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

FAQPage Schema

How do I discover and run the correct test commands for a repository?▼

Repository test discovery analyzes README files, CI workflows, and build manifests to identify primary test entry points. It selects commands based on modes like fast, ci, or full, ensuring deterministic and safe execution.

How can I safely execute tests without triggering unintended installations or network access?▼

Safety guardrails require explicit user confirmation before any installs, network access, or external services are used. This prevents disruptive actions during test runs while providing structured, evidence-backed execution reports.

Does this test automation tool support multi-stack repositories with backend and frontend components?▼

Multi-stack repositories with backend and frontend components are supported. The tool discovers tests from documentation and manifests, providing guidance to re-run individual stacks in a controlled order for safe execution.

What is the best way to generate a reproducible test plan from CI configs and build manifests?▼

Generate a reproducible test plan by extracting evidence from CI configs and build manifests to identify test entry points. The machine-readable output includes evidence, commands, assumptions, execution state, and failure diagnostics.

Why do I need to confirm constraints before running repository tests in a specific mode?▼

Confirming constraints ensures mode-based command selection chooses the safest matching tests for your environment. This prevents unintended side effects and requires confirmation before installs or external services run.