496 件 ・ 関連度順
概要と使いどころ
Release tdmcp: write the Keep-a-Changelog entry, bump the SemVer version across every manifest, then (autonomously, per project policy) commit, tag, and push — gated on a td-qa PASS, with hard git safety rails. Use when releasing/shipping/cutting a tdmcp version, writing the CHANGELOG, bumping the version, or tagging a release.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews git history and updates CHANGELOG.md with entries for [Unreleased] section (converted from agent)
日本語の概要は準備中です。原文の説明を表示しています。
Use when opening, merging, or releasing a PR for imp - branching off main, `gh pr create`, enabling auto-merge, writing the PR body or a CHANGELOG entry, cutting a tagged release (version bump + CHANGELOG + tag + GitHub release). Symptoms - "PR stuck BLOCKED", "my last commit didn't land on main", "which check is required", "how do I cut a release", "auto-merge merged too early", "check-release failed", "STALE.md blocks git pull". Do NOT use for build/test mechanics (building-and-testing) or perf measurement / baseline refresh (benchmark-cuda).
日本語の概要は準備中です。原文の説明を表示しています。
Draft a changelog for the next release by summarizing git commits since the last tag. Use only when the user asks to draft release notes, write a changelog entry, or prepare the next version's notes — never trigger automatically.
日本語の概要は準備中です。原文の説明を表示しています。
Create a GitHub release with proper tagging, release notes, and optional build artifacts. Covers semantic versioning, changelog generation, and GitHub CLI usage. Use when marking a stable version of software for distribution, publishing a new library or application version, creating release notes for stakeholders, or distributing build artifacts (binaries, tarballs).
日本語の概要は準備中です。原文の説明を表示しています。
Track changes and versions in AI systems. TRIGGERS - Use when user needs help with ai-changelog-tracker related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Generate the stable Galyarder Framework release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag.
日本語の概要は準備中です。原文の説明を表示しています。
Generate CHANGELOG entries following conventional commits format with semantic versioning. Use when finalizing features to maintain proper change history.
日本語の概要は準備中です。原文の説明を表示しています。
Versioning and changelog management with @changesets/cli — adding changesets, version bumping, changelog generation, monorepo publishing, pre-release modes, and CI automation
日本語の概要は準備中です。原文の説明を表示しています。
Generate a weekly changelog entry from git history, filtering operational noise and producing editorial summary, field notes, statistics, and a bounded commit manifest. Stops for review unless commit was explicitly requested.
日本語の概要は準備中です。原文の説明を表示しています。
Helper for release operations, compilation of changelogs between tags, version lockstep syncing, and promotion of GitHub releases from canary/pre-release to latest/production. Use when the user asks to "compile the changelog", "promote release to latest", "tag a release", or do version release operations.
日本語の概要は準備中です。原文の説明を表示しています。
中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 /chinese-commit-conventions 时调用，不要根据上下文自动触发。
日本語の概要は準備中です。原文の説明を表示しています。
Update the CHANGELOG.md with the description of the changes between the last released version and the new one
日本語の概要は準備中です。原文の説明を表示しています。
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
日本語の概要は準備中です。原文の説明を表示しています。
Write and publish changelogs — release notes that users read, versioning, and launch communication cadence.
日本語の概要は準備中です。原文の説明を表示しています。
Write, restructure, or review documentation — tutorials, how-to guides, reference pages, concept/explanation docs, API references, READMEs, changelogs, release notes, and troubleshooting guides. Distills documentation craft from Mintlify's guides (compiled from technical writers at Stripe, GitHub, Amplitude, and Anaconda), the Diátaxis framework (including the compass and per-type voice), the Google and Microsoft style guides, Every Page Is Page One, Write the Docs, and Docs for Developers: audience analysis, content-type selection, style and word-level rules, procedure writing, structure for humans and AI agents, code-example standards, page templates (templates.md), mechanical enforcement and llms.txt (mechanics.md), maintenance, and success metrics. Use this skill when the user asks to "write docs", "document this feature", "improve this page", "review these docs", "write a tutorial / how-to / reference page", "structure the docs", "write API documentation", "write a README / changelog", or when authoring any file under a `docs/` tree. For SKMTC docs specifically, this skill governs the *craft* (what makes the page good); the content split between skills, `llms.md`, and the docs tree is governed by `docs/skills/README.md`. Distinct from `skmtc-retro` (captures observations about work) and the `skmtc-*` operational skills (guide doing the work) — this skill guides writing *about* the work for readers.
日本語の概要は準備中です。原文の説明を表示しています。
Generic automated semantic versioning and release workflow. Handles version increments, git tagging, GitHub releases, and automated changelog generation for any repository.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinates release preparation for your monorepo — maintaining CHANGELOG and the release assessment document, resolving merge conflicts on release branches, and communicating status, risk, and asks to the broader team. Use when the user mentions release manager, release train, cut a release, release branch, CHANGELOG, release assessment, monorepo release, merge conflicts during release, versioning, or coordinating a version bump with engineering and stakeholders.
日本語の概要は準備中です。原文の説明を表示しています。
Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update the docs", "sync documentation", or "post-ship docs". Proactively suggest after a PR is created and before it merges.
日本語の概要は準備中です。原文の説明を表示しています。
On-demand "what's new" generator. Main context (which knows the impending change) writes keepachangelog-style entries to a fragment file at `.claude/state/whatsnew/<slug>.json` (gitignored, transient). An optional per-project `project.json → whatsnew.route_workflow` names a routing workflow that consumes the fragment and renders it wherever the project wants (a site page, a release body, a docs page). Not a workflow phase — it never blocks a commit, and it never writes `CHANGELOG.md` (that file is owned solely by semantic-release in CI).
日本語の概要は準備中です。原文の説明を表示しています。
Use when taking a repo open source, or hardening one that already is. Run /oss-launch and it scans the repo (stack, existing files, git remote, secrets), asks only what it cannot infer, then generates a tailored OSS file collection (README, LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, CHANGELOG, .gitignore, .github/ issue + PR templates, CI/CD). Also covers launch (GitHub metadata, badges, Show HN, Reddit, YouTube), release cadence (SemVer + CHANGELOG), and demo-GIF generation. Triggers on "open source this", "OSS checklist", "prep for launch", "make this repo public", "add a license / contributing / security policy", "Show HN", "release workflow", "star growth", "get contributors".
日本語の概要は準備中です。原文の説明を表示しています。
Draft release summaries, changelog summaries, version PR notes, and changeset-friendly package release notes for npm packages or monorepos. Use this whenever the user asks to write a release summary, 发版说明, release notes, changelog entry, version PR summary, package publish notes, or wants the agent to summarize what will be released from git history, diffs, or changesets, especially for ui libraries, design systems, and multi-package workspaces.
日本語の概要は準備中です。原文の説明を表示しています。
公開CLIツールのリリース作業(バージョン付け・利用者向けドキュメント・CHANGELOG・検証・PR・タグ)を、ツール公開手順の規約に従って進める。ツールをリリースするとき、バージョンを上げて公開するとき、リリースPRやタグを作るときに使用する。
Run the complete release workflow: changelog entry, version bump, git tag, and GitHub release. Invokes changelog-entry, tag-version, and publish in sequence. Use when releasing a new version of the project.
日本語の概要は準備中です。原文の説明を表示しています。