run-tests

Run OhMyCode pytest suites and analyze failures with tracebacks.

131|4|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/AlphaLab-USTC/OhMyCode --skill run-tests-alphalab-ustc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-tests
Source: https://github.com/AlphaLab-USTC/OhMyCode/tree/main/.claude/skills/run-tests
Command: npx skills add https://github.com/AlphaLab-USTC/OhMyCode --skill run-tests-alphalab-ustc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you verify that changes to OhMyCode still work by running the appropriate tests, reading failures, and guiding the next fix.

Core Features & Use Cases

  • Scoped Test Execution: Run the full suite or a targeted subset such as tools, core, providers, config, or skills.
  • Failure Analysis: Read pytest output, identify whether the issue is in tests, implementation, or environment setup, and determine the next action.
  • Regression Control: Re-run tests after fixes and prompt for a full-suite check when only a subset was executed.
  • Use Case: After editing code in ohmycode/, use this Skill to verify the change, inspect any traceback, and continue the repair loop until tests pass.

Quick Start

Ask to run the relevant OhMyCode tests for the area you changed and report any failures with the traceback.

Frequently Asked Questions about run-tests

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

FAQPage Schema
How do I run pytest tests for specific code areas after making changes?

Run pytest tests by targeting a scoped subset such as tools, core, providers, config, or skills. Scoped test execution verifies that your code changes work without running the full suite.

What is the best way to analyze pytest tracebacks and fix failing tests?

Analyze pytest failures by reading the traceback, log capture, and output to identify whether the issue is in the tests, implementation, or environment setup, then apply the next fix.

Do I need pytest to run regression checks on my code changes?

Yes, pytest is required to run regression checks. The process involves log capture, traceback review, and iterative re-running until the test suite is green.

How do I control regression risks when running a scoped test subset?

Control regression by re-running tests after fixes and prompting for a full-suite check when only a scoped subset was executed, ensuring no hidden regressions remain.

Why do my pytest tests keep failing after applying a code fix?

Tests may keep failing because the failure analysis requires iterative re-running. You must inspect the traceback, determine if the issue is environment or implementation related, and continue the repair loop.