ln-643-api-contract-auditor

Audit API contracts across service boundaries for layer leakage and DTO misuse.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/0xtaoist/taogate --skill ln-643-api-contract-auditor-0xtaoist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ln-643-api-contract-auditor
Source: https://github.com/0xtaoist/taogate/tree/main/ln-643-api-contract-auditor
Command: npx skills add https://github.com/0xtaoist/taogate --skill ln-643-api-contract-auditor-0xtaoist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Checks architecture-level API contracts across service boundaries to prevent layer leakage, ensure proper DTO usage, and enforce consistent error contracts.

Core Features & Use Cases

  • Audits API contracts at architecture level to detect leakage between services and domains.
  • Verifies DTO presence and consistent error-handling patterns; reports findings with a penalty-based score.
  • Generates four scores (compliance, completeness, quality, implementation) and a structured findings report for remediation.
  • Supports domain-aware scans and writes per-domain reports to the configured output directory.

Quick Start

Run the API Contract Auditor against your codebase to produce a formal report in the designated output path.

Frequently Asked Questions about ln-643-api-contract-auditor

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

FAQPage Schema
How do I audit API contracts to detect layer leakage across service boundaries?▼

To audit API contracts for layer leakage, apply an architecture-level scanner to your API and service directories to identify cross-boundary violations and generate a penalty-based score with structured findings for remediation.

What is a penalty-based score in API contract auditing?▼

A penalty-based score in API contract auditing evaluates architectural integrity by calculating four metrics—compliance, completeness, quality, and implementation—based on detected issues like missing DTOs and inconsistent error contracts.

How do I check for missing or misused DTOs in my service directories?▼

To check for missing or misused DTOs, run a domain-aware contract audit across your service directories to verify DTO presence and produce a domain-tagged report detailing completeness and quality scores.

Does API contract auditing support domain-aware scans for isolated reporting?▼

Yes, API contract auditing supports domain-aware scans that analyze specific domain layers and write per-domain structured findings reports to your configured output directory for targeted remediation.

What's the best way to enforce consistent error contracts across multiple domain layers?▼

The best way to enforce consistent error contracts is to perform an architecture-level audit across service boundaries to detect pattern inconsistencies and generate a compliance score with a detailed domain-tagged report.