skills.rest
PacificStudio
PacificStudioOFFICIAL
Explore all skills by this author →
GitHub

auto-harness

Audit repository harness drift and generate guardrails for contract coherence.

264|27|Updated Mar 19, 2026
Search Tags:#architecture#audit#drift#contracts#guardrails#ci#harness
One-click install
npx skills add https://github.com/PacificStudio/openase --skill auto-harness
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-harness
Source: https://github.com/PacificStudio/openase/tree/main/internal/builtin/skills/auto-harness
Command: npx skills add https://github.com/PacificStudio/openase --skill auto-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

OpenASE's Auto Harness provides a structured approach to detect and fix drift in repository harness rules, aligning AGENTS.md, docs, lint/type gates, API contracts, tests, and observability.

Core Features & Use Cases

  • Central drift auditing: map where semantics drift across layers and propose durable guardrails.
  • Guardrail generation: produce generated artifacts, tests, and CI gates that enforce contracts and boundaries.
  • CI-ready deliveries: deliver a prioritized fix plan, drift risks, and residual gaps for teams to act on.

Quick Start

Run a harness audit on your repository to generate a drift risk report and a prioritized guardrail plan.

Frequently Asked Questions about auto-harness

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

FAQPage Schema
How do I detect architecture drift across multiple repositories?▼

Repository harness drift occurs when rules, API contracts, and boundaries diverge across code, docs, lint gates, and tests. It is detected through a central audit that maps these semantic inconsistencies and proposes durable guardrails to realign the ecosystem.

How do I generate CI guardrails to enforce API contract coherence?▼

To enforce contract coherence, the audit generates artifacts, tests, and CI gates that act as guardrails. These deliver CI-ready diagnostics and a prioritized fix plan, ensuring boundaries are enforced directly within your continuous integration pipeline.

Can I audit contract drift in a multi-repo ecosystem using a central authority model?▼

Yes, you can audit contract drift in a multi-repo ecosystem using a central authority model. The audit enforces contract coherence across code, docs, and tests, detecting drift and enabling CI-ready diagnostics for remediation.

What is the best way to align AGENTS.md, docs, and lint rules when they drift?▼

The best way to align AGENTS.md, docs, and lint rules is to apply a structured harness audit that detects drift across these layers. It generates a prioritized guardrail plan and tests to remediate inconsistencies and enforce boundaries.

What are the limitations of relying on manual reviews for repository harness drift?▼

Manual reviews for repository harness drift lack CI-ready diagnostics and generated guardrails, leaving residual gaps in contract coherence. Without a central audit to map semantic drift, multi-repo ecosystems risk undetected boundary violations and inconsistent gates.

Related Skills

Explore More Software Engineering Skills→
8Dionysus8Dionysus
4

aoa-bounded-context-map

Map bounded contexts with interface notes and vocabulary recommendations.

Community
Intermediate
Arnutt-NArnutt-N

security-scanner

Detect OWASP Top 10 risks and misconfigurations in HR-IMS code.

Community
Advanced
YusufkotavomYusufkotavom

testing-quality-gates

Run lint, type-check, and tests across scoped changes for pre-commit or CI workflows.

Community
Advanced
rshadershade
3

lint-fix

Detect project linting tools and assemble a zero-error execution pipeline.

Community
Advanced