skills.rest
blakecyze
blakecyzeCOMMUNITY
Explore all skills by this author →
Website𝕏@cyze_devGitHub

kanso-audit

Audit codebases for correctness, clarity, consistency, and architectural issues.

2|Updated Apr 23, 2026
Search Tags:#quality assurance#static analysis#code review#refactoring#audit#technical debt
One-click install
npx skills add https://github.com/blakecyze/kanso --skill kanso-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kanso-audit
Source: https://github.com/blakecyze/kanso/tree/main/skills/kanso-audit
Command: npx skills add https://github.com/blakecyze/kanso --skill kanso-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates code review noise by focusing on structural integrity, maintainability, and correctness, preventing the accumulation of technical debt and anti-patterns.

Core Features & Use Cases

  • Multi-Tiered Analysis: Categorizes findings into blockers, important architectural issues, and polish, ensuring focus remains on high-impact improvements.
  • Adversarial Review: Actively probes code for edge cases, security vulnerabilities, and logic errors using an adversarial lens.
  • Integrated Workflow: Provides a seamless approval gate that routes refactors to specialized tools and applies behaviour changes inline with verification.

Quick Start

Invoke the audit skill to review the current branch for structural issues and potential bugs.

Frequently Asked Questions about kanso-audit

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

FAQPage Schema
How do I perform a code review that focuses on structural integrity and architectural issues?▼

A static code audit identifies correctness, clarity, consistency, and architectural issues within a codebase. It analyzes diffs, branches, or modules to surface high-priority findings and proposes concrete, verifiable fixes to prevent technical debt.

How do I audit a git branch for technical debt and anti-patterns?▼

You audit a git branch for technical debt by analyzing the diff or module to identify blockers, important architectural issues, and polish opportunities. This enforces anti-dilution principles to ensure maintainability without introducing unnecessary complexity.

Can I use an adversarial code review to find logic errors and security vulnerabilities?▼

Yes, adversarial code review actively probes code for edge cases, security vulnerabilities, and logic errors. It uses an adversarial lens to identify potential bugs and structural weaknesses that standard reviews might miss.

What is the best way to categorize code review findings to avoid noise?▼

The best way to avoid code review noise is using a multi-tiered analysis system. This categorizes findings into blockers, important architectural issues, and polish, ensuring focus remains on high-impact improvements.

Does static analysis work for refactoring code and routing changes to specialized tools?▼

Static analysis supports refactoring by providing an integrated workflow approval gate. This routes refactors to specialized tools and applies behaviour changes inline with verification to maintain code quality.

Related Skills

Explore More Software Engineering Skills→
zhu327zhu327
2

code-review-expert

Review Git diffs for structural regressions, security risks, and maintainability issues.

Community
Advanced
zm2231zm2231

code-refactoring

Refactor code to improve quality, readability, and maintainability.

Community
Advanced
HomericIntelligenceHomericIntelligence
18

detect-code-smells

Detect code smells and complexity issues in codebases.

Official
Intermediate
ClipboardHealthClipboardHealth
66

simplify

Analyze code diffs or modules for reuse, quality, and efficiency improvements.

Official
Advanced