Loading...
Loading...
Found 51 Skills
GitHub release workflow with semantic versioning, changelogs, and release automation using gh CLI. Use when creating releases, tagging versions, or publishing changelogs.
Extract and parse local git commit history into structured JSON format with custom tags ([Why], [What], [Impact]). Use when generating changelogs, creating PR summaries, updating CHANGELOG.md files, or analyzing recent code changes. Parses conventional commits, extracts technical details and business impact, and returns flat JSON to save context tokens and reduce hallucinations during documentation generation.
Prepare release documentation including CHANGELOG entry, announcement text, and validation. Run before tagging a new release.
Analyzes git commit history and generates structured changelogs categorized by change type. Use when the user asks about recent changes, wants a changelog, or needs to understand what changed in the repository.
Automate Drupal module updates in DDEV environments with safety snapshots, composer update, drush updb, config export, and changelog generation. Handles security updates, patch versions, minor versions, and major version upgrades with compatibility checking. Use when updating Drupal modules, checking for module updates, running composer update, upgrading dependencies, checking outdated packages, or when user mentions DDEV, drush, composer outdated, or module security updates.
Use when creating git commits, writing commit messages, or following version control workflows
Create engaging changelogs for recent merges to main branch
Create changelog files for important commits in a PR
Cut a release — detect versioning context, generate a changelog from conventional commits, bump versions, and create a git tag. Use when the user says "release", "cut a release", "tag a release", "bump the version", "create a changelog", "ship a version", "publish", or any variation of shipping/publishing a version. This skill is intentionally generic and works across any repo — it infers context from git history and project structure rather than assuming a specific setup.
Create git commits following Conventional Commits specification with project-specific branch naming rules. Use for commit message generation, changelog, and versioning.
Create versioned releases with consolidated changelogs. Gathers shipped items, generates CHANGELOG.md entry, creates git tag, and GitHub Release. Use after multiple /ship tasks are merged.
Generate structured, professional Release Notes / Changelog from a raw commit log. Automatically categorizes commits into Breaking Changes, Features, and Fixes. Trigger when the user asks to write release notes or a changelog based on provided text.