code-quality

Name: code-quality
Availability: InStock
Author: Theo

Detect code-quality issues across Go, Python, TypeScript, and Rust.

Updated May 13, 2026

Search Tags:#auditing #multi-language #detection #code-quality #dead-code #mutation-testing #symbol-fabrication

Ready to run

npx skills add https://github.com/usetheodev/theo-ui --skill code-quality-usetheodev

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tree-sitter>=0.25,<0.26, tree-sitter-languages>=1.10,<2.0, requests>=2.32,<3.0, pyyaml>=6.0,<7.0, and includes scripts (resource) components.

What problem does it solve?

Audits code quality across multiple languages (Go, Python, TypeScript, and Rust) to surface dead code, fabricated APIs, cross-package wiring issues, and weak test quality, helping teams ship safer software faster.

Core Features & Use Cases

Detects dead code across multiple languages (D1) using language-specific detectors.
Validates symbol fabrication via tree-sitter + registry lookups (D2) and flags unverified imports.
Checks cross-package wiring for orphan exports (D3) and surfaces soft-caps to guide remediation.
Supports mutation testing (D4) tailored to an implementation plan's Critical paths and can bind audits to plans.
Generates machine-readable JSON verdicts and optional Markdown audit reports for plan-confidence workflows.

Quick Start

Run a standalone audit or bind to a plan to begin an end-to-end code-quality gate across your repository.

Frequently Asked Questions about code-quality

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

FAQPage Schema

How do I detect dead code across multiple languages like Go, Python, TypeScript, and Rust?▼

To detect dead code across Go, Python, TypeScript, and Rust, you can run a multi-language audit that orchestrates per-language detectors to identify unused exports and output structured JSON verdicts.

What is symbol fabrication detection and how does tree-sitter validate imports?▼

Symbol fabrication detection uses tree-sitter parsing combined with registry lookups to validate imports, flagging unverified or fabricated APIs that do not exist in the project's dependencies.

How do I run mutation testing bound to critical implementation paths?▼

You can run mutation testing bound to critical paths by integrating external tools like mutmut or stryker, which evaluate test quality specifically against the implementation plan's defined routes.

Can I use vulture and knip for cross-package wiring checks in a monorepo?▼

Yes, vulture and knip act as language-specific detectors to check cross-package wiring, surfacing orphan exports and providing soft-caps to guide remediation across Python and TypeScript packages.

Does the audit support standalone execution or does it require binding to a plan?▼

The audit supports both standalone execution for general code-quality checks and plan-bound audits that specifically evaluate risk against a plan's critical paths configured in the .claude/rules directory.

What are the limitations of using cargo-udeps and deadcode for code-quality auditing?▼

Limitations include reliance on external tools like cargo-udeps and deadcode, requiring specific dependency version constraints and proper manifest auto-detection to accurately emit structured Markdown audit reports.