engineering-audit

Audit the Teqo codebase for code smells and architectural drift.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/fsolla/teqo --skill engineering-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engineering-audit
Source: https://github.com/fsolla/teqo/tree/main/.cursor/skills/engineering-audit
Command: npx skills add https://github.com/fsolla/teqo --skill engineering-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses technical debt, architectural drift, and code duplication by performing a rigorous, multi-pass audit of the codebase to ensure it adheres to established engineering standards.

Core Features & Use Cases

  • Code-Smell Detection: Identifies bloaters, couplers, and change preventers based on Fowler families and Teqo-specific standards.
  • Consolidation Hunt: Pinpoints opportunities to merge near-duplicate components and logic into unified, parameterizable abstractions.
  • Recurrence Prevention: Classifies deterministic guardrails for every finding to ensure issues do not reappear in future development.

Quick Start

Run the engineering audit skill to perform a full codebase sweep and generate a remediation plan for identified technical debt.

Frequently Asked Questions about engineering-audit

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

FAQPage Schema
How do I identify code smells and architectural drift in my codebase?

A code-smell sweep detects bloaters, couplers, and change preventers based on Fowler families to identify technical debt. It evaluates your repository against documented engineering standards to produce a findings ledger for architectural drift.

What is the best way to find opportunities to consolidate duplicate code components?

Consolidation hunting pinpoints opportunities to merge near-duplicate components and logic into unified, parameterizable abstractions. This refactoring approach eliminates code duplication and reduces architectural drift across the codebase.

How do I generate a remediation plan for technical debt?

An engineering audit generates a remediation plan by evaluating the codebase against operational patterns and engineering standards. It produces a findings ledger detailing identified technical debt and actionable steps to resolve code smells.

How can I prevent code smells from recurring after refactoring?

Prevent code smells from recurring by classifying deterministic guardrails for every audit finding. This structural analysis enforces engineering standards to ensure issues do not reappear during future development.

Can I automate a full codebase audit for technical debt without external dependencies?

You can automate a full codebase audit for technical debt without external dependencies. The engineering audit performs a rigorous multi-pass sweep internally to identify code smells, architectural drift, and consolidation opportunities.