portable-contract-normalizer

Detect machine-local path assumptions in bounded code surfaces and report findings.

4|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/danielbaustin/agent-design-language --skill portable-contract-normalizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: portable-contract-normalizer
Source: https://github.com/danielbaustin/agent-design-language/tree/main/adl/tools/skills/portable-contract-normalizer
Command: npx skills add https://github.com/danielbaustin/agent-design-language --skill portable-contract-normalizer

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Bounded codebases often embed machine-specific paths, user homes, and environment cues that break portability across machines. This skill detects absolute host paths, brittle worktrees, machine-local temp paths, stale contract references, and environment-specific assertions, then reports findings or applies narrowly scoped mechanical normalizations.

Core Features & Use Cases

  • Detect portable surface defects in contracts, tests, review packets, and validation artifacts within a bounded repository.
  • Provide safe, mechanical normalization when operator-approved, replacing host-specific fixtures with portable placeholders.
  • Generate Markdown and JSON artifacts suitable for reviews and compliance evidence, or guidance for design decisions.

Quick Start

Run the portable-contract-normalizer over a bounded repository root to scan for portability issues and optionally apply safe fixes.

Frequently Asked Questions about portable-contract-normalizer

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

FAQPage Schema
How do I detect absolute host paths and machine-local assumptions in repository contracts?

To detect absolute host paths and machine-local assumptions in repository contracts, run a scan over a bounded repository root. The scan identifies environment-specific brittleness, stale references, and path leakage, then generates Markdown and JSON reports.

Can I automatically fix portability bugs and path leakage in validation artifacts?

You can automatically fix portability bugs in validation artifacts using the scan_and_apply_safe_fixes mode. This applies mechanical normalizations to replace host-specific fixtures with portable placeholders, but requires explicit operator approval before applying fixes.

What portability defects should I scan for in bounded codebases before review?

When scanning bounded codebases for portability defects, target absolute host paths, brittle worktrees, machine-local temp paths, stale contract references, and environment-specific assertions. These machine-specific cues break portability across different environments.

Does the contract normalizer require specific dependencies to scan review packets?

The contract normalizer requires no external dependencies to scan review packets. It operates on a bounded repository root and requires mandatory inputs including a target path and a defined policy to execute scans and generate review artifacts.

What is the best way to normalize environment-specific assertions in test suites?

The best way to normalize environment-specific assertions in test suites is to scan the bounded repository and apply narrowly scoped mechanical normalizations. This process replaces machine-local fixtures with portable placeholders while enforcing explicit stop conditions.