Loading...
Loading...
Found 192 Skills
Manage project changelog following Keep a Changelog format. Use when documenting releases, adding change entries, generating changelogs from commits, or maintaining version history.
Diagnose the release-please release pipeline, read-only. Preview the next version from the merged Conventional-Commit PR titles since the last tag (feat→minor, fix/perf/revert→patch, !/BREAKING→major; docs/chore/ci/refactor/ test/build/style→none), show the open release-please--branches--main PR and its required-check (🔬 Build & Lint) status, detect the recurring stale `autorelease: pending` stall on the last merged release PR (where release-please aborts and releases silently stop firing), and confirm tag-vs-version parity (does a v<package.json version> tag already exist, or is publishing pending — the release.yml version-vs-tag gate). Use when asked why a release didn't fire, what version would cut next, whether the release PR is green, whether the pipeline is stalled, or to check release health. Advisory only — it inspects post-merge main and changes nothing.
Create release notes that summarize features, fixes, and migration guidance for software releases.
Generate and maintain changelogs following Keep a Changelog and Conventional Commits standards. Use when releasing versions, documenting changes, or updating project history.
Ship a new dtctl release — bump version, write changelog entries, run tests, commit, tag, push, and write GitHub release notes. Use this skill whenever the user says "release", "ship it", "cut a release", "new version", "bump version", "publish", or asks about the dtctl release process. Also use when the user wants to update CHANGELOG.md for a release or write GitHub release notes.
Use when designing monorepo structure, organizing packages, or migrating to monorepo architecture with architectural patterns for managing dependencies and scalable workspace configurations.
Generate and maintain changelogs following Keep a Changelog format. Analyzes git commits, categorizes changes, and produces well-structured release notes.
Maintains changelogs following Keep a Changelog format, categorizes changes by type. Use when updating CHANGELOG, preparing releases, or documenting version changes.
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
Maintain comprehensive changelogs and release notes following Keep a Changelog format. Use when documenting version history, release notes, or tracking changes across versions.
Event sourcing patterns and design decisions
Expert in Gravito Satellite modules. Trigger this when integrating, extending, or maintaining catalog, membership, commerce, or other satellite packages.