Menu
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/notque/vexjoy-agent --skill sapcc-auditThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
Run the full evidence-to-live implementation workflow for large, multi-system, multi-wave, or CPU-delegated 5 Star Booker GM programs.
Classify user requests and route to the correct agent + skill. Primary entry point for all delegated work.
Structured multi-phase workflows: review, debug, refactor (tidy, clean up, untangle messy code without behaviour change), deploy, create, research.
Based on SOC occupation classification
| name | sapcc-audit |
| description | Full-repo SAP CC Go compliance audit against review standards. |
| user-invocable | false |
| command | /sapcc-audit |
| agent | golang-general-engineer |
| allowed-tools | ["Read","Write","Bash","Grep","Glob","Edit","Task","Skill"] |
| routing | {"not_for":"deep 10-specialist parallel review of specific files (use sapcc-review). This skill is full-repo compliance scan; multi-perspective code review with newcomer/senior/pedant views (use reviewer-perspectives agent)","triggers":["sapcc audit","sapcc compliance","check sapcc rules","full repo audit","sapcc standards check"],"pairs_with":["golang-general-engineer","golang-general-engineer-compact","go-patterns"],"force_route":false,"complexity":"Complex","category":"language"} |
Review every package against established review standards. Not checklist compliance — code-level review that finds over-engineering, dead code, interface violations, and inconsistent patterns.
| Signal | Load This File | When |
|---|---|---|
| Phase 1 begins | references/phase-1-discover-commands.md | Detection commands, package mapping, segmentation table |
| Phase 2 begins | references/phase-2-dispatch-agents.md | Full dispatch prompt and per-domain review checklist (11 areas) |
| Phase 3 begins | references/output-templates.md | Report scaffold, per-finding format, severity guide |
Load each reference file at the start of its phase. Do not load all three upfront.
Goal: Map the repository and plan the package segmentation.
Read references/phase-1-discover-commands.md for the exact detection commands, segmentation table, and file-count queries.
Verify this is an sapcc project (sapcc imports in go.mod). If not, stop immediately.
Map all packages, count files per package, and produce a segmentation table (5–8 agents, 5–15 files each).
Gate: Packages mapped, agents planned. Proceed to Phase 2.
Goal: Launch parallel agents that review packages against project standards.
Read references/phase-2-dispatch-agents.md for the full dispatch prompt (11 review areas: over-engineering, dead code, error messages, constructors, interface contracts, copy-paste, HTTP handlers, database patterns, type patterns, logging, mixed approaches).
Use the standard dispatch prompt verbatim, substituting the assigned package list.
Dispatch all agents in a single message using the Task tool with subagent_type=golang-general-engineer.
Gate: All agents dispatched. Proceed to Phase 3.
Goal: Aggregate findings into a code-level compliance report.
Read references/output-templates.md for the report scaffold, per-finding format, and deduplication rules.
Deduplicate by file:line. Write sapcc-audit-report.md. Display verdict, must-fix count, and top 5 findings inline.
Gate: Report complete.
| Scenario | Response |
|---|---|
| Not an sapcc project | Stop immediately. Print: "This does not appear to be an SAP CC Go project (no sapcc imports in go.mod)." |
| Agents cannot read a file | Log and continue. Flag in the report under "Warnings." |
| gopls MCP tools unavailable | Fall back to manual grep-based analysis. Note in the report. |
| Too many packages (>30) | Split into >8 agents. Ensure each still gets 5-15 files. |
| Agent finds no violations | Report is valid. Output empty sections for unused severity levels. |
Audit only: READS and REPORTS. Does NOT modify code unless explicitly asked with --fix.
/do routes via "sapcc audit", "sapcc compliance", "sapcc lead review"go-patterns (the rules), golang-general-engineer (the executor)| Package Type | Reference to Load |
|---|---|
HTTP handlers (internal/api/) | api-design-detailed.md |
Test files (*_test.go) | testing-patterns-detailed.md |
| Error handling heavy packages | error-handling-detailed.md |
| Architecture/drivers | architecture-patterns.md |
| Build/CI config | build-ci-detailed.md |
| Import-heavy files | library-reference.md |
Always available for calibration (load only when needed): quality-issues.md, review-standards-lead.md.