Loop On CiSAFE
Cursor plugin specification and official plugins
Overview
Cursor plugin specification and official plugins
890eaf6b2dddOBSERVED · 2026-10-12What 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: loop-on-ci description: Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks. --- # Loop on CI ## Trigger Need to watch a branch or pull request and iterate on CI failures until all required checks are green. Use `gh pr checks` as the source of truth. It includes all PR-attached checks, while `gh run list` only covers GitHub Actions. ## Workflow 1. Resolve the PR for the current branch. 2. Inspect current PR checks before waiting. 3. If checks already failed, diagnose those failures first. 4. If checks are pending, watch with `gh pr checks --watch --fail-fast`. 5. After each push, re-check the full PR check set and repeat until green. ## Commands ```bash # Resolve the active PR gh pr view --json number,url,headRefName # Inspect all attached checks gh pr checks --json name,bucket,state,workflow,link # Watch pending checks and fail fast gh pr checks --watch --fail-fast # GitHub Actions logs, when the failing check links to a GHA run gh run view <run-id> --log-failed ``` ## Guardrails - Keep each fix scoped to a single failure cause when possible. - Do not bypass hooks (`--no-verify`) to force progress. - If the failure is clearly unrelated to the PR and appears fixed on main, merge latest main instead of bloating the PR with unrelated fixes. - If failures are flaky, retry once and report flake evidence. - Re-run `gh pr checks --json name,bucket,state,workflow,link` after every push; the check set can change. ## Output - Current CI status - Failure summary and fixes applied - PR URL once checks are green
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| 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 (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
890eaf6b2dddfull audit observations/trust-audit/skill/cursor__loop-on-ci.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-12 | 890eaf6b2ddd | SAFE | B | 89 | first audit |
Questions
What does the Loop On Ci skill do?
Cursor plugin specification and official plugins
Is Loop On Ci safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Loop On Ci 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 (890eaf6b2ddd), read on 2026-10-12. The repository is watched, and a new audit runs when it changes — this is the first audit.