ci — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited ci (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
why-not-mechanizable: skill workflow guidance; each step requires understanding the surrounding context (repo, task shape, prior state).
.gitlab-ci.yml -> glab, .github/ -> gh (review-time: see section note)(review-time: see section note)bash ~/.claude/skills/ci/scripts/gh-ci-monitor.sh (review-time: see section note)bash ~/.claude/skills/ci/scripts/glab-ci-monitor.sh (review-time: see section note)persistent: false, timeout_ms: 3600000 (1 hour ceiling — CI pipelines can be long) (review-time: see section note)(review-time: see section note)(review-time: see section note)no-runs|<branch>: no CI runs found for this branch — inform the user and stop (review-time: see section note)error|persistent-failure: the monitor script hit 5 consecutive errors — report and stop (review-time: see section note)in_progress|null → completed|success): acknowledge briefly (review-time: see section note)completed|success): (review-time: see section note)~/.claude/scripts/notify.sh "CI passed - <branch-name>" (review-time: see section note)(review-time: see section note)completed|manual, GitLab only): (review-time: see section note)(review-time: see section note)~/.claude/scripts/notify.sh "CI awaiting manual action - <branch-name>" (review-time: see section note)(review-time: see section note)completed|failure or any non-success conclusion): (review-time: see section note)a. Fetch the job log:
glab ci trace <job-id> (review-time: see section note)gh run view <run-id> --log-failed (review-time: see section note)b. Do NOT pipe output through head, tail, grep, or any other command - run the commands directly c. Analyze the root cause - identify the specific failure (test, lint, type check, build, coverage, etc.) d. Run ~/.claude/scripts/notify.sh "CI failed - <failure-summary>" e. Propose the fix to the user - explain what failed and what you'd change. Do NOT push automatically f. Wait for user approval before implementing the fix g. After approval: fix, commit with a descriptive message, push
The monitor scripts poll CI status every 30 seconds but only emit a line when the status changes. This means:
(review-time: see section note)(review-time: see section note)(review-time: see section note)gh/glab fails 5 times in a row (auth expired, network down), the script exits with an error notification (review-time: see section note)These commands require a TTY and will NOT work - never use them:
glab ci view (interactive TUI) (review-time: see section note)gh run watch (interactive watcher) (review-time: see section note)--web flag (opens browser) (review-time: see section note)Safe commands to use:
glab ci status, glab ci list, glab ci trace <job-id> (review-time: see section note)gh pr checks, gh run list, gh run view <run-id> --log-failed (review-time: see section note)(review-time: see section note)(review-time: see section note)--no-verify or skip hooks (review-time: see section note)(review-time: see section note)~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.