audit-codebase

Name: audit-codebase
Availability: InStock
Author: sambeau

Audit Go codebases with static analysis, structural queries, and style checks.

5|Updated Mar 18, 2026

Search Tags:#linting #codebase #audit #static-analysis #triage #dead-code #go-style

Ready to run

npx skills add https://github.com/sambeau/kanbanzai --skill audit-codebase-sambeau

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: audit-codebase
Source: https://github.com/sambeau/kanbanzai/tree/main/.kbz/skills/audit-codebase
Command: npx skills add https://github.com/sambeau/kanbanzai --skill audit-codebase-sambeau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This audit helps teams identify quality issues across the entire codebase without requiring a formal spec. It detects dead code, linting/style deviations, and performance concerns that threaten release readiness.

Core Features & Use Cases

Static analysis with go vet and staticcheck to surface correctness issues.
Knowledge-graph–based structural queries to identify dead code, change coupling, and risky dependencies.
Go style conformance checks and triage-driven reporting; outputs a triage-ready audit report saved to work/reviews/.

Use cases include pre-release validation, post-refactor health checks, and on-demand quality sweeps across large codebases.

Quick Start

Start a full-codebase audit to generate a triage-ready report saved to work/reviews/.

Frequently Asked Questions about audit-codebase

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

FAQPage Schema

How do I perform a comprehensive codebase audit for a large Go repository?▼

Perform a comprehensive codebase audit by running static analysis, knowledge-graph structural queries, and Go style conformance checks to detect dead code and linting deviations. It generates a triage-ready report saved to work/reviews/ to guide developers in fixing critical issues.

What is the best way to check for dead code and risky dependencies before a Go release?▼

The best way to check for dead code and risky dependencies before a Go release is using knowledge-graph structural queries combined with static analysis. This identifies change coupling and risky dependencies, producing a triage-ready audit report for pre-release validation.

Can I use staticcheck and go vet for automated post-refactor health checks?▼

Yes, you can use staticcheck and go vet for automated post-refactor health checks. The audit applies these static analysis tools alongside Go style conformance checks to surface correctness issues and generate a triage-ready report for post-refactor health verification.

Does this codebase audit require a formal spec to identify quality issues?▼

No, this codebase audit does not require a formal spec to identify quality issues. It detects dead code, linting style deviations, and performance concerns that threaten release readiness by directly analyzing the repository structure and applying static analysis rules.

What is included in a triage-ready audit report for static analysis and Go style conformance?▼

A triage-ready audit report includes findings from static analysis and Go style conformance checks, highlighting dead code, correctness issues, and performance concerns. Saved to work/reviews/, it guides developers directly to fix critical issues identified during the quality sweep.