SECURITY REVIEW
Not yet assessed
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
Run local CI checks with ruff, bandit, pytest, and sonar-scanner, then refresh SonarQube.
Run the local CI pipeline (ruff, bandit, pytest, sonar-scanner) and refresh SonarQube.
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
How clearly the skill guides your agent, how complete its workflow is, and how you can check the outcome.
No quality assessment is available for this catalog entry yet.
Original instructions from the publisher’s SKILL.md
# /ci: full local CI + SonarQube refresh Run this before opening a PR, or whenever the `mcp__sonarqube__*` findings look stale. The scanner uploads the JSON reports that ruff, bandit, and pytest produce, so those have to run first. ## Steps 1. Drop stale reports so the scanner never uploads yesterday's data. 2. Sync dev and test deps. 3. Run ruff with a JSON report (exit-zero so the chain continues even if there are findings). 4. Run bandit with a JSON report (exit-zero, same reason). 5. Run the full pytest suite (must pass; pytest-cov writes `reports/coverage.xml`). 6. Assert `reports/coverage.xml` exists and is non-empty. This guards against the "0% coverage" trap where `sonar-scanner` silently ships an empty report. 7. Invoke `sonar-scanner`, tee the log to `reports/sonar-scan.log`. ```bash rm -f reports/coverage.xml reports/lcov.info reports/ruff_report.json reports/bandit_report.json && \ uv sync --group dev --group test && \ uv run ruff check --fix --output-format=json --output-file=reports/ruff_report.json --exit-zero . && \ uv run bandit --configfile pyproject.toml --recursive --format json --output reports/bandit_report.json --exit-zero . && \ uv run pytest && \ test -s reports/coverage.xml && \ sonar-scanner 2>&1 | tee reports/sonar-scan.log ``` After the scanner finishes, use `mcp__sonarqube__search_sonar_issues_in_projects` to pull new findings for review. ## Notes - pytest is the gate: if tests fail, the chain stops before the scanner runs. - The `test -s reports/coverage.xml` guard is the second gate. If coverage.xml is missing or empty the chain stops before upload, so the SonarCloud dashboard never flips back to 0%. - ruff and bandit are set to `--exit-zero` on purpose so report JSON is always written. - Do **not** skip this pipeline to make findings disappear. If something is flaky, fix the flake. - Do **not** run `sonar-scanner` on its own. Without a fresh `reports/coverage.xml` it uploads an analysis with 0% coverage and overwrites the last good one.