GPT-5 finding
Line-count approach is not YAML-aware and doesn’t truly count distinct enabled skills
lowmaintainabilitymedium
- skills/fork-cohort/SKILL.md:87-91
wc -l over regex matches is not guaranteed to reflect distinct skills in YAML (e.g., unconventional formatting, anchors/aliases, or repeated keys in separate sections could skew counts). While typical Aeon configs likely work, this brittleness risks future miscounts and increases maintenance overhead.
Recommendation
Use a YAML-aware parser to count enabled skills under the skills map. Example with yq: yq -r '.skills | to_entries | map(select(.value.enabled == true)) | length' /tmp/fork-aeon.yml. As a grep-only fallback, at least ignore comments and constrain matches to lines starting at a skill value context.