New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Run Tests

by AlphaLab-USTC in AlphaLab-USTC/OhMyCode

Run tests and analyze results for OhMyCode. An agent skill from AlphaLab-USTC/OhMyCode.

MITAuto-check passed

Install Run Tests

skills CLI
$ npx skills add AlphaLab-USTC/OhMyCode --skill run-tests -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install AlphaLab-USTC/OhMyCode run-tests --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/AlphaLab-USTC/OhMyCode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/run-tests .claude/skills/run-tests && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
run-tests
GitHub stars
131
Token cost
~959 tokens
SKILL.md length
443 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Run tests and analyze results for OhMyCode. An agent skill from AlphaLab-USTC/OhMyCode.

  • Works in 4 steps: Determine Scope → Run Tests → Analyze Results → …
  • User wants to run
  • SKILL.md covers When to Use, Input, Step 1 — Determine Scope and Step 2 — Run Tests, plus 4 more sections
  • Calls python3

What it does

Run Tests is an agent skill from AlphaLab-USTC/OhMyCode. Run tests and analyze results for OhMyCode. Use when user wants to run, check, or verify tests — or after any code change.

Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Minimal and Customizable CC-Style Coding Agent. The licence is MIT.

When your agent uses it

  • User wants to run
  • After any code change

Example prompts

  • “/run-tests”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Determine Scope
  2. Run Tests
  3. Analyze Results
  4. Regression Check

What it can do on your machine

Read from SKILL.md and the folder at commit 4d1bb28. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Run Tests loads about 959 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 443 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~33
When it runs · the whole SKILL.md, loaded when a task matches
~959

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AlphaLab-USTC/OhMyCode at commit 4d1bb28, republished under its MIT licence (© AlphaLab-USTC). 443 words, ~959 tokens.

Download SKILL.mdSave it as .claude/skills/run-tests/SKILL.md (or your agent's skills folder).
name
run-tests
description
Run tests and analyze results for OhMyCode. Use when user wants to run, check, or verify tests — or after any code change.

Run Tests for OhMyCode

Run the project test suite, analyze results, and take action on failures.

This skill is part of the OhMyCode development closed-loop:

编码 ──→ /gen-tests ──→ /run-tests ──→ 分析失败 ──→ 修代码 ──╮
 ↑                                                            │
 ╰────────────────────────────────────────────────────────────╯

When to Use

  • After /gen-tests generates new test files — verify them immediately
  • After editing any source code in ohmycode/ — catch regressions
  • After fixing a bug found by a previous /run-tests — confirm the fix
  • Before committing — full suite gate
  • User says "run tests", "check tests", "verify tests"

Input

$ARGUMENTS — optional scope specifier. If empty, run the full suite.

Argumentpytest path
(empty)tests/ (full suite)
toolstests/tools/
tools/bashtests/tools/test_bash.py
coretests/core/
core/looptests/core/test_loop.py
providerstests/providers/
configtests/config/
skillstests/skills/
specific file pathuse as-is

Step 1 — Determine Scope

Resolve $ARGUMENTS to a pytest target path using the table above.

If a specific file is given, verify it exists. If not, check for the closest match under tests/.

Step 2 — Run Tests

bash
python3 -m pytest <resolved_path> -v --tb=short 2>&1 | tee tests_run.log

Use -v for verbose output and --tb=short for concise tracebacks.

Step 3 — Analyze Results

All passed

Report the result summary (e.g., "73 passed in 2.1s") and confirm the code is healthy. No further action needed.

Failures detected — enter fix loop

For each failure:

  1. Read the traceback from the test output
  2. Classify the root cause:
    • Test bug — the test itself has a wrong assertion or outdated expectation
    • Implementation bug — the source code under test has a defect
    • Environment issue — missing dependency, import error, fixture mismatch
  3. Fix it:
    • For test bugs: fix the test code directly
    • For implementation bugs: fix the source code in ohmycode/
    • For environment issues: install missing deps or fix config
  4. Re-run /run-tests — repeat until all green ✓

This is the core of the closed-loop: fail → diagnose → fix → re-run → pass.

Show full SKILL.md (164 more words)Show less
Warnings

Review warnings in the output. Common ones:

WarningAction
PytestUnraisableExceptionWarningUsually async cleanup — check for missing await
DeprecationWarningNote for future cleanup, not blocking
RuntimeWarning: coroutine was never awaitedMissing await — fix immediately

Ignore warnings that don't affect correctness unless they indicate real bugs.

Step 4 — Regression Check

If Step 2 only ran a subset of tests, prompt to run the full suite:

bash
python3 -m pytest tests/ -v --tb=short 2>&1 | tee tests_run.log

This catches regressions in other modules caused by the recent change. The task is not complete until the full suite passes.

Development Loop Checkpoints

Use /run-tests at every transition in the closed-loop:

WhenWhat to do
After /gen-testsRun new tests to verify they pass
After editing ohmycode/ sourceCatch regressions early
After fixing a failureConfirm the fix, re-enter loop if still red
Before committingFull suite gate — python3 -m pytest tests/ -v must be all green
When resuming workBaseline health check
  • /gen-tests — generates tests; always follow up with /run-tests
  • /commit-conventions — commit after all tests pass

© AlphaLab-USTC, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/run-tests of AlphaLab-USTC/OhMyCode.

Open the folder on GitHubat commit 4d1bb28

Compare with similar skills

Run Tests next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Run Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Run Tests this skillAlphaLab-USTC/OhMyCode131—~959Automated safety check: PassMIT
Debug OhmycodeAlphaLab-USTC/OhMyCode131—~1.3kAutomated safety check: PassMIT
Commit ConventionsAlphaLab-USTC/OhMyCode131—~479Automated safety check: PassMIT
Add FeatureAlphaLab-USTC/OhMyCode131—~995Automated safety check: PassMIT
Add ToolAlphaLab-USTC/OhMyCode131—~758Automated safety check: PassMIT
Add ProviderAlphaLab-USTC/OhMyCode131—~888Automated safety check: PassMIT

Similar skills

  • Debug Ohmycode

    AlphaLab-USTC/OhMyCode

    Guide for debugging OhMyCode issues. An agent skill from AlphaLab-USTC/OhMyCode.

    131 GitHub stars~1.3k tokensUpdated 6 mo ago
    DevelopmentAuto-check passed

  • Commit Conventions

    AlphaLab-USTC/OhMyCode

    OhMyCode commit message conventions. An agent skill from AlphaLab-USTC/OhMyCode.

    131 GitHub stars~479 tokensUpdated 6 mo ago
    DevelopmentAuto-check passed

  • Add Feature

    AlphaLab-USTC/OhMyCode

    Guide for adding a new feature to OhMyCode. An agent skill from AlphaLab-USTC/OhMyCode.

    131 GitHub stars~995 tokensUpdated 6 mo ago
    Testing & QAAuto-check passed

  • Add Tool

    AlphaLab-USTC/OhMyCode

    Guide for adding a new tool to OhMyCode. An agent skill from AlphaLab-USTC/OhMyCode.

    131 GitHub stars~758 tokensUpdated 6 mo ago
    Testing & QAAuto-check passed

  • Add Provider

    AlphaLab-USTC/OhMyCode

    Guide for adding a new LLM provider to OhMyCode. An agent skill from AlphaLab-USTC/OhMyCode.

    131 GitHub stars~888 tokensUpdated 6 mo ago
    Auto-check passed

  • Gen Tests

    AlphaLab-USTC/OhMyCode

    Generate high-quality tests for OhMyCode modules. An agent skill from AlphaLab-USTC/OhMyCode.

    131 GitHub stars~1.6k tokensUpdated 6 mo ago
    Testing & QAAuto-check passed

More from AlphaLab-USTC/OhMyCode

All 10 skills in this repo

  • Bench

    AlphaLab-USTC/OhMyCode

    Run OhMyCode benchmarks — score any provider/model with token tracking.

    131 GitHub stars~941 tokensUpdated 6 mo ago
    Auto-check passed

  • Customize Response Style

    AlphaLab-USTC/OhMyCode

    Guide for customizing OhMyCode's terminal output style and rendering.

    131 GitHub stars~1.1k tokensUpdated 6 mo ago
    Auto-check passed

  • Customize System Prompt

    AlphaLab-USTC/OhMyCode

    Guide for customizing OhMyCode's AI personality and behavior via system prompt.

    131 GitHub stars~819 tokensUpdated 6 mo ago
    Auto-check passed

Questions about Run Tests

What does Run Tests do?

Run tests and analyze results for OhMyCode. An agent skill from AlphaLab-USTC/OhMyCode. Run Tests is an agent skill from AlphaLab-USTC/OhMyCode. Run tests and analyze results for OhMyCode.

When should I use Run Tests?

Run Tests fits situations like: user wants to run; after any code change.

How do I install Run Tests in Claude Code?

Run `npx skills add AlphaLab-USTC/OhMyCode --skill run-tests -a claude-code`. Or copy the skill folder (.claude/skills/run-tests in AlphaLab-USTC/OhMyCode) into .claude/skills/run-tests in your project. Claude Code loads it when a task matches its description.

How do I install Run Tests in Codex?

Run `npx skills add AlphaLab-USTC/OhMyCode --skill run-tests -a codex`. Or copy the skill folder (.claude/skills/run-tests in AlphaLab-USTC/OhMyCode) into .agents/skills/run-tests in your project. Codex loads it when a task matches its description.

Can I use Run Tests in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AlphaLab-USTC/OhMyCode --skill run-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/run-tests, .gemini/skills/run-tests, .github/skills/run-tests and .opencode/skills/run-tests in your project.

What does Run Tests need to run?

Going by SKILL.md and its folder, Run Tests needs the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Run Tests access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Run Tests safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Run Tests use?

Run Tests is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Run Tests use?

About 959 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Run Tests?

Skills that share tags, products or a category with Run Tests: Debug Ohmycode (AlphaLab-USTC/OhMyCode, 131 stars), Commit Conventions (AlphaLab-USTC/OhMyCode, 131 stars), Add Feature (AlphaLab-USTC/OhMyCode, 131 stars) and Add Tool (AlphaLab-USTC/OhMyCode, 131 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Run Tests?

AlphaLab-USTC (a GitHub user) maintains it in AlphaLab-USTC/OhMyCode, which has 131 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on April 2, 2026.

Source: AlphaLab-USTC/OhMyCode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.