sapcc-audit

Audit Go codebases for SAP Converged Cloud standards and generate a report.

415|44|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/notque/claude-code-toolkit --skill sapcc-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sapcc-audit
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/sapcc-audit
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill sapcc-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit Go codebases for SAP Converged Cloud standards, focusing on over-engineering, dead code, interface contracts, copy-paste patterns, and consistency with project guidelines. It produces actionable findings and enables targeted improvements across a repository.

Core Features & Use Cases

  • Parallel per-package SAPCC rule evaluation with code-level findings
  • Generates a sapcc-audit-report.md at the repo root
  • Each finding includes CURRENT and SHOULD BE with before/after code blocks
  • Non-modifying by default; can run with --fix to apply corrections

Quick Start

Run the sapcc-audit tool against your Go repository to produce a detailed code-review report.

Frequently Asked Questions about sapcc-audit

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

FAQPage Schema
How do I automate a Go code audit for SAP Converged Cloud standards?

Run an automated Go code audit to evaluate your repository against SAP Converged Cloud standards by dispatching parallel per-package checks that generate a detailed report at the repo root.

What does a static analysis code review for over-engineering and dead code include?

A static analysis code review detects over-engineering, dead code, interface contract violations, and copy-paste patterns, providing findings with CURRENT and SHOULD BE sections alongside before and after code blocks.

Can I automatically apply code corrections during a Go repository audit?

Yes, you can automatically apply code corrections during a Go repository audit by executing the process in --fix mode, which modifies the codebase to resolve identified consistency and structural issues.

How do I check Go codebases for interface contracts and copy-paste patterns?

Check Go codebases for interface contracts and copy-paste patterns by running a full-repo audit that evaluates package-level rules and outputs a markdown report detailing necessary structural corrections.

Does the SAPCC audit report modify my existing Go source files by default?

The SAPCC audit report does not modify your existing Go source files by default, but you can enable an optional --fix mode to auto-apply the recommended code corrections.