菜单
Executes SonarCloud API operations for quality gates, issues, metrics, analysis history, and security hotspots. Use when checking code quality, inspecting bugs/vulnerabilities, retrieving coverage/complexity metrics, or viewing project security status.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | sonarcloud-tools |
| user-invocable | false |
| description | Executes SonarCloud API operations for quality gates, issues, metrics, analysis history, and security hotspots. Use when checking code quality, inspecting bugs/vulnerabilities, retrieving coverage/complexity metrics, or viewing project security status. |
Dictum: Zero-arg defaults enable immediate code quality inspection.
Execute SonarCloud queries through unified Python CLI.
[IMPORTANT] Commands default to project=bsamiee_Parametric_Portal, organization=bsamiee. 1Password auto-injects API token. SonarCloud API base: https://sonarcloud.io/api.
Dictum: Local scanner enables pre-push quality gates.
Run Analysis:
pnpm sonar
Requirements:
SONAR_TOKEN environment variable (1Password injection or export)packages/*/coverage/lcov.info (run nx run-many -t test first)Configuration: sonar-project.properties at repo root.
| [CMD] | [ARGS] | [PURPOSE] |
|---|---|---|
| quality-gate | [branch] or pr <num> | Quality gate pass/fail status |
| issues | [severities] [types] | Search code issues |
| measures | [metrics] | Project metrics |
| analyses | [page_size] | Analysis history |
| projects | [page_size] | List organization projects |
| hotspots | [status] | Security hotspots |
# Zero-arg invocation (most common)
uv run .claude/skills/sonarcloud-tools/scripts/sonarcloud.py quality-gate
uv run .claude/skills/sonarcloud-tools/scripts/sonarcloud.py issues
uv run .claude/skills/sonarcloud-tools/scripts/sonarcloud.py measures
uv run .claude/skills/sonarcloud-tools/scripts/sonarcloud.py analyses
uv run .claude/skills/sonarcloud-tools/scripts/sonarcloud.py projects
uv run .claude/skills/sonarcloud-tools/scripts/sonarcloud.py hotspots
# With optional args
uv run .claude/skills/sonarcloud-tools/scripts/sonarcloud.py quality-gate main
uv run .claude/skills/sonarcloud-tools/scripts/sonarcloud.py quality-gate pr 42
uv run .claude/skills/sonarcloud-tools/scripts/sonarcloud.py issues BLOCKER,CRITICAL
uv run .claude/skills/sonarcloud-tools/scripts/sonarcloud.py issues BLOCKER,CRITICAL BUG,VULNERABILITY
uv run .claude/skills/sonarcloud-tools/scripts/sonarcloud.py measures coverage,bugs
uv run .claude/skills/sonarcloud-tools/scripts/sonarcloud.py analyses 20
uv run .claude/skills/sonarcloud-tools/scripts/sonarcloud.py projects 50
uv run .claude/skills/sonarcloud-tools/scripts/sonarcloud.py hotspots TO_REVIEW
quality-gate: [branch] or pr <num>
main -- specific branchpr 42 -- specific pull requestissues: [severities] [types]
severities -- Comma-separated: BLOCKER, CRITICAL, MAJOR, MINOR, INFOtypes -- Comma-separated: BUG, VULNERABILITY, CODE_SMELLmeasures: [metrics]
metrics -- Comma-separated (default: all standard metrics)ncloc, coverage, bugs, vulnerabilities, code_smells, duplicated_lines_density, security_hotspots, reliability_rating, security_rating, sqale_ratinganalyses: [page_size]
page_size -- Number of results (default: 10, max: 100)projects: [page_size]
page_size -- Number of results (default: 100, max: 500)hotspots: [status]
status -- Filter: TO_REVIEW, ACKNOWLEDGED, FIXED, SAFECommands return: {"status": "success|error", ...}.
| [INDEX] | [CMD] | [RESPONSE] |
|---|---|---|
| [1] | quality-gate | {project, gate_status, passed: bool, conditions[]} |
| [2] | issues | {project, total, issues[], summary} |
| [3] | measures | {project, name, metrics} |
| [4] | analyses | {project, total, analyses[]} |
| [5] | projects | {organization, total, projects[]} |
| [6] | hotspots | {project, total, hotspots[]} |
| [VAR] | [REQUIRED] | [DESCRIPTION] |
|---|---|---|
SONAR_TOKEN | Yes | SonarCloud API token (1Password) |
[ERROR] <status>: <body> and exit 1[ERROR] SONAR_TOKEN environment variable not set[ERROR] 404: Component not foundUse for Bash 5.2+/5.3 scripts, shell CLIs, entrypoints, CI jobs, cron, text-processing pipelines, ShellCheck remediation, and shell reviews. Enforces strict mode, dispatch-table routing, fork-minimal primitives, atomic I/O, signal-safe cleanup, and pragmatic functional shell patterns.
Enforces C# + LanguageExt functional/ROP style, type discipline, runtime-record effects, Scrutor composition, and module organization standards. Use when writing, editing, reviewing, refactoring, or debugging .cs modules, implementing domain models, sealed DU hierarchies, Eff/Fin/Validation pipelines, or configuring .csproj, analyzers, or DI.
Use for PostgreSQL 18 SQL, migrations, DDL, functions, RLS policies, indexes, query plans, extensions, and SQL embedded in TypeScript via @effect/sql-pg. Enforces set-algebraic queries, schema-level invariants, current PostgreSQL features, extension-first design, tenant security, observability, and migration safety.
Enforces Python + expression style, type discipline, error handling, concurrency, and module organization standards. Use when writing, editing, reviewing, refactoring, or debugging .py/.pyi modules, implementing domain models, ROP pipelines, Protocol-driven services, or configuring pyproject.toml, Ruff, or ty.
Enforces TypeScript + Effect functional/ROP style, type discipline, polymorphic surfaces, and module organization standards. Use when writing, editing, reviewing, refactoring, or debugging .ts/.tsx modules, implementing domain models, Effect services, persistence adapters, or boundary handlers, or configuring TypeScript, Effect, or lint/type-check posture.
Generates and validates project documentation: READMEs, ADRs, changelogs, ARCHITECTURE.md, and code documentation. Use when creating, updating, or reviewing any non-code markdown artifact, README file, architecture decision record, ARCHITECTURE document, CHANGELOG entry, or code documentation (docstrings, XML docs, TSDoc). Activates for: (1) scaffolding README, CHANGELOG, ADR, CONTRIBUTING, ARCHITECTURE, or SECURITY files; (2) writing or reviewing doc comments on exported APIs; (3) auditing documentation coverage or staleness; (4) generating release notes from commit history.