Ci AllCAUTION
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
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-all description: "Full CI pipeline: run local tests, type check, push branch, and return the pipeline URL. The only command you need before opening a PR." argument-hint: "[--skip-tests | --e2e]" allowed-tools: [Bash] model: haiku effort: medium disable-model-invocation: true --- # /ci:all: Full CI before PR Runs everything in order: local tests → type check → push → pipeline URL. One `/ci:all` replaces: manual tests + git push + copying the pipeline URL. ## Stack detection ```bash if [ -f "uv.lock" ]; then STACK="python" elif [ -f "pnpm-lock.yaml" ]; then STACK="node" elif [ -f "package-lock.json" ]; then STACK="node-npm" elif [ -f "Cargo.toml" ]; then STACK="rust" fi ``` ## Step 1: Local tests (blocking) **Python (uv/pytest):** ```bash uv run pytest --tb=short -q # Failure → STOP + print failing tests ``` **Node (pnpm/vitest):** ```bash pnpm vitest run pnpm tsc --noEmit # Failure → STOP ``` **Rust:** ```bash cargo test --quiet 2>&1 ``` If `--skip-tests` is passed → skip to step 2. ## Step 2: Push + pipeline ```bash BRANCH=$(git branch --show-current) # Verify commits exist to push AHEAD=$(git rev-list --count origin/$BRANCH..HEAD 2>/dev/null || echo "1") if [ "$AHEAD" = "0" ]; then echo "Branch already up to date on origin." else git push origin "$BRANCH" fi ``` ## Step 3: Pipeline URL ### GitLab CI ```bash REMOTE=$(git remote get-url origin) WEB_URL=$(echo "$REMOTE" | sed 's/git@gitlab\.com:/https:\/\/gitlab.com\//' | sed 's/\.git$//') echo "Pipeline: $WEB_URL/-/pipelines?ref=$BRANCH" # Optional: live status via glab CLI if command -v glab &>/dev/null; then sleep 3 glab ci status --branch "$BRANCH" 2>/dev/null || true fi ``` ### GitHub Actions ```bash REMOTE=$(git remote get-url origin) WEB_URL=$(echo "$REMOTE" | sed 's/git@github\.com:/https:\/\/github.com\//' | sed 's/\.git$//') echo "Actions: $WEB_URL/actions?query=branch%3A$BRANCH" # Optional: live status via gh CLI if command -v gh &>/dev/null; then sleep 5 gh run list --branch "$BRANCH" --limit 3 2>/dev/null || true fi ``` ## Expected output ``` CI: my-app (Node/Vitest) ────────────────────────── 1 Local tests ✅ 47 passed in 8.2s 2 Type check ✅ No errors 3 Push ✅ origin/feat/my-feature 4 Pipeline 🔗 https://gitlab.com/org/my-app/-/pipelines?ref=feat/my-feature Next step: open a PR with /pr or directly on GitLab/GitHub. ``` If tests fail: ``` CI: my-api (Python/pytest) ──────────────────────────── 1 Local tests ❌ 2 failed FAILED tests/test_orders.py::TestOrderService::test_refund_validation AssertionError: expected 400, got 500 → Fix tests before pushing. Pipeline not triggered. ``` ## Usage ``` /ci:all /ci:all --skip-tests # push without re-running tests /ci:all --e2e # include E2E tests (if configured) ``` 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-all.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 All skill do?
The most comprehensive Claude Code guide: agentic workflows, hooks, skills, MCP servers, quizzes, and production-ready templates. 430K+ lines.
Is Ci All 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 All 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.