auditing-libraries

Audit local and package libraries for convention violations and report issues.

1|Updated Oct 21, 2016
One-click install
npx skills add https://github.com/jasonkuhrt/dotfiles --skill auditing-libraries
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auditing-libraries
Source: https://github.com/jasonkuhrt/dotfiles/tree/main/claude/todo/library-standards/skills/auditing-libraries
Command: npx skills add https://github.com/jasonkuhrt/dotfiles --skill auditing-libraries

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auditing libraries for conformance to defined namespace and structural conventions, identifying violations and guiding fixes.

Core Features & Use Cases

  • Audit Single Library: Check one library for namespace and barrel patterns and report violations.
  • Audit All Libraries: Scan all libraries in the project and aggregate results.
  • Fix Violations: Propose and apply fixes to resolve detected issues.

Quick Start

Run the auditing-libraries skill against a library directory to generate a violation report.

Frequently Asked Questions about auditing-libraries

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

FAQPage Schema
How do I audit TypeScript libraries for namespace and barrel export convention violations?▼

To audit TypeScript libraries for namespace and barrel export violations, run the auditing-libraries skill against a library directory. It checks library structure, namespace module integrity, cross-file references, and test import consistency, producing a structured audit report.

What is the _.ts and __.ts namespace pattern for library structure?▼

The _.ts and __.ts namespace pattern defines a structural convention for local and package libraries. The auditing skill checks codebases using these patterns to ensure proper namespace exports, barrel integrity, and consistent cross-file references.

Can I scan all libraries in a project for convention violations at once?▼

Yes, you can scan all libraries in a project for convention violations at once. The audit all libraries feature scans the entire project, aggregating results for namespace exports, barrel integrity, and test import consistency into a single structured report.

How do I fix namespace export and barrel integrity issues detected during an audit?▼

To fix namespace export and barrel integrity issues detected during an audit, the skill proposes and applies fixes to resolve the violations. This addresses structural problems, cross-file references, and test import inconsistencies found in the audit report.

Why do I need to audit library structure and test import consistency?▼

You need to audit library structure and test import consistency to maintain codebase conventions. Auditing identifies violations in namespace exports, barrel integrity, and cross-file references, ensuring local and package libraries conform to defined structural patterns.