go-clearpath-auditor

Audit Go code for ClearPath style compliance and generate a read-only report.

1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/mikeschinkel/ai-agent-depot --skill go-clearpath-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-clearpath-auditor
Source: https://github.com/mikeschinkel/ai-agent-depot/tree/main/skills/go-clearpath-auditor
Command: npx skills add https://github.com/mikeschinkel/ai-agent-depot --skill go-clearpath-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audits Go code for compliance with ClearPath style and related non-negotiables, producing an actionable, read-only report without modifying source files.

Core Features & Use Cases

  • Enforces ClearPath structural rules and non-negotiables in production Go code.
  • Generates a detailed findings report with suggested diffs and concrete remediation steps.
  • Works on user-specified files or entire packages, prioritizing production code and avoiding test files.

Quick Start

Run the go-clearpath-auditor on your Go module to generate a read-only compliance report.

Frequently Asked Questions about go-clearpath-auditor

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

FAQPage Schema
How do I audit Go code for ClearPath compliance?

You can audit Go code for ClearPath compliance by running the auditor on your Go module to generate a detailed, read-only report of style and structural violations. It analyzes full packages or specific files without modifying source.

Does the Go code auditor modify my source files during static analysis?

No, the Go code auditor does not modify source files during static analysis. It produces a read-only compliance report containing violation findings, guidance, and suggested diffs, preserving your original code.

Can I run a static analysis audit on specific Go files instead of a full package?

Yes, you can run the static analysis audit on user-specified Go files or entire packages. The auditor prioritizes production code and actively avoids test files during the compliance review.

What does the ClearPath compliance report include for Go code violations?

The ClearPath compliance report includes flagged violations for nested control structures and non-negotiables. It provides actionable remediation steps, guidance, and suggested diffs to help fix the identified code quality issues.

When should I use a code quality auditor for Go production code?

You should use a code quality auditor for Go production code when you need to enforce structural rules and non-negotiables. It helps identify nested control structures and style violations before deployment.

Are there limitations to using static analysis for Go code quality reporting?

A limitation of this static analysis approach is its focus on ClearPath structural rules and non-negotiables, meaning it primarily targets production Go code and avoids test files rather than providing general-purpose linting.