Ci TestsCAUTION
The most comprehensive Claude Code guide: agentic workflows, hooks, skills, MCP servers, quizzes, and production-ready templates. 430K+ lines.
Overview
The most comprehensive Claude Code guide: agentic workflows, hooks, skills, MCP servers, quizzes, and production-ready templates. 430K+ lines.
d90170da4369OBSERVED · 2026-10-07Install
Commands as the repository documents them. They are shown, not run.
uv run pytest --tb=short -q $ARGUMENTS
uv run pytest --cov=src --cov-report=term-missing -q
uv run pytest $ARGUMENTS -v
uv run pytest --tb=short -q
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: ci-tests description: Run the test suite for the current repo, auto-detecting Python (pytest/uv), Node (vitest/pnpm), or Rust (cargo test) argument-hint: "[file or folder target]" allowed-tools: [Bash] model: haiku effort: low disable-model-invocation: true --- # /ci:tests: Run tests Detects the stack and runs tests with the right command. ## Stack detection ```bash if [ -f "uv.lock" ]; then STACK="python" elif [ -f "pnpm-lock.yaml" ] || [ -f "package.json" ]; then STACK="node" elif [ -f "Cargo.toml" ]; then STACK="rust" else STACK="unknown" fi ``` ## Commands by stack ### Python (uv + pytest) ```bash # All tests uv run pytest --tb=short -q $ARGUMENTS # With coverage uv run pytest --cov=src --cov-report=term-missing -q # Specific file or folder uv run pytest $ARGUMENTS -v ``` ### Node (pnpm + vitest) ```bash # All tests pnpm vitest run $ARGUMENTS # With coverage pnpm vitest run --coverage # Watch mode (dev) pnpm vitest ``` ### Node (npm + jest) ```bash npm test -- --passWithNoTests $ARGUMENTS ``` ### Rust (cargo) ```bash cargo test --quiet $ARGUMENTS 2>&1 ``` ## Expected output ``` Tests: my-api (Python/pytest) ─────────────────────────────── uv run pytest --tb=short -q [pytest output] ✅ 42 passed in 3.1s → Ready to push ``` On failure: ``` ❌ 2 failed FAILED tests/test_billing.py::TestInvoice::test_promo_expired AssertionError: expected discount=0, got discount=10 → Fix before pushing. ``` ## Usage ``` /ci:tests /ci:tests tests/test_orders.py /ci:tests src/components/Button.test.tsx ``` Target: $ARGUMENTS
Trust audit
CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | WARN |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (2)
whitepapers/recap-cards/en/_extensions
whitepapers/recap-cards/fr/_extensions
Gates applied: no_behavioural_pass.
d90170da4369full audit observations/trust-audit/skill/florianbruniaux__ci-tests.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-07 | d90170da4369 | CAUTION | B | 89 | first audit |
Questions
What does the Ci Tests skill do?
The most comprehensive Claude Code guide: agentic workflows, hooks, skills, MCP servers, quizzes, and production-ready templates. 430K+ lines.
Is Ci Tests safe to install?
With care. The audit graded it B (89/100) and found 2 things worth knowing before you trust this skill, listed below with the exact line each was found on.
What can Ci Tests access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (d90170da4369), read on 2026-10-07. The repository is watched, and a new audit runs when it changes — this is the first audit.