Ci StatusCAUTION
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-07What 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-status
description: Show current pipeline status for the active branch (GitLab CI or GitHub Actions)
argument-hint: "[pr_number optional]"
allowed-tools: [Bash]
model: haiku
effort: low
disable-model-invocation: true
---
# /ci:status: Pipeline status
Quick snapshot of the CI pipeline on the current branch.
## Process
```bash
# 1. Current branch
BRANCH=$(git branch --show-current)
echo "Branch: $BRANCH"
# 2. Last commits
git log -3 --oneline
```
## GitLab CI
```bash
# With glab CLI (recommended)
if command -v glab &>/dev/null; then
glab ci status --branch "$BRANCH"
else
# Fallback: show URL
REMOTE=$(git remote get-url origin 2>/dev/null || echo "")
if [ -n "$REMOTE" ]; then
WEB_URL=$(echo "$REMOTE" | sed 's/git@gitlab\.com:/https:\/\/gitlab.com\//' | sed 's/\.git$//')
echo "Pipeline: $WEB_URL/-/pipelines?ref=$BRANCH"
fi
fi
# If MR number provided
if [ -n "$ARGUMENTS" ] && command -v glab &>/dev/null; then
glab mr view "$ARGUMENTS"
fi
```
## GitHub Actions
```bash
# With gh CLI (recommended)
if command -v gh &>/dev/null; then
gh run list --branch "$BRANCH" --limit 5
else
# Fallback: show URL
REMOTE=$(git remote get-url origin 2>/dev/null || echo "")
if [ -n "$REMOTE" ]; then
WEB_URL=$(echo "$REMOTE" | sed 's/git@github\.com:/https:\/\/github.com\//' | sed 's/\.git$//')
echo "Actions: $WEB_URL/actions?query=branch%3A$BRANCH"
fi
fi
# If PR number provided
if [ -n "$ARGUMENTS" ] && command -v gh &>/dev/null; then
gh pr checks "$ARGUMENTS"
fi
```
## Expected output
```
Branch: feat/add-payment-retry
Last commits:
a1b2c3d feat(payments): add retry logic with exponential backoff
e4f5g6h test(payments): add Vitest coverage on retry scenarios
i7j8k9l chore: update pnpm lockfile
Pipeline: running
✅ lint 30s
✅ typecheck 45s
⏳ test running...
⏸️ deploy waiting
URL: https://gitlab.com/org/my-app/-/pipelines?ref=feat/add-payment-retry
```
## Usage
```
/ci:status
/ci:status 42 # MR or PR number 42
```
Target: $ARGUMENTSTrust 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-status.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 Status skill do?
The most comprehensive Claude Code guide: agentic workflows, hooks, skills, MCP servers, quizzes, and production-ready templates. 430K+ lines.
Is Ci Status 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 Status 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.