agent-sort

Sort ECC components into DAILY versus LIBRARY buckets using evidence-based classification from direct repository inspection, then generate an install plan to trim your skill and commands set to only what your codebase supports.

Evidence-based classification for daily vs library component sorting means inspecting the target repository's actual file structure and grep results to decide what loads every session versus what remains available without default load, replacing generic heuristics.

Plan a lean ECC install by performing parallel or sequential review passes to build an evidence table from repo-local inspection, then generate an install plan with a verification report confirming the trimmed component surface matches your stack.

Yes, you can filter hooks alongside skills, commands, rules, and extras to reduce your command surface, sorting them into DAILY or LIBRARY buckets based on actual project needs rather than installing the full default set.

Run a repository audit for ECC component cleanup when your project needs a smaller, correct surface and you want to avoid installing an oversized, noisy set of skills, commands, rules, and hooks that do not match your codebase.

Agent-sort works without generic heuristics by requiring an evidence table from repo-local inspection, applying review passes to classify components, and outputting an install plan with a verification report to ensure correct defaults for your specific repository.