changelog-generator

Quick Review

The skill has clear structure and metadata but lacks substantive content. The description is vague and repetitive, offering no concrete guidance on how to generate changelogs. There are no actual procedures, templates, or code for parsing commit history, categorizing changes, formatting output, or following changelog standards (e.g., Keep a Changelog). The skill claims to provide 'step-by-step guidance' and 'production-ready code' but contains none. While changelog generation could be valuable (parsing git logs, semantic versioning), this implementation provides minimal task knowledge beyond generic placeholders.