skills.rest
leocosta
leocostaCOMMUNITY
Explore all skills by this author →
𝕏@leoccostaGitHub

audit-contracts

Detect API-frontend contract drift in multi-stack monorepos and generate severity-tiered reports.

4|Updated Mar 21, 2026
Search Tags:#frontend#api#openapi#audit#diff#swagger#contracts
One-click install
npx skills add https://github.com/leocosta/octopus --skill audit-contracts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-contracts
Source: https://github.com/leocosta/octopus/tree/main/skills/audit-contracts
Command: npx skills add https://github.com/leocosta/octopus --skill audit-contracts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect API-vs-frontend contract drift in multi-stack monorepos (.NET/Node API + React/Vue/Astro). Given a branch/PR, flags endpoint additions without consumers, removals/renames that break callers, DTO/enum drift, status-code changes, auth-rule changes, and param changes. Severity-tiered report with confidence labels.

Core Features & Use Cases

  • Stack discovery across manifest overrides and autodetection to identify api, app, and lp stacks.
  • Extracts contract changes (endpoints, DTOs, enums, auth rules, and parameters) and correlates them with frontend usage to surface drift.
  • Produces a structured report suitable for PR comments and review, with configurable checks.

Quick Start

Invoke the audit-contracts skill with a branch or PR reference to generate a drift report comparing API and frontend contracts.

Frequently Asked Questions about audit-contracts

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

FAQPage Schema
How do I detect API and frontend contract drift in a monorepo?▼

To detect API and frontend contract drift in a monorepo, you can analyze a branch or PR to flag endpoint additions without consumers, removals that break callers, DTO/enum drift, status-code changes, and auth-rule changes.

What types of API changes cause breaking callers in a frontend stack?▼

Breaking callers in a frontend stack is typically caused by API endpoint removals or renames, DTO/enum drift, status-code changes, auth-rule modifications, and parameter changes that go unconsumed or mismatched.

Can I audit OpenAPI or Swagger contract changes against React or Vue frontends?▼

Yes, you can audit OpenAPI or Swagger contract changes against React or Vue frontends by extracting API endpoint, DTO, and auth rule modifications, then correlating them with frontend usage to surface drift.

How do I generate a PR comment report for API-frontend contract changes?▼

You generate a PR comment report for API-frontend contract changes by running a branch or PR analysis that produces a structured, severity-tiered drift report with confidence labels suitable for review.

Does API contract drift detection work without manifest-driven stack configurations?▼

API contract drift detection works without manifest-driven stack configurations by using autodetection to discover API, app, and LP stacks across multi-stack monorepos during the pre-pass location phase.

What is the best way to prevent breaking frontend callers when modifying API endpoints?▼

The best way to prevent breaking frontend callers when modifying API endpoints is to run a pre-pass drift detection that correlates API removals, renames, and param changes with frontend usage before merging.

Related Skills

Explore More Software Engineering Skills→
reidemeister94reidemeister94
10

eval-regression

Compare working-tree plugin versions against HEAD using parallel evals.

Community
Advanced
ksciuskscius
2

get-pr-comments

Summarize active pull request review comments into a prioritized action list.

Community
Intermediate
jhlee0409jhlee0409
4

openapi-parser

Parse OpenAPI 3.x and Swagger 2.0 specs into structured endpoint catalogs.

Community
Advanced
XSpoonAiXSpoonAi
17

api-contract-diff

Compare OpenAPI and GraphQL schemas to produce categorized JSON diffs.

Official
Advanced