gap

Audit cross-repository integration health and automate remediation.

3|1|Updated Oct 9, 2025

Search Tags:#code quality #automation #ci/cd #integration #drift detection #audit #health check

Ready to run

npx skills add https://github.com/OmniNode-ai/omniclaude --skill gap

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gap
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/gap
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill gap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill identifies and helps resolve integration drift and architectural violations across multiple repositories, ensuring system health and preventing silent breakages.

Core Features & Use Cases

Cross-Repo Auditing: Detects drift in Kafka topics, database schemas, API contracts, and more across your services.
Automated Fixing: Attempts to automatically fix common integration issues like legacy configuration or stale branch protection rules.
Full Cycle Orchestration: Manages the entire detect-fix-verify loop for comprehensive integration health checks.
Use Case: Before deploying a new feature that spans several microservices, run the gap cycle command to ensure all inter-service contracts and configurations are aligned, preventing runtime integration failures.

Quick Start

Run the gap skill to audit cross-repo integration health for epic OMN-2500.

Frequently Asked Questions about gap

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

FAQPage Schema

How do I detect cross-repository integration drift across microservices?▼

Cross-repository integration drift is detected by auditing Kafka topics, database schemas, and API contracts across services. The audit identifies contract mismatches, architectural violations, and integration health issues to prevent silent breakages.

Can I automate fixing legacy configuration and stale branch protection rules?▼

Yes, you can automate fixing legacy configuration and stale branch protection rules through the automated fixing mode. This mode attempts to resolve common integration issues and remediate drift across repositories automatically.

What is the best way to verify API contract alignment before a multi-service deployment?▼

The best way to verify API contract alignment is running a full cycle orchestration that manages the detect-fix-verify loop. This ensures inter-service contracts and configurations are aligned across repositories, preventing runtime integration failures.

Does cross-repo auditing work for finding Kafka topic and database schema mismatches?▼

Yes, cross-repo auditing works for finding Kafka topic and database schema mismatches. It comprehensively detects drift across these integration points alongside API contracts to maintain overall system health.

How do I create automated tickets for architectural violations found during an audit?▼

You create automated tickets for architectural violations by running a cross-repo audit with detailed reporting enabled. This generates actionable insights and automatically creates tickets for identified integration health issues.