dev-adapt

To profile a repository and identify test commands, this automation reads common manifest files and workflows to surface commands, protected branches, and stack signals. It then persists findings to dev.* keys in config.json and writes a compiled dev-profile artifact.

A dev-profile artifact is a compiled file generated by auditing root documentation and manifests. It surfaces test commands and stack details for quick reference, allowing operators and ongoing automation to access current project configurations.

You should re-run project profiling after running hatch-based setup or whenever the project's testing, lint, or CI configurations change. This ensures the persisted dev.* keys in config.json reflect the latest workflow updates.

Yes, you can discover protected branches and technology stack details without manual inspection. The profiling process reads root documentation and workflow files to automatically surface and persist these stack signals into config.json.

No external dependencies are required to read manifest files and profile the project. The workflow operates independently to audit configurations and generate the locked dev-profile artifact for automation.

The best way to keep dev.* keys in config.json updated is to execute the profiling process whenever CI workflows change. This automatically reads the updated manifests and regenerates the compiled dev-profile artifact.