Generate synchronized developer and client changelogs from git history and task trackers.
npx skills add https://github.com/gkganesh12/gk-stack --skill gk-changelog
Please help me install this Agent Skill. Skill: gk-changelog Source: https://github.com/gkganesh12/gk-stack/tree/main/skills-extra/gk-changelog Command: npx skills add https://github.com/gkganesh12/gk-stack --skill gk-changelog
This skill solves the problem of maintaining inconsistent or outdated project history by automatically generating synchronized changelogs for both technical developers and non-technical stakeholders.
Trigger the gk-changelog skill to generate or update your project changelogs based on the latest git history and task documentation.
High-intent search queries and answers about installing and using this skill.
Automated changelog generation works by parsing git commit history, task trackers, and architectural decision logs to create context-aware release documentation. It groups raw commits into meaningful, high-level entries tailored for specific audiences rather than dumping raw commit lists.
Yes, dual-format changelog generation produces a technical CHANGELOG.md for developers and a plain-English CHANGELOG_CLIENT.md for business stakeholders. It automatically translates technical git history into plain-English release summaries for non-technical audiences.
Automated changelog generation strictly satisfies requirements for semantic versioning and Keep a Changelog formatting standards. It parses your project history and outputs structured release documentation grouped by added, changed, fixed, and security categories.
Yes, the changelog automation works by parsing task trackers and architectural decision logs alongside git history. It aggregates commits, tasks, and architectural decisions into meaningful, high-level entries for comprehensive release reporting.
The best way to generate plain-English release summaries is applying technical-to-plain-English translation to parsed git history. This context-aware grouping aggregates raw technical commits into high-level entries tailored for non-technical business stakeholders.
You need to run automated changelog generation after completing a development sprint to instantly update project documentation. It is required for automated release documentation and stakeholder communication within software development lifecycles.
nirholasAdd emojis to git commit messages, branches, logs, and tags.
jonaseck2Enforce CHANGELOG.md release-note structure with a 10-block rolling window.
baphledManage software release lifecycle with Semantic Versioning and changelogs.
ZJU-REALTranslate Chinese technical documentation to English while preserving formatting and validating accuracy.
