494 件 ・ 関連度順
概要と使いどころ
Reusable-session release-notes runbook for {{target_repo}}. Finds the range since the last release covered, reads every PR merged in it, groups them by area, writes plain-language notes in the house voice, and opens a PR against {{changelog_path}} only when a new release has actually shipped.
日本語の概要は準備中です。原文の説明を表示しています。
Polish a published qiankun GitHub Release's aggregated notes into a bilingual (English then Chinese) write-up with an agent. Use after a release goes out — turning the mechanically-aggregated, per-package release notes into a clean, human-readable, English + Chinese write-up (highlights, de-duped cross-package lines, clearer wording) via `gh release edit`. Triggers include "polish the release notes", "clean up the GitHub release", "improve the changelog for the latest release".
日本語の概要は準備中です。原文の説明を表示しています。
Create changelog files for important commits in a PR
日本語の概要は準備中です。原文の説明を表示しています。
Scan recent merges and commits since last release for changelog content.
日本語の概要は準備中です。原文の説明を表示しています。
Scan recent merges to main (and noteworthy direct commits) since a given window (last tag or date in state). Extract titles, labels, types, linked issues, and signals for breaking changes or security. Produces structured input for a release notes drafter. Use in changelog-drafter loops.
日本語の概要は準備中です。原文の説明を表示しています。
中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 /chinese-commit-conventions 时调用，不要根据上下文自动触发。
日本語の概要は準備中です。原文の説明を表示しています。
Oversee the other Claude threads (sessions) working on the same project. Check what each is doing, confirm finished work is merged to main, has its changelog entry with screenshots, and is live, archive threads that are truly done, and restart or flag threads that were cut off. Use when the user says "check threads", "check new changes", "are the threads merged and pushed", "archive the done threads", or asks what the other sessions are up to. Project specifics (changelog format, live site, capture folders) go in an optional local references/<project>.md next to this skill.
日本語の概要は準備中です。原文の説明を表示しています。
View recent CHANGELOG entries
日本語の概要は準備中です。原文の説明を表示しています。
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.
日本語の概要は準備中です。原文の説明を表示しています。
Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags.
日本語の概要は準備中です。原文の説明を表示しています。
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release", "cut a release", "ship a new version", or "bump and publish" brooks-lint. Do NOT trigger for: propagating an already-decided version without releasing (use `npm run bump` directly), CHANGELOG edits alone, or questions about the release process that don't ask to perform it.
日本語の概要は準備中です。原文の説明を表示しています。
Review generated or changed documentation before it ships — READMEs, API references, docstrings, PHPDoc/JSDoc, changelogs, tutorials, and doc sites. Best used reactively after an agent writes or edits docs, after code changes documented behavior, or before publishing docs. Use when the user says 'review the docs', 'is this documentation accurate', 'update the docs', 'write a README', 'document this API', 'add a docstring', or 'add a changelog entry'. Core job: verify every referenced function, flag, endpoint, config key, and code sample against the source; catch docs-vs-code drift; strip filler and unverifiable claims. DO NOT USE for production code review (use clean-code-guard), test review (use test-guard), marketing copy or blog posts, prose style editing of non-technical writing, or documentation site theming.
日本語の概要は準備中です。原文の説明を表示しています。
Automate versioning and changelog generation using semantic versioning principles. Configure release automation, version bumping, and changelog tools. Use when implementing version management or automating release processes.
日本語の概要は準備中です。原文の説明を表示しています。
Post-ship documentation sync. Updates README, ARCHITECTURE, CONTRIBUTING, CHANGELOG, TODOS, VERSION. Auto-applies factual corrections, asks for risky rewrites. CHANGELOG voice polish. Cross-doc consistency checks.
日本語の概要は準備中です。原文の説明を表示しています。
Auto-generate changelog from git commits
日本語の概要は準備中です。原文の説明を表示しています。
Generate changelogs from recent commits and merged PRs
日本語の概要は準備中です。原文の説明を表示しています。
Automates release management with changelog generation, semantic versioning, and release readiness checks. Use when preparing releases, generating changelogs, bumping versions, or validating release candidates.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a set of commits or a diff into a clean, user-facing changelog entry. Use before a release or PR description.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update a structured change log for a product or platform. Use when someone asks to "create a change log", "log this change", "what changed", "update the change log", "release notes", or "changelog". Reads project memory (CLAUDE.local.md Recent Changes) and meeting notes to build chronological change records. Supports init (backfill from memory), update (append new entries), and release (summarize for a version).
日本語の概要は準備中です。原文の説明を表示しています。
Generate user-facing release notes for the App Store and Google Play from git history (App Store <=4000 chars, Google Play <=500). Use when generating release notes, app store changelog, play store release, or "what's new" text for a mobile app.
日本語の概要は準備中です。原文の説明を表示しています。
CONTRIBUTOR TOOL - Track CC changelog, extract new versions since last check, analyze impact on plugin (breaking changes, opportunities, deprecations). Run periodically or before releases. NOT part of the distributed plugin.
日本語の概要は準備中です。原文の説明を表示しています。
Web change monitoring - track changes on pages, detect updates, changelog diffs
日本語の概要は準備中です。原文の説明を表示しています。
Git history'den otomatik changelog, semantic versioning, release notes, conventional commits
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive documentation specialist covering API documentation, technical writing, design documentation, migration guides, and changelog generation. Use when creating OpenAPI/Swagger specs, generating SDKs, writing user guides, creating README files, documenting architecture, writing design specs, creating ADRs, writing migration guides, or generating changelogs from git commits. Handles versioning, examples, developer experience, and user-facing documentation.
日本語の概要は準備中です。原文の説明を表示しています。