تشغيل أي مهارة في Manus بنقرة واحدة

sonarclaude

النجوم٣

التفرعات١

آخر تحديث٢٢ يونيو ٢٠٢٦ في ١٨:٥٨

Query SonarCloud API for code quality data. Use when: checking quality gate status, fetching code issues or security hotspots, reviewing metrics (coverage, bugs, code smells), or the user says "sonar", "quality gate", "code quality", "sonarclaude".

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

agentculture

agentculture/lobes-cli

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

محللو ضمان جودة البرمجيات والمختبرونمهن الحاسوب والرياضيات·SOC 15-1253

مستكشف الملفات

2 ملفات

SKILL.md

readonly

name	sonarclaude
description	Query SonarCloud API for code quality data. Use when: checking quality gate status, fetching code issues or security hotspots, reviewing metrics (coverage, bugs, code smells), or the user says "sonar", "quality gate", "code quality", "sonarclaude".

SonarClaude

Vendored from steward (canonical upstream: docs/skill-sources.md); this copy is owned by lobes and may diverge.

Query SonarCloud projects for quality gate status, issues, metrics, and security hotspots.

Prerequisites

The script requires the following tools on PATH:

bash
curl — talks to the SonarCloud REST API
jq — parses responses and URL-encodes accept comments

Environment

Requires SONAR_TOKEN environment variable. Set the project key per-repo via the SONAR_PROJECT environment variable (or pass --project KEY on each invocation).

Usage

# Quality gate status (pass/fail)
bash .claude/skills/sonarclaude/scripts/sonar.sh status

# List issues (bugs, vulnerabilities, code smells)
bash .claude/skills/sonarclaude/scripts/sonar.sh issues

# Filter issues by severity and type
bash .claude/skills/sonarclaude/scripts/sonar.sh issues --severity CRITICAL --type BUG

# Key metrics (coverage, bugs, code smells, duplication, LOC)
bash .claude/skills/sonarclaude/scripts/sonar.sh metrics

# Security hotspots
bash .claude/skills/sonarclaude/scripts/sonar.sh hotspots

# Accept (won't-fix) an OPEN issue with a rationale comment
bash .claude/skills/sonarclaude/scripts/sonar.sh accept \
  --issue AZ3Ep83i4ywi8V_l99p0 \
  --comment "Pushback: rule premise doesn't fit our test fixture pattern."

# Different project
bash .claude/skills/sonarclaude/scripts/sonar.sh status --project OtherOrg_OtherProject

# Raw JSON output
bash .claude/skills/sonarclaude/scripts/sonar.sh issues --raw

# Limit results
bash .claude/skills/sonarclaude/scripts/sonar.sh issues --limit 10

Options

Flag	Default	Description
`--project`	`$SONAR_PROJECT`	SonarCloud project key
`--severity`	all	Filter: `BLOCKER`, `CRITICAL`, `MAJOR`, `MINOR`, `INFO`
`--type`	all	Filter: `BUG`, `VULNERABILITY`, `CODE_SMELL`
`--limit`	`25`	Max results returned
`--raw`	off	Output raw JSON instead of formatted summary
`--issue`	—	Issue key (required for `accept`)
`--comment`	—	Rationale comment (required for `accept`)

When to use `accept`

Sonar rules occasionally flag patterns where the rule's premise does not fit the code (e.g. test fixtures with intentional bad-password literals, contradictory rule pairs like S7494 vs S7500). After deciding pushback in PR review, run sonar.sh accept with a rationale comment instead of leaving the issue OPEN — this moves it to ACCEPTED/WONTFIX in SonarCloud history (visible to future maintainers) while clearing the quality-gate signal. Always include a --comment explaining why; silent dismissals are not acceptable curation.

Do not call SonarCloud's HTTP API directly from other skills or one-off scripts — sonar.sh accept is the supported entry point so the rationale flow stays consistent.

المزيد من هذا المستودع

نفس المستودع

recall

agentculture/lobes-cli

Search the shared eidetic memory store and get back ranked, provenanced records. Drives `eidetic recall` with four search modes — exact (verbatim substring), approximate (vector/semantic), keyword (BM25 lexical), and hybrid (a weighted blend of vector+keyword, the default) — each hit carrying its text, full metadata, a relevance `score`, and a freshness `signal`. Recall passively reinforces matched records (bumps last_recall + recall_count). Shadowed and archived records are excluded by default; use --include-shadowed / --include-archived to retrieve them. The store lives at ~/.eidetic/memory (a home-dir path outside any git worktree); the wrapper defaults queries to this agent's PERSONAL, PRIVATE scope (`--scope lobes --visibility private`, suffix read from culture.yaml) — matching where /remember writes — so a no-flag recall returns this agent's own private records plus the shared public pool, and Claude and the colleague backend recall each other's memories because both resolve the same suffix via this ski

2026-06-263

remember

agentculture/lobes-cli

Ingest records into the shared eidetic memory store so they can be recalled later. Drives `eidetic remember`: accepts one record as a JSON object, or a batch as NDJSON on stdin for bulk ingest. Upsert is idempotent by id (and dedups by content hash) — re-remembering updates in place, never duplicates. Stamps a `created` date on every record at ingest time. Accepts `supersedes` (id of the record this one replaces, for within-scope shadowing via `sweep`) and `links` (list of related-memory ids). The store lives at ~/.eidetic/memory (a home-dir path outside any git worktree), and the wrapper defaults records to this agent's PERSONAL, PRIVATE scope (`--scope lobes --visibility private`, suffix read from culture.yaml) so they don't leak to a default/other-scope recall — Claude and the colleague backend still share them because both resolve the same suffix via this skill. Pass `--visibility public` to contribute to the shared public pool instead. Use when the user says "remember this", "store this", "save to memory

2026-06-263

ask-colleague

agentculture/lobes-cli

Ask colleague — a *different* backend/model than you (e.g. a local vLLM Qwen) — to take a scoped repo task off your plate, then fold its answer back. The point isn't a stronger model; it's a second, independent mind, and that diversity is the value: `ask-colleague review` gets a candid second opinion on a diff, `ask-colleague explore` gets a fresh read of an area, `ask-colleague write` hands off a small implementation, `ask-colleague feedback` grades a finished work item (the ROI loop), and `ask-colleague clean` reaps stale/corrupt `colleague/*` branches a crashed run left behind (which can break `git fetch`). Pilot a running work item with `monitor`/`guide`/`stop`. Reach for it REFLEXIVELY, the way you'd lean over to the teammate at the next desk — not only when asked: before you present or open a PR on a non-trivial committed diff, run `review` for a diverse second opinion; for a fresh read of an unfamiliar area whose answer is independent of your current context, run `explore`. Both are read-only — isolate

2026-06-223

cicd

agentculture/lobes-cli

Steward's CI/CD lane, layered on `agex pr`. Delegates lint / open / read / reply / delta to agex; adds two steward extensions — `status` (SonarCloud quality gate + hotspots + unresolved-thread tally) and `await` (read --wait + status with non-zero exit on Sonar ERROR or unresolved threads). Use when: creating PRs in steward, handling review feedback, polling CI status, or the user says "create PR", "review comments", "address feedback", "resolve threads". Renamed from `pr-review` in steward 0.7.0; rebased on agex in 0.12.0.

2026-06-223

communicate

agentculture/lobes-cli

Cross-repo + mesh communication from steward: file tracked GitHub issues on sibling repos, fetch issues from sibling repos to inline current state into briefs, and send live messages to Culture mesh channels. Use when the next step lives outside steward (a brief for a sibling-repo agent, a status ping for a Culture channel, or pulling an issue body + comments into context). Issue posts auto-sign with `- steward (Claude)`; mesh messages are unsigned (the IRC nick is the speaker). Not for in-steward issues — use `gh issue create` or the `cicd` skill for those. Renamed from `coordinate` in steward 0.8.0; absorbed `gh-issues` in 0.9.1. Issue I/O is backed by `agtag` (>=0.1) starting in 0.11.0.

2026-06-223

doc-test-alignment

agentculture/lobes-cli

Verify that committed docs (README.md, CLAUDE.md, SKILL.md descriptions) still describe what the code and tests actually do. Use at the end of a plan, before PR creation, or when the user says "check doc-test alignment", "verify docs", or "do the docs still match the code". STUB — `scripts/check.sh` exits with a not-yet-implemented error today; the contract for what it will do lives in this file.

2026-06-223

SonarClaude

Vendored from steward (canonical upstream: docs/skill-sources.md); this copy is owned by lobes and may diverge.

Query SonarCloud projects for quality gate status, issues, metrics, and security hotspots.

Prerequisites

The script requires the following tools on PATH:

bash

curl — talks to the SonarCloud REST API

jq — parses responses and URL-encodes accept comments

Environment

Requires SONAR_TOKEN environment variable. Set the project key per-repo via the SONAR_PROJECT environment variable (or pass --project KEY on each invocation).

Usage

# Quality gate status (pass/fail) bash .claude/skills/sonarclaude/scripts/sonar.sh status # List issues (bugs, vulnerabilities, code smells) bash .claude/skills/sonarclaude/scripts/sonar.sh issues # Filter issues by severity and type bash .claude/skills/sonarclaude/scripts/sonar.sh issues --severity CRITICAL --type BUG # Key metrics (coverage, bugs, code smells, duplication, LOC) bash .claude/skills/sonarclaude/scripts/sonar.sh metrics # Security hotspots bash .claude/skills/sonarclaude/scripts/sonar.sh hotspots # Accept (won't-fix) an OPEN issue with a rationale comment bash .claude/skills/sonarclaude/scripts/sonar.sh accept \ --issue AZ3Ep83i4ywi8V_l99p0 \ --comment "Pushback: rule premise doesn't fit our test fixture pattern." # Different project bash .claude/skills/sonarclaude/scripts/sonar.sh status --project OtherOrg_OtherProject # Raw JSON output bash .claude/skills/sonarclaude/scripts/sonar.sh issues --raw # Limit results bash .claude/skills/sonarclaude/scripts/sonar.sh issues --limit 10

Options

Flag

Default

Description

--project

$SONAR_PROJECT

SonarCloud project key

--severity

all

Filter: BLOCKER, CRITICAL, MAJOR, MINOR, INFO

--type

all

Filter: BUG, VULNERABILITY, CODE_SMELL

--limit

25

Max results returned

--raw

off

Output raw JSON instead of formatted summary

--issue

—

Issue key (required for accept)

--comment

—

Rationale comment (required for accept)

When to use accept

Do not call SonarCloud's HTTP API directly from other skills or one-off scripts — sonar.sh accept is the supported entry point so the rationale flow stays consistent.

sonarclaude

SonarClaude

Prerequisites

Environment

Usage

Options

When to use accept

المزيد من هذا المستودع

المزيد من هذا المستودع

SonarClaude

Prerequisites

Environment

Usage

Options

When to use accept

When to use `accept`

When to use `accept`