verifying-agnosticism

Detect hardcoded paths by running the repository audit script to scan files for Windows and Unix path literals, BASE_DIR and PROJECT_ROOT constants, and JSON workdir values. It targets .claude, .codex, and related directories to ensure portability by identifying environment-coupled values.

Templates break during onboarding due to hardcoded paths and project-specific references coupling them to specific environments. Scanning for absolute path literals, BASE_DIR constants, and JSON workdir values identifies these environment-coupled values for replacement with repo-root-aware patterns.

Fix BASE_DIR and PROJECT_ROOT constants by auditing orchestration files for hardcoded path literals and replacing them with repo-root-aware patterns. The scan detects these constants in code and JSON workdir fields, delivering a report with guidance for portable remediation.

Yes, the path audit detects Windows and Unix absolute path literals. It scans agents, skills, hooks, and orchestration files across .claude, .codex, and related directories to identify environment-coupled values and recommends fixes to replace hardcoded references with portable patterns.

Yes, you can audit JSON workdir fields in .claude and .codex directories. The scanner targets these directories to detect hardcoded paths, project-specific references, and environment-coupled values, producing a report with remediation guidance to ensure template portability across diverse repos.

Automated hardcoded path scanning should not be the sole portability check when repositories rely intentionally on environment-specific absolute paths. The scanner identifies Windows and Unix literals, BASE_DIR constants, and JSON workdir values, but manual review ensures intended project-specific references remain untouched.