check-mechanical-constraints

Validate linter rules, boundary schemas, and forbidden imports in code projects.

18|11|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/Intense-Visions/harness-engineering --skill check-mechanical-constraints
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-mechanical-constraints
Source: https://github.com/Intense-Visions/harness-engineering/tree/main/agents/skills/claude-code/check-mechanical-constraints
Command: npx skills add https://github.com/Intense-Visions/harness-engineering --skill check-mechanical-constraints

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Check Mechanical Constraints automates enforcement of repository-level machine-checkable rules, preventing architectural drift by validating linter rules, boundary schemas, and forbidden imports.

Core Features & Use Cases

  • Phase-based validation using harness validate, harness linter validate, and harness check-deps to catch structure and dependency issues.
  • Enforces architectural boundaries during pre-commit and PR reviews to maintain project integrity.
  • Provides deterministic, rule-based feedback to guide remediation after code generation or refactoring.

Quick Start

Run harness skill run check-mechanical-constraints to execute all mechanical constraint checks against a project root.

Frequently Asked Questions about check-mechanical-constraints

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

FAQPage Schema
How do I enforce mechanical constraints and prevent architectural drift in a codebase?

You can enforce mechanical constraints by running automated validation phases via harness validate, harness linter validate, and harness check-deps to deterministically detect file structure, style, and dependency violations.

What is the best way to validate forbidden imports and boundary schemas before a commit?

Pre-commit mechanical constraint validation enforces architectural boundaries by running deterministic checks against boundary schemas and forbidden imports, providing rule-based feedback to guide remediation before code is merged.

How do I run deterministic checks for linter rules and file structure violations?

Executing harness skill run check-mechanical-constraints applies all mechanical constraint checks against a project root, utilizing harness linter validate and harness check-deps to catch structural and dependency issues.

Does this mechanical constraint validation work after code generation and refactoring?

Yes, mechanical constraint validation provides deterministic, rule-based feedback to guide remediation specifically after code generation or refactoring, ensuring newly created code adheres to repository-level machine-checkable rules.

What are the limitations of automating mechanical constraint enforcement in software engineering?

This approach implements deterministic, machine-checkable rules limited to detecting file structure, style, and architectural violations, and does not assess semantic code logic or functional correctness outside of defined linter and dependency schemas.