gemini-auditor

Interpret SonarCloud reports and generate file-specific code fixes.

Updated Nov 8, 2022
One-click install
npx skills add https://github.com/gvinokur/qatar-prode --skill gemini-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gemini-auditor
Source: https://github.com/gvinokur/qatar-prode/tree/main/.gemini/skills/gemini-auditor
Command: npx skills add https://github.com/gvinokur/qatar-prode --skill gemini-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill interprets SonarCloud static-analysis output and audits repository structural documentation against the actual code changes in a pull request, reducing manual review effort and preventing documentation drift.

Core Features & Use Cases

  • SonarCloud interpretation: Parse provided SonarCloud findings, categorize by severity, and produce clear, human-readable summaries with concrete, file-and-line-specific fix suggestions.
  • Documentation audit (The Librarian): Use git diffs to identify new or changed functions and components, read CODE-STRUCTURE.md and related layer docs, verify signatures and Calls:/Renders: lines, and list missing or inaccurate documentation entries.
  • Actionable reporting: Return two structured sections for the caller — prioritized SonarCloud feedback with suggested code fixes, and a documentation audit checklist with exact edits required to synchronize docs with code.
  • Use Case: When a PR is marked ready, run this skill as a subagent to convert CI-provided SonarCloud output and the PR diff into prioritized fixes and documentation updates.

Quick Start

Analyze the provided SonarCloud report and PR diff, then return prioritized code fixes and a checklist of required documentation updates.

Frequently Asked Questions about gemini-auditor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix SonarCloud issues found in my pull request?

To fix SonarCloud issues in a pull request, you can parse the CI-provided SonarCloud output and map the findings to specific code locations to generate prioritized, file-and-line-specific code fixes.

What is the best way to keep documentation synced with code changes?

Keeping documentation synced with code changes requires auditing git diffs to identify modified functions and verifying structural documentation entries like CODE-STRUCTURE.md against the actual code updates to produce a checklist of required edits.

How do I automate code audits for pull requests using SonarCloud reports?

Automating code audits for pull requests involves passing SonarCloud static-analysis output and repository git diff context to an agent, which then categorizes findings by severity and returns actionable code fix suggestions.

Does this documentation audit process work with standard git diff context?

Yes, the documentation audit process works with standard git diff context by reading the diffs to identify new or changed functions and components, then verifying signatures and structural documentation entries against those code changes.

What do I need to generate documentation updates from a SonarCloud report?

To generate documentation updates from a SonarCloud report, you need the SonarCloud output in the prompt, read access to repository files, git diff context, and the repository's structural documentation to synchronize with code changes.