AI Agent Skill HUB

test-running

Run tests according to repository guidelines. Use after linting passes, before staging changes.

9 stars
byaspiers
View on GitHubInstallation ↓

Best use case

test-running is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Run tests according to repository guidelines. Use after linting passes, before staging changes.

Teams using test-running should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/test-running/SKILL.md --create-dirs "https://raw.githubusercontent.com/aspiers/ai-config/main/.agents/skills/test-running/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/test-running/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How test-running Compares

Feature / Agenttest-runningStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Run tests according to repository guidelines. Use after linting passes, before staging changes.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Test Running

Run all appropriate tests according to repository guidelines.

## When to Use This Skill

Use this skill:
- After linting passes
- Before staging changes for commit
- After implementing a feature or bug fix
- When verifying existing functionality still works

## Test Discovery

Run tests according to repository guidelines. Look for test commands in:

1. Repository documentation (`README.md`, `AGENTS.md`, `CLAUDE.md`, etc.)
2. Package configuration (`package.json`, `Makefile`, `pyproject.toml`, `Cargo.toml`, etc.)
3. Standard test patterns for the project type

If no test guidelines are found or they are unclear, ask the user for
clarification.

## Common Test Commands

```bash
# JavaScript/TypeScript
npm test
yarn test
pnpm test

# Python
pytest
python -m pytest
make test

# Other
./bin/test-*
*test*
```

## Testing Process

**CRITICAL REQUIREMENT: 100% test success is MANDATORY.**

For each test command found:

1. Run it
2. If ANY test failures occur, they MUST be fixed
3. If issues can't be fixed immediately, stop and ask the user what to do next
4. Only consider the task complete when ALL tests pass with 100% success rate
   OR the user explicitly gives permission to ignore certain failures

## Important Notes

- "Issues" includes not only test failures, but also noise in test output
  such as warnings which could mask true failures
- Don't proceed until all tests pass or user explicitly allows deferral
- Document any failures clearly with file, test name, and error message

## Output

Report results organized by:

1. **Passing tests**: Summary of what passed
2. **Failing tests**: Each failure with file, test name, and error
3. **Recommendations**: What needs to be fixed

If all tests pass, simply confirm: "All tests passed."

Related Skills

slow-command-running

9
from aspiers/ai-config

Pipe long running commands through tee(1) to allow watching output and repeated analyses without rerunning

xlsx-to-csv

9
from aspiers/ai-config

Convert XLSX spreadsheets (single or multi-sheet) to CSV files you can read and grep. Use whenever you need to process an .xlsx report from Xero, Cryptio, bank exports, or any tool that delivers spreadsheet output.

xero-mcp

9
from aspiers/ai-config

Use the Xero MCP server — obtain/refresh OAuth2 bearer tokens, troubleshoot authentication, and pick up other operational notes for working with Xero MCP tools. Use when Xero MCP tools fail with authentication errors, when the bearer token has expired (tokens last ~30 min), before starting any Xero workflow, or for general guidance on Xero MCP usage.

xero-browser

9
from aspiers/ai-config

General Xero browser automation notes. Use when automating any Xero page with agent-browser — covers non-standard UI patterns, waiting, and dropdown menus.

task-orchestration

9
from aspiers/ai-config

Orchestrate the complete development workflow for implementing sub-tasks from a task list. Use for end-to-end feature implementation with quality controls.

task-implementation

9
from aspiers/ai-config

Implement a single sub-task from a task list. Use when working on feature development with existing task lists.

task-generation

9
from aspiers/ai-config

Generate a detailed task list from a PRP. Use after a PRP is created and ready for implementation planning.

subagent-authoring

9
from aspiers/ai-config

Create subagent definitions for Claude Code and OpenCode that delegate to skills. Use when creating new subagents or refactoring existing ones to follow the delegation pattern.

skill-authoring

9
from aspiers/ai-config

Create and maintain Claude Code skills following Anthropic best practices. Use when building new skills, refactoring existing ones, or ensuring skills follow official guidelines for structure, naming, progressive disclosure, and testing.

safe-rm

9
from aspiers/ai-config

Safely delete files / directories without asking for permission

prp-generation

9
from aspiers/ai-config

Generate a Product Requirements Prompt (PRP) from a feature description. Use when starting work on a new feature.

project-initialization

9
from aspiers/ai-config

Initialize a project with AI agent rules and documentation. Use when setting up a new repository for AI agent collaboration.