enterprise-harness

Run a 10-check quality gate on code before merging.

1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/anotherben/claude-enterprise-skills --skill enterprise-harness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enterprise-harness
Source: https://github.com/anotherben/claude-enterprise-skills/tree/main/skills/enterprise-harness
Command: npx skills add https://github.com/anotherben/claude-enterprise-skills --skill enterprise-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill acts as a critical, automated quality assurance gate, ensuring code meets stringent enterprise standards before being merged, preventing regressions and maintaining code integrity.

Core Features & Use Cases

  • Automated Checks: Executes 10 distinct checks covering contract adherence, test coverage, import resolution, data shape consistency, build success, file size limits, debug artifacts, and code patterns.
  • Unbiased Evaluation: Runs after code is built, preventing the builder from gaming the checks.
  • Use Case: Before merging a new feature branch for user authentication, this Skill verifies that all contract postconditions are met by tests, that no new test failures were introduced, that all imports resolve correctly, and that no debug statements are present in the code.

Quick Start

Run the enterprise-harness skill to verify the code on the 'feature/new-auth' branch against the 'main' branch.

Frequently Asked Questions about enterprise-harness

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

FAQPage Schema
How do I run automated code quality checks before merging a feature branch?

You can run automated code quality checks by executing this Skill against your feature branch and a main branch. It orchestrates a 10-check quality gate validating test coverage, imports, data shapes, and build success before merging.

What is a CI/CD quality gate for code review and how does it prevent regressions?

A CI/CD quality gate for code review is an automated validation step that ensures code meets enterprise standards before merging. This Skill evaluates contract adherence, test execution, and code patterns post-build to prevent regressions and maintain integrity.

Can I validate test coverage against postconditions and check for debug artifacts simultaneously?

Yes, you can validate test coverage against postconditions and check for debug artifacts simultaneously. The Skill's automated checks include verifying test coverage, test execution results, and confirming the absence of debug statements in your code.

Does this automated validation tool support checking import resolution and frontend build success?

Yes, this automated validation tool supports checking import resolution and frontend build success. It operates on specified branches and task slugs to verify import resolution, data shape consistency, and frontend build success for production-readiness.

What is the best way to gatekeep code generated by builder agents before merging?

The best way to gatekeep code generated by builder agents is to run this Skill after the code is built. It provides an unbiased evaluation by executing 10 distinct checks, preventing the builder from gaming the validation process before merging.

Why does my code merge fail validation due to uncommitted files or file size limits?

Your code merge fails validation because the quality gate checks for uncommitted files and enforces file size limits. It ensures production-readiness by identifying uncommitted files and rejecting code that exceeds specified file size constraints.