audit-patterns

Identify and unify inconsistent software implementations across repositories and services.

10|5|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/JHostalek/dotclaude --skill audit-patterns-jhostalek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-patterns
Source: https://github.com/JHostalek/dotclaude/tree/main/skills/audit-patterns
Command: npx skills add https://github.com/JHostalek/dotclaude --skill audit-patterns-jhostalek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies inconsistent implementations, duplicated utilities, naming violations, import disorder, and architectural drift that make software behavior unpredictable and increase maintenance costs.

Core Features & Use Cases

  • Systematic Pattern Audits: Compare recurring concerns across architecture, domain models, interfaces, data access, failures, operations, dependencies, tests, and delivery tooling.
  • Evidence-Based Convergence: Distinguish actual defects and worthwhile improvements from intentional variants, migrations, generated code, external contracts, and unresolved questions.
  • Safe Remediation Guidance: Define violated invariants, affected call paths, realistic consequences, target patterns, migration implications, approval boundaries, and verification methods.
  • Use Case: Apply the Skill to a repository where multiple services implement retries, validation, logging, or serialization differently and need a consistent, justified target without collapsing legitimate domain distinctions.

Quick Start

Ask the audit-patterns skill to review the specified path for inconsistent implementations and reimplementations, classify each divergence, and document evidence-backed fixes.

Frequently Asked Questions about audit-patterns

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

FAQPage Schema
How do I unify inconsistent code patterns across multiple services without flattening domain semantics?

Auditing inconsistent software implementations requires comparing recurring concerns like retries and validation across repositories, distinguishing actual defects from intentional domain variants to establish a justified target architecture.

What is architectural drift and how do I identify duplicated implementations causing maintenance issues?

Architectural drift occurs when duplicated utilities and inconsistent implementations cause unpredictable behavior, identified by systematically auditing data flows, interfaces, and operational modes across modules to isolate defects.

How do I audit code conventions and pattern consistency across repositories and delivery tooling?

Auditing code conventions and pattern consistency involves comparing semantics, invariants, and failure behavior across repositories, services, and delivery tooling to document evidence-backed corrections and approval boundaries.

Can I review refactoring targets across microservices while preserving intentional platform variants?

You can review refactoring targets across microservices while preserving intentional platform variants by comparing ownership, concurrency, and observability to classify divergences and document safe remediation guidance.

What's the best way to document safe code corrections and verification methods for architectural inconsistencies?

Documenting safe code corrections for architectural inconsistencies requires defining violated invariants, affected call paths, migration implications, approval boundaries, and verification methods backed by concrete evidence.

When should I not unify inconsistent implementations during a code audit?

Avoid unifying inconsistent implementations during a code audit when divergences represent intentional domain distinctions, migrations, generated code, external contracts, or unresolved questions requiring preserved variants.