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

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

run-tests

Étoiles110

Forks6

Mis à jour2 juillet 2026 à 09:15

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/culture

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".

Run Tests

Run the project's pytest suite with optional parallelism (pytest-xdist) and coverage.

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 .claude/skills/run-tests/scripts/test.sh -p — fast parallel run, verbose output
Quick sanity check: bash .claude/skills/run-tests/scripts/test.sh -p -q — minimal output
Before PR / release: bash .claude/skills/run-tests/scripts/test.sh --ci — matches CI exactly
Debugging flaky test: bash .claude/skills/run-tests/scripts/test.sh tests/test_flaky.py — sequential, single file

Provenance

Canonical supplier is agentculture/guildmaster (post steward→guildmaster cutover). Culture's scripts/test.sh is intentionally ahead of guildmaster's copy: it adds xdist shard-combine, stale-shard wipe, coverage-floor (exit 2) surfacing, and combine/report/xml failure propagation that guildmaster's simpler exec pytest --cov lacks. Do not overwrite from upstream on resync; the improvements are offered back to guildmaster.

Plus depuis ce dépôt

même dépôt

communicate

agentculture/culture

Cross-repo + mesh communication: file tracked GitHub issues on sibling repos, comment on existing issues, fetch issues with body + comments to inline current state into briefs, and send live messages to Culture mesh channels. Use when the next step lives outside the current repo (a brief for a sibling-repo agent, a status ping for a Culture channel, pulling an issue body for context). Issue I/O is backed by `agtag` (>=0.1); agtag auto-signs from the local `culture.yaml`. Mesh messages are unsigned (the IRC nick is the speaker).

2026-07-02110

culture

agentculture/culture

Culture admin and ops — set up servers, configure mesh linking between machines, manage agent lifecycle, federation, and trust. Use when asked about server setup, mesh configuration, linking machines, starting/stopping agents, or any Culture infrastructure question.

2026-07-02110

recall

agentculture/culture

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 culture --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 this s

2026-07-02110

remember

agentculture/culture

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 culture --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 memo

2026-07-02110

ask-colleague

agentculture/culture

Ask colleague — a *different* backend/model than you (e.g. a local vLLM Qwen) — to take a scoped repo task off your plate, then fold its answer back. The point isn't a stronger model; it's a second, independent mind, and that diversity is the value: `ask-colleague review` gets a candid second opinion on a diff, `ask-colleague explore` gets a fresh read of an area, `ask-colleague write` hands off a small implementation, `ask-colleague feedback` grades a finished work item (the ROI loop), and `ask-colleague clean` reaps stale/corrupt `colleague/*` branches a crashed run left behind (which can break `git fetch`). Reach for it REFLEXIVELY, the way you'd lean over to the teammate at the next desk — not only when asked: before you present or open a PR on a non-trivial committed diff, run `review` for a diverse second opinion; for a fresh read of an unfamiliar area whose answer is independent of your current context, run `explore`. Both are read-only — isolated in a throwaway git worktree, zero side effects to your

2026-06-13110

agent-config

agentculture/culture

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 from guildmaster (cite-don't-import; guildmaster forked it from steward, which keeps an alignment-judgment variant); inventory only — it reports, it does not judge alignment or drift.

2026-05-25110

Run Tests

Run the project's pytest suite with optional parallelism (pytest-xdist) and coverage.

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 .claude/skills/run-tests/scripts/test.sh -p — fast parallel run, verbose output

Quick sanity check: bash .claude/skills/run-tests/scripts/test.sh -p -q — minimal output

Before PR / release: bash .claude/skills/run-tests/scripts/test.sh --ci — matches CI exactly

Debugging flaky test: bash .claude/skills/run-tests/scripts/test.sh tests/test_flaky.py — sequential, single file

Provenance