Loading...
Loading...
Found 241 Skills
Set up monitoring for API changes, changelogs, or documentation updates. Useful for tracking breaking changes in services you depend on.
Prepare release documentation including CHANGELOG entry, announcement text, and validation. Run before tagging a new release.
Breaking changes documentation, migration guides, deprecation process, and versioning. Use when introducing breaking API changes, creating migration guides, deprecating features, updating changelogs, managing major version releases, or documenting version transitions. Triggered by keywords like breaking changes, migration guide, deprecation notice, version upgrade, changelog update, breaking API modification.
Stage 2 (REX mode only) — Git archaeology, changelog analysis, verified factual timeline. Skip automatically in Concept mode.
Update dependencies safely — check changelogs, run tests, create PR
Package specification compliance for Elastic integration packages. Covers manifest structure (format_version, conditions, variables, routing rules), changelog schema and semantic version bumps, and alignment with the upstream elastic/package-spec. Use when building or reviewing manifest.yml, changelog.yml, or debugging elastic-package lint/check errors on package metadata.
Understand auto-generated changelogs via semantic-release. Use when viewing release history, understanding changelog format, or debugging missing changelog entries.
Investigate a cluster of GitHub issues and PRs, determine canonical candidates, post duplicate/related status, preserve contributor credit, and execute cleanup actions (comments, closes, labels, changelog touchpoints).
Documentation best practices — README structure, inline code comments, API docs, changelogs, and technical writing principles. Reference when writing any documentation.
Maintains CHANGELOG.md following Keep a Changelog format and Semantic Versioning. Use when the user mentions preparing or publishing a new release, or asks to review or refactor CHANGELOG.md.
When the user wants to create, optimize, or structure a changelog or release notes page. Also use when the user mentions "changelog," "release notes," "what's new," "updates," "product updates," "version history," or "changelog.yourdomain.com."
Generate player-facing patch notes from git history, sprint data, and internal changelogs. Translates developer language into clear, engaging player communication.