Aggregate merged pull requests into human-friendly changelogs for engineering teams.
npx skills add https://github.com/JesusFilm/core --skill changelog-jesusfilm
Please help me install this Agent Skill. Skill: changelog Source: https://github.com/JesusFilm/core/tree/main/.claude/skills/changelog Command: npx skills add https://github.com/JesusFilm/core --skill changelog-jesusfilm
Aggregates and formats merged pull requests into human-friendly changelogs for internal engineering teams.
Generate a concise daily changelog for the latest PR merges to main, including features, bug fixes, and contributor credits.
High-intent search queries and answers about installing and using this skill.
To generate a changelog from merged pull requests, you can aggregate and format PR metadata such as titles, descriptions, labels, and merge dates into a human-friendly log for your engineering team. This process summarizes features and bug fixes while crediting contributors.
Automating release notes for daily engineering cycles involves parsing merged pull request metadata and formatting it into readable summaries. This tailored output includes contributor attribution, issue references, and optional breaking change notes for transparent internal reviews.
Yes, an automated changelog can include breaking changes and issue references. By parsing pull request metadata, the output specifically formats issue references and optional notes on breaking changes alongside standard feature and bug fix summaries.
Changelogs handle contributor attribution by extracting author and reviewer information from merged pull request metadata. This data is then formatted directly into the human-friendly change log to credit the specific individuals involved in each item.
Yes, automated changelog generation works for weekly project handoffs. It supports both daily and weekly release cycles by aggregating merged pull requests into transparent logs that document changes, issue references, and contributor credits for internal reviews.
To format human-friendly release notes, the required pull request metadata includes the PR title, description, labels, merge date, author attribution, and issue references. This information is parsed to document features and flag breaking changes.
lucasilverentandStandardize pull request titles, descriptions, and labels using the GitHub CLI.
product-on-purposeGenerate user-facing release notes from changelog data.
jobayerarmanPrepare a development branch for pull request submission with validation and cleanup.
haojing8312Analyze git commits and tags to recommend version bumps and draft bilingual release notes.
