agent-sort

To optimize environment configuration, you can classify ECC components into DAILY and LIBRARY buckets based on actual repository contents like lockfiles and framework configs. This generates an evidence-backed install plan that trims unnecessary surfaces, keeping only what the project requires.

Evidence-based ECC component classification is the process of sorting skills, rules, and hooks into DAILY or LIBRARY buckets. It verifies language, framework, and dependency manifests within a repository to ensure a clean and performant workspace tailored to the current tech stack.

Yes, you need repository-level file access to generate an ECC install plan. The classification process requires access to verify language, framework, and dependency manifests, ensuring the resulting DAILY and LIBRARY buckets accurately reflect the project's specific tech stack.

You should automate ECC component sorting during project initialization and environment cleanup tasks. It is specifically designed for situations where context-loading must be optimized by eliminating bloated, generic configurations in favor of a project-specific setup.

Automated install planning handles bloated generic configurations by analyzing repository-specific evidence to create a targeted setup. It automatically determines which rules and hooks are relevant to the current tech stack, generating an actionable plan to trim unnecessary surfaces.