Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

run-tests

Étoiles1

Forks0

Mis à jour25 mai 2026 à 06:14

Run pytest with parallel execution and coverage. Use when running tests, verifying changes, or the user says "run tests", "test", or "pytest".

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

agentculture

agentculture/auntiepypi

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	run-tests
description	Run pytest with parallel execution and coverage. Use when running tests, verifying changes, or the user says "run tests", "test", or "pytest".
type	command

Run Tests

Run the project's pytest suite with optional parallelism (pytest-xdist) and coverage. Coverage targets are read from pyproject.toml's [tool.coverage.run] section, so the same script works in any sibling repo without modification.

Usage

# Default: parallel + verbose (recommended)
bash .claude/skills/run-tests/scripts/test.sh -p

# Quick check: parallel + quiet
bash .claude/skills/run-tests/scripts/test.sh -p -q

# Full CI mode: parallel + coverage + xml report
bash .claude/skills/run-tests/scripts/test.sh --ci

# Specific test file
bash .claude/skills/run-tests/scripts/test.sh -p tests/test_socket_server.py

# Without parallelism (for debugging test ordering issues)
bash .claude/skills/run-tests/scripts/test.sh tests/test_rooms.py

# With coverage
bash .claude/skills/run-tests/scripts/test.sh -p -c

Options

Flag	Short	Description
`--parallel`	`-p`	Run with `-n auto` (pytest-xdist, uses all CPU cores)
`--coverage`	`-c`	Enable coverage reporting to terminal
`--ci`		Full CI mode: parallel + coverage + XML report + verbose
`--quick`	`-q`	Quiet output (no verbose, no coverage)

Extra arguments are passed through to pytest (e.g., -x for stop-on-first-failure, -k "pattern" for filtering).

When to Use Which Mode

After code changes: bash test.sh -p — fast parallel run, verbose output
Quick sanity check: bash test.sh -p -q — minimal output
Before PR / release: bash test.sh --ci — matches CI exactly
Debugging flaky test: bash test.sh tests/test_flaky.py — sequential, single file

Plus depuis ce dépôt

même dépôt

recall

agentculture/auntiepypi

Search the shared eidetic memory store and get back ranked, provenanced records. Drives `eidetic recall` with four search modes — exact (verbatim substring), approximate (vector/semantic), keyword (BM25 lexical), and hybrid (a weighted blend of vector+keyword, the default) — each hit carrying its text, full metadata, a relevance `score`, and a freshness `signal`. Recall passively reinforces matched records (bumps last_recall + recall_count). Shadowed and archived records are excluded by default; use --include-shadowed / --include-archived to retrieve them. The store lives at ~/.eidetic/memory (a home-dir path outside any git worktree); the wrapper defaults queries to this agent's PERSONAL, PRIVATE scope (`--scope auntiepypi --visibility private`, suffix read from culture.yaml) — matching where /remember writes — so a no-flag recall returns this agent's own private records plus the shared public pool, and Claude and the colleague backend recall each other's memories because both resolve the same suffix via thi

2026-06-231

remember

agentculture/auntiepypi

Ingest records into the shared eidetic memory store so they can be recalled later. Drives `eidetic remember`: accepts one record as a JSON object, or a batch as NDJSON on stdin for bulk ingest. Upsert is idempotent by id (and dedups by content hash) — re-remembering updates in place, never duplicates. Stamps a `created` date on every record at ingest time. Accepts `supersedes` (id of the record this one replaces, for within-scope shadowing via `sweep`) and `links` (list of related-memory ids). The store lives at ~/.eidetic/memory (a home-dir path outside any git worktree), and the wrapper defaults records to this agent's PERSONAL, PRIVATE scope (`--scope auntiepypi --visibility private`, suffix read from culture.yaml) so they don't leak to a default/other-scope recall — Claude and the colleague backend still share them because both resolve the same suffix via this skill. Pass `--visibility public` to contribute to the shared public pool instead. Use when the user says "remember this", "store this", "save to m

2026-06-231

agent-config

agentculture/auntiepypi

Show a Culture agent's full configuration in one read-only view: its system-prompt file (CLAUDE.md / AGENTS.md / GEMINI.md), the parallel culture.yaml, and the agent's local .claude/skills index. Use when an operator says "show agent <name>", "what does <agent> look like", or before teaching/onboarding an agent and you need to see its current kit + config. Backs the `guild show` verb. Vendored via guildmaster (origin steward; cite-don't-import); inventory only — it reports, it does not judge alignment or drift.

2026-05-251

cicd

agentculture/auntiepypi

auntiepypi's CI/CD lane, layered on `agex pr`. Delegates lint / open / read / reply / delta to agex; adds two extensions — `status` (SonarCloud quality gate + hotspots + unresolved-thread tally) and `await` (read --wait + status with non-zero exit on Sonar ERROR or unresolved threads). Use when: creating PRs in auntiepypi, handling review feedback, polling CI status, or the user says "create PR", "review comments", "address feedback", "resolve threads". Renamed from `pr-review` in steward 0.7.0; rebased on agex in 0.12.0.

2026-05-251

communicate

agentculture/auntiepypi

Cross-repo + mesh communication from auntiepypi: file tracked GitHub issues on sibling repos, fetch issues from sibling repos to inline current state into briefs, and send live messages to Culture mesh channels. Use when the next step lives outside auntiepypi (a brief for a sibling-repo agent, a status ping for a Culture channel, or pulling an issue body + comments into context). Issue posts auto-sign with `- auntiepypi (Claude)`; mesh messages are unsigned (the IRC nick is the speaker). Not for in-auntiepypi issues — use `gh issue create` or the `cicd` skill for those. Renamed from `coordinate` in steward 0.8.0; absorbed `gh-issues` in 0.9.1. Issue I/O is backed by `agtag` (>=0.1) starting in 0.11.0.

2026-05-251

doc-test-alignment

agentculture/auntiepypi

Verify that committed docs (README.md, CLAUDE.md, SKILL.md descriptions) still describe what the code and tests actually do. Use at the end of a plan, before PR creation, or when the user says "check doc-test alignment", "verify docs", or "do the docs still match the code". STUB — `scripts/check.sh` exits with a not-yet-implemented error today; the contract for what it will do lives in this file.

2026-05-251

name	run-tests
description	Run pytest with parallel execution and coverage. Use when running tests, verifying changes, or the user says "run tests", "test", or "pytest".
type	command

Run Tests

Usage

# Default: parallel + verbose (recommended)
bash .claude/skills/run-tests/scripts/test.sh -p

# Quick check: parallel + quiet
bash .claude/skills/run-tests/scripts/test.sh -p -q

# Full CI mode: parallel + coverage + xml report
bash .claude/skills/run-tests/scripts/test.sh --ci

# Specific test file
bash .claude/skills/run-tests/scripts/test.sh -p tests/test_socket_server.py

# Without parallelism (for debugging test ordering issues)
bash .claude/skills/run-tests/scripts/test.sh tests/test_rooms.py

# With coverage
bash .claude/skills/run-tests/scripts/test.sh -p -c

Options

Flag	Short	Description
`--parallel`	`-p`	Run with `-n auto` (pytest-xdist, uses all CPU cores)
`--coverage`	`-c`	Enable coverage reporting to terminal
`--ci`		Full CI mode: parallel + coverage + XML report + verbose
`--quick`	`-q`	Quiet output (no verbose, no coverage)

Extra arguments are passed through to pytest (e.g., -x for stop-on-first-failure, -k "pattern" for filtering).

When to Use Which Mode

After code changes: bash test.sh -p — fast parallel run, verbose output
Quick sanity check: bash test.sh -p -q — minimal output
Before PR / release: bash test.sh --ci — matches CI exactly
Debugging flaky test: bash test.sh tests/test_flaky.py — sequential, single file