scaffold-hygiene

To detect scaffolding drift before a testnet relaunch, run an automated hygiene sweep that orchestrates parallel inspection agents to compare build, test, deploy, and CI configurations across your workspace. It validates workspace integrity and surfaces blockers by filing GitHub issues for real drift findings.

The best way to automate drift detection between CI workflows and Docker configs is to run a scaffolding hygiene pass that coordinates four parallel sub-agents across your repos. It checks for mismatches in docs, env vars, and cross-repo API contracts, then generates a timestamped report of the findings.

You need to run a scaffolding hygiene sweep during sprint closeouts, before testnet relaunches, after large PR waves, or any time drift is suspected. This ensures docs, configs, and scripts stay in sync across the workspace and surfaces blockers before they impact deployments.

Yes, you can automate GitHub issue creation for cross-repo API contract drift by running a scaffolding hygiene pass. It orchestrates parallel inspection agents that validate workspace integrity and automatically file GitHub issues for any real drift detected between repos.

Yes, the scaffolding hygiene pass operates without external dependencies. It orchestrates four parallel internal sub-agents to inspect docs, configs, and scripts, validates workspace integrity independently, and outputs a timestamped report alongside filed GitHub issues.

You should use parallel sub-agents for build and deploy script drift detection to efficiently surface blockers across a large workspace. Coordinating four parallel agents validates workspace integrity and identifies mismatches faster than sequential checks, ensuring real findings are filed as GitHub issues.