12 skills · sorted by relevance
Standardize Chinese Git commit messages and changelogs using Conventional Commits, a structured message format. The skill provides writing rules and configuration examples for message checks, interactive commit entry, and automatic changelog generation.
commitlint checks that Git commit messages follow the Conventional Commits format (type(scope): subject) and fails when they do not. Use when a user asks to standardize commit messages, enforce commit conventions with a husky commit-msg hook, lint commits or PR commits in CI, customize rules, or prepare commits for automated changelogs and semantic versioning.
The English summary is being prepared. Showing the original description.
When setting up commit message validation for a project. When project has commitlint.config.js or .commitlintrc files. When configuring CI/CD to enforce commit format. When extracting commit rules for LLM prompt generation. When debugging commit message rejection errors.
The English summary is being prepared. Showing the original description.
commitlint (Conventional Commits メッセージ検証ツール) リファレンス。 rules 設定、plugins、shareable-config、@commitlint/config-conventional、 Husky / lefthook / simple-git-hooks 連携、CI 統合、custom rules。
The English summary is being prepared. Showing the original description.
Build workflows that generate changelogs and release notes from commits, pull requests, and releases. Use Keep a Changelog formatting, standardize commit messages with Conventional Commits, and manage version numbers through Semantic Versioning rules.
Validate commit messages against the Conventional Commits specification. Auto-detects and installs commitlint CLI if missing. Checks project config or falls back to sensible defaults. Use when validating commit messages, preparing PRs, or enforcing commit conventions.
The English summary is being prepared. Showing the original description.
Generate one short Conventional Commits squash message describing only the net diff between the PR's base and head, set its header as the PR title, validate it with the repository's commitlint and both copy its description to the clipboard and display it, when asked for a squash message. Works in any Scenario repository, whatever its default branch.
The English summary is being prepared. Showing the original description.
Husky v9 setup, lint-staged v16 patterns, commitlint with conventional commits, CI/production handling, monorepo setup, migration from v8
The English summary is being prepared. Showing the original description.
中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 /chinese-commit-conventions 时调用，不要根据上下文自动触发。
The English summary is being prepared. Showing the original description.
Generate a PR_MESSAGE.md file from session context using GitHub CLI. Detects related issues via branch-keyword search, writes a structured PR description with commit subject, summary, test plan, and changelog. Validates with commitlint and markdownlint. Use when preparing a pull request on GitHub.
The English summary is being prepared. Showing the original description.
Configures Husky, lint-staged, commitlint, and Python pre-commit
The English summary is being prepared. Showing the original description.
Write commit messages under the agent-commits convention - a Conventional Commits fork with no chore catch-all, intent-only type tokens, facts in trailers, and legally-grounded AI provenance (Assisted-by, never Co-authored-by). Use when composing a commit in a repo whose commitlint.config.js extends agent-commits, when deciding between feat/fix/refactor/perf, or when recording AI participation.
The English summary is being prepared. Showing the original description.