sonarcloud-pr-fix

Estrellas0

Forks0

Actualizado30 de abril de 2026 a las 09:10

Use when the user wants to find SonarCloud issues for the current branch pull request, fix them in the local repo, verify with local checks, push the branch, and confirm whether SonarCloud has reanalyzed the PR.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

alkampfergit

alkampfergit/cisharpai

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	sonarcloud-pr-fix
description	Use when the user wants to find SonarCloud issues for the current branch pull request, fix them in the local repo, verify with local checks, push the branch, and confirm whether SonarCloud has reanalyzed the PR.

SonarCloud PR Fix

Use this skill for PR-scoped SonarCloud cleanup work in this repository.

Goal

Find the SonarCloud issues attached to the current branch's pull request, apply the smallest safe fixes, verify locally, push the branch, and check whether SonarCloud has refreshed on the latest commit.

Default assumptions

Repo root is the current working directory.
The branch usually has an open GitHub pull request.
This repo uses Beads for task tracking.
The usual SonarCloud project key here is alkampfergit_azdo-cli.

Workflow

Recover repo and branch context.
- Read AGENTS.md and CLAUDE.md.
- Run git status --short --branch.
- Run git rev-parse --abbrev-ref HEAD.
- Run bd prime.
Create and claim a Beads issue before editing code.
- Example:
  - bd create --title "Fix SonarCloud pull request issues" --type bug --priority 1 --label "sonarcloud,quality" --description "..."
  - bd update <id> --claim
Resolve the current branch to a GitHub pull request number.
- Preferred:
  - curl -fsSL "https://api.github.com/repos/<owner>/<repo>/pulls?state=open&head=<owner>:<branch>"
- Extract the PR number from the response.
- If there is no open PR, stop and tell the user.
Query SonarCloud for PR issues.
- Preferred issue query:
  - curl -fsSL "https://sonarcloud.io/api/issues/search?componentKeys=<projectKey>&pullRequest=<prNumber>&ps=100"
- Also check PR status when needed:
  - curl -fsSL "https://sonarcloud.io/api/project_pull_requests/list?project=<projectKey>"
- Summarize findings by file, rule, and line before editing.
Inspect the affected code and nearby tests.
- Read only the files touched by SonarCloud plus relevant tests.
- Prefer targeted fixes over broad refactors.
- Watch for CI-only failures such as tsc --noEmit issues that local npm test may miss.
Apply fixes.
- Use apply_patch for edits.
- Keep behavior stable unless the Sonar issue requires a behavior change.
- Typical fixes:
  - extract helpers to reduce cognitive complexity
  - simplify negated conditions
  - replace String#replace() with replaceAll() when global replacement is intended
  - prefer RegExp.exec() when Sonar requests it
Verify locally.
- Minimum when TypeScript code changes:
  - npm run typecheck
  - npm test
  - npm run lint
- If a command fails, fix that before pushing.
Commit and push.
- Use non-interactive git commands only.
- Run:
  - git add <files>
  - git commit -m "<message>"
  - git pull --rebase
  - bd dolt push
  - git push
- If bd dolt push fails because no Dolt remote is configured, do not invent one.
  - Report the exact failure.
  - Create a follow-up Beads issue for the missing Dolt remote if one does not already exist.
  - Still complete git push.
Recheck remote status.
- Confirm branch state:
  - git status --short --branch
- Check GitHub checks for the pushed commit:
  - curl -fsSL "https://api.github.com/repos/<owner>/<repo>/commits/<sha>/check-runs" -H "Accept: application/vnd.github+json"
- Requery SonarCloud:
  - curl -fsSL "https://sonarcloud.io/api/project_pull_requests/list?project=<projectKey>"
  - curl -fsSL "https://sonarcloud.io/api/issues/search?componentKeys=<projectKey>&pullRequest=<prNumber>&ps=100"
Report final state precisely.

Include:
- PR number
- files changed
- local verification results
- pushed commit SHA
- whether SonarCloud has reanalyzed the latest commit yet
- any remaining blocker outside the code changes

Notes

SonarCloud can lag behind GitHub pushes. If SonarCloud still shows an older analysisDate or commit SHA, say so explicitly instead of claiming the issues remain.
GitHub Actions may reveal stricter typecheck failures than npm test if typecheck is not part of the test script. Always run npm run typecheck for TypeScript changes.
Do not close the loop with "ready to push". Push the branch unless the user explicitly tells you not to.

Más de este repositorio

mismo repositorio

cisharpai-expert

alkampfergit/cisharpai

Expert guidance for the Cisharpai .NET library — a unified HttpClient-based interface for OpenAI, Azure OpenAI, Azure AI Inference, Anthropic, and Cohere LLM providers. Use when writing, debugging, or architecting code that uses Cisharpai clients, features, DTOs, DI registration, or provider-specific integrations. Activates on mentions of "Cisharpai", "IChatCompletionClient", "IEmbeddingClient", provider setup, tool calling, streaming, JSON output, grounded chat, vision, embeddings, or fake clients for testing.

2026-05-190

speckit-retrospec

alkampfergit/cisharpai

Reverse-engineer speckit specification files (spec.md, plan.md, and supporting artifacts) from an already-implemented feature in the codebase. Use when the code exists but no speckit specs do. Tasks.md generation is skipped by default (add '--tasks' to include it).

2026-05-150

sonarcloud

alkampfergit/cisharpai

Analyze and fix SonarCloud issues on pull requests. Use when the user mentions SonarCloud, quality gate, code smells, duplication, or wants to check PR quality status. Reads issues via GitHub API, creates fix plans, and applies fixes with awareness of parallel agent safety.

2026-05-060

speckit-gh

alkampfergit/cisharpai

Drive a single GitHub issue through the full speckit pipeline (specify → clarify → plan → tasks → PR-report → draft PR → implement → test → ready → CI → review) using the `gh` CLI. Fully human-in-the-loop — every speckit phase posts its artefact on the issue and polls for owner approval. All user communication stays on the issue / PR threads, never the console. Use when the user says "implement issue

2026-04-300

pr-expert

alkampfergit/cisharpai

Diagnose failing pull request checks across GitHub Actions and external status providers such as SonarCloud and CodeQL. Use when a user asks why a PR is red, which check is blocking merge, why CI passed but the pull request still fails, why branch protection is not satisfied, or what file needs to change to fix a failing status. Determines whether the failing check belongs to github-actions or an external app, traces the exact root cause, and identifies the smallest correct fix.

2026-03-130

SonarCloud PR Fix

Use this skill for PR-scoped SonarCloud cleanup work in this repository.

Goal

Default assumptions

Repo root is the current working directory.

The branch usually has an open GitHub pull request.

This repo uses Beads for task tracking.

The usual SonarCloud project key here is alkampfergit_azdo-cli.

Workflow

Recover repo and branch context.

Read AGENTS.md and CLAUDE.md.
Run git status --short --branch.
Run git rev-parse --abbrev-ref HEAD.
Run bd prime.

Create and claim a Beads issue before editing code.

Example:
- bd create --title "Fix SonarCloud pull request issues" --type bug --priority 1 --label "sonarcloud,quality" --description "..."
- bd update <id> --claim

Resolve the current branch to a GitHub pull request number.

Preferred:
- curl -fsSL "https://api.github.com/repos/<owner>/<repo>/pulls?state=open&head=<owner>:<branch>"
Extract the PR number from the response.
If there is no open PR, stop and tell the user.

Query SonarCloud for PR issues.

Preferred issue query:
- curl -fsSL "https://sonarcloud.io/api/issues/search?componentKeys=<projectKey>&pullRequest=<prNumber>&ps=100"
Also check PR status when needed:
- curl -fsSL "https://sonarcloud.io/api/project_pull_requests/list?project=<projectKey>"
Summarize findings by file, rule, and line before editing.

Inspect the affected code and nearby tests.

Read only the files touched by SonarCloud plus relevant tests.
Prefer targeted fixes over broad refactors.
Watch for CI-only failures such as tsc --noEmit issues that local npm test may miss.

Apply fixes.

Use apply_patch for edits.
Keep behavior stable unless the Sonar issue requires a behavior change.
Typical fixes:
- extract helpers to reduce cognitive complexity
- simplify negated conditions
- replace String#replace() with replaceAll() when global replacement is intended
- prefer RegExp.exec() when Sonar requests it

Verify locally.

Minimum when TypeScript code changes:
- npm run typecheck
- npm test
- npm run lint
If a command fails, fix that before pushing.

Commit and push.

Use non-interactive git commands only.
Run:
- git add <files>
- git commit -m "<message>"
- git pull --rebase
- bd dolt push
- git push
If bd dolt push fails because no Dolt remote is configured, do not invent one.
- Report the exact failure.
- Create a follow-up Beads issue for the missing Dolt remote if one does not already exist.
- Still complete git push.

Recheck remote status.

Confirm branch state:
- git status --short --branch
Check GitHub checks for the pushed commit:
- curl -fsSL "https://api.github.com/repos/<owner>/<repo>/commits/<sha>/check-runs" -H "Accept: application/vnd.github+json"
Requery SonarCloud:
- curl -fsSL "https://sonarcloud.io/api/project_pull_requests/list?project=<projectKey>"
- curl -fsSL "https://sonarcloud.io/api/issues/search?componentKeys=<projectKey>&pullRequest=<prNumber>&ps=100"

Report final state precisely.

Include:

PR number
files changed
local verification results
pushed commit SHA
whether SonarCloud has reanalyzed the latest commit yet
any remaining blocker outside the code changes

Notes

SonarCloud can lag behind GitHub pushes. If SonarCloud still shows an older analysisDate or commit SHA, say so explicitly instead of claiming the issues remain.

GitHub Actions may reveal stricter typecheck failures than npm test if typecheck is not part of the test script. Always run npm run typecheck for TypeScript changes.

Do not close the loop with "ready to push". Push the branch unless the user explicitly tells you not to.