Loading...
Loading...
Found 241 Skills
Get the latest changelog for Claude Code. Trigger words: claude changelog, what's new in CC, claude code updates, latest version, what's new in claude code
Use this skill when designing SDKs, writing onboarding flows, creating changelogs, or authoring migration guides. Triggers on developer experience (DX), API ergonomics, SDK design, getting-started guides, quickstart documentation, breaking change communication, version migration, upgrade paths, developer portals, and developer advocacy. Covers the full DX lifecycle from first impression to long-term retention.
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.
Cuts a jackin❯ release — runs the readiness gates, writes the changelog, recommends a version, then executes cargo release on explicit operator confirmation.
This is a skill to check whether the content of CHANGELOG.md in a framework intended for external release is appropriate. It is used when updating or reviewing CHANGELOG.md.
Claude Code config optimization skill. Use when: - Editing CLAUDE.md, rules/, skills/, agents/, commands/ - User asks about config best practices - Checking optimization status - User says "claude code changelog" or "claude code updates" - User asks about new features or breaking changes in Claude Code
Technical documentation patterns for READMEs, ADRs, API docs (OpenAPI 3.1), changelogs, and writing style guides. Use when creating project documentation, writing architecture decisions, documenting APIs, or maintaining changelogs.
Run all quality checks (tests, lint, typecheck), fix failures, update the changelog, commit, push, and create/update the pull request or merge request.
Author, refresh, or repair the changelog entry for the current branch — derive metadata, write the frontmatter and grouped body, run the deterministic enrichment scripts, and validate against the changelog contract. Use when asked to write or update a changelog entry, refresh an entry after new commits, or as the changelog step inside a ship/PR flow. Detects an existing entry for the branch (idempotent update-vs-create), keeps `created_at` sacred, leaves post-merge fields to the release step, and validates with a zero-dependency Node script.
Maintain comprehensive changelogs and release notes following Keep a Changelog format. Use when documenting version history, release notes, or tracking changes across versions.
Generate comprehensive release notes and changelogs. Compiles version history, feature descriptions, and breaking changes from commit information.
Detects and prevents manual edits to release-please managed files (CHANGELOG.md, version fields in package.json, pyproject.toml, Cargo.toml). Provides conventional commit templates. Use when editing changelogs, version bumps, release files, or when user mentions "release", "changelog", "version bump", or "conventional commits".