code-quality

Inspect web audio application code for dead code, magic numbers, and type safety issues.

Updated Jan 25, 2026

Search Tags:#code quality #automation #typescript #code review #linting #refactoring

Ready to run

npx skills add https://github.com/acidsound/acidApps --skill code-quality-acidsound

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/acidsound/acidApps/tree/main/skills/code-quality
Command: npx skills add https://github.com/acidsound/acidApps --skill code-quality-acidsound

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jscpd, ts-unused-exports, es6-plato, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenges of maintaining high code quality by providing tools and checks to identify potential issues like dead code, type errors, and inconsistencies, leading to more robust and maintainable applications.

Core Features & Use Cases

Automated Code Inspection: Detects common code quality issues such as unused code, type safety problems, and naming inconsistencies.
Convention Enforcement: Helps enforce coding standards and identify "magic numbers" or hardcoded values.
Use Case: Before merging a new feature, run this skill to ensure the code adheres to project standards, identify any potential bugs related to type safety, and flag areas that might need refactoring.

Quick Start

Run a quick check of the code quality in the src directory.

Frequently Asked Questions about code-quality

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

FAQPage Schema

How do I find dead code and unused exports in a TypeScript project?▼

Automated code quality inspections identify dead code and unused exports in TypeScript projects by analyzing the src directory to detect unreachable logic, type safety issues, and naming inconsistencies.

What's the best way to detect code duplication and refactoring priorities?▼

Detecting code duplication and refactoring priorities is best handled by analyzing file size, function parameters, and nesting depth, using tools like jscpd to highlight complex areas requiring immediate refactoring.

How do I enforce coding standards and identify magic numbers before merging?▼

Enforce coding standards and identify magic numbers before merging by running automated code inspection scripts that detect hardcoded values, type errors, and naming inconsistencies to ensure code adheres to project standards.

Does this code review automation work with web audio applications?▼

Yes, this code review automation works with web audio applications, performing linting and quality checks specifically tailored to identify dead code, type safety issues, and naming inconsistencies within that context.

Can I analyze code complexity metrics like nesting depth and function parameters?▼

You can analyze code complexity metrics like nesting depth and function parameters using es6-plato, which generates reports on file size and structural complexity to suggest targeted refactoring priorities.