搜索
搜索结果
33 results for "conventional commit"
conventional-commit
使用结构化XML格式生成约定式提交消息的提示词和工作流程。引导用户按照约定式提交规范创建标准化、描述性的提交消息，包含说明、示例和验证。
github
conventional-commit-message
Generate high-quality Conventional Commit messages for repositories using conventional-changelog-conventionalcommits.
conventional-changelog
conventional-commit
Create conventional commit messages following best conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits specification.
marcelorodrigo
everything-claude-code
Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
affaan-meverything-claude-code-conventions
everything-claude-code 的开发规范与模式指南。这是一个采用 Conventional Commits 规范的 JavaScript 项目。
affaan-m
caveman-commit
超精简提交信息生成器。去除提交信息中的噪音，同时保留意图和理由。采用 Conventional Commits 格式。主题行 ≤50 字符，仅在“为什么”不明显时添加正文。当用户说“写提交”、“提交信息”、“生成提交”、“/commit”或调用 /caveman-commit 时使用。暂存更改时自动触发。
juliusbrussee
git-pushing
Safely stage, commit, and push intended git changes with conventional commit messages. Use for ordinary non-release pushes when explicitly asked to push, save work remotely, or share a completed change.
sickn33commit-message-storyteller
Analyzes git diffs or staged changes and generates narrative commit messages that explain WHY a change was made, not just what changed — following Conventional Commits format. Use when asked to "write a commit message", "generate a commit", "describe my changes", "what should I commit this as", "commit this", "summarize my diff", or "help me commit". Works with git diff output, staged files, or plain descriptions of changes.
githubgit-commit
执行 git commit，包含约定式提交信息分析、智能暂存和消息生成。当用户要求提交更改、创建 git commit 或提及 "/commit" 时使用。支持：(1) 根据更改自动检测类型和范围，(2) 根据差异生成约定式提交信息，(3) 交互式提交，可覆盖类型/范围/描述，(4) 智能文件暂存以实现逻辑分组
github
changelog-generator
Produce consistent, auditable release notes from Conventional Commits. Separates commit parsing, semantic-bump logic, and changelog rendering for automated releases with editorial control. Use when cutting a release, generating CHANGELOG.md from git history, computing the next semantic version from commits, automating release notes in CI, or planning a hotfix/rollback. Examples: 'generate the changelog for v1.4.0', 'what version bump do these commits require', 'we need an emergency hotfix process'.
alirezarezvani
chinese-commit-conventions
中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 /chinese-commit-conventions 时调用，不要根据上下文自动触发。
jnmetacode
tlc-spec-driven
Feature planning and implementation with 4 adaptive phases (Specify, Design, Tasks, Execute). Auto-sizes depth by complexity. Writes testable requirements in EARS notation, atomic tasks, atomic Conventional Commits, and requirement traceability. Ships deterministic Python validation scripts so structural gates are enforced by code, not memory. Features an independent Verifier (author != verifier, evidence-or-zero), a discrimination sensor, a decision log (STATE.md), a test-coverage matrix, and a self-improving lessons layer. Stack-agnostic and tool-agnostic. Use when (1) planning features, (2) implementing with verification and atomic commits, (3) validating an implementation against a spec. Triggers on "specify feature", "discuss feature", "design", "tasks", "implement", "validate", "verify work", "UAT", "record decision", "pause work", "resume work". Do NOT use for pure architecture decomposition analysis or standalone technical design documents.
tech-leads-club
commit-work
创建高质量的 Git 提交：审查/暂存预期更改，拆分为逻辑提交，并编写清晰的提交消息（包括 Conventional Commits）。当用户要求提交、编写提交消息、暂存更改或将工作拆分为多个提交时使用。
softaworks
commit
Create well-formatted commits with conventional commit messages and emoji
neolabhq
commit
用于每次请求提交更改或草拟提交信息。创建带有问题引用的 Sentry 风格约定式提交。
getsentry
genshijin-commit
超圧縮コミットメッセージ生成。Conventional Commits形式で件名≤50文字、 「何を」より「なぜ」を重視。日本語・英語両対応。 「コミットメッセージ作って」「/commit」「/genshijin-commit」で起動。 ステージング変更時に自動起動候補。
interfacex-co-jp
conventional-git
Conventional Commits v1.0.0 branch naming, worktree naming, and commit message standards for GitHub and GitLab projects. Use when creating branches, naming worktrees, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation. Apply when your project needs consistent git history, SemVer-driven releases, parseable changelog generation, or automatic issue closing. Trigger when the user asks how to name a worktree, create a git worktree, or organize worktrees alongside branches.
samber
create-commit
Conventional Commits 形式で git コミットを作成する。staged 差分から type/scope を推定し、breaking change やシークレット混入 (.env 等) を検出。pre-commit フックを必ず通す (`--no-verify` 不可)。「コミットして」「git commit」「変更を記録して」などで使用。
fandhe-aicreate-pr
Conventional Commits 形式で GitHub PR を作成する。OWASP Top 10 のセキュリティチェック必須で、問題があれば PR 作成を中止。Summary/Test plan/Design を含む body を生成。「PR 作って」「プルリク」「`gh pr create`」などで使用。別リポジトリ (upstream) への貢献は contribute-skill。
fandhe-aiimplement-issue
GitHub Issue を読み込み、`_/local-plans/<issue-number>-<slug>.md` に詳細計画を作成して**ユーザー承認後**にコードを実装する。実装後はセキュリティレビュー (OWASP Top 10) → テスト実行 → Conventional Commits でコミット。Issue 番号や URL を渡された実装依頼、「Issue #N を実装して」「この Issue を着手」などで使用。
fandhe-aicreate-issue
GitHub Issue を親子構造 (sub-issues) で作成する。`gh issue create` で親・子 Issue を生成し、`gh api .../sub_issues` で親子関係を紐付ける。タイトルは Conventional Commits 形式 (`feat:`, `fix:` 等) を推奨。「Issue 作って」「タスクを分解して Issue 化」などで使用。
fandhe-aiimplement-review-pr
GitHub PR の CI ステータス (`gh pr checks`)・コード品質・セキュリティ (OWASP Top 10)・Conventional Commits 準拠をレビューする。`gh pr review --approve/--request-changes/--comment` でレビュー投稿も可能。「PR #N をレビュー」「PR レビューして」などで使用。ローカル diff のレビューには implement-review を使用。
fandhe-ai
ce-commit
创建清晰且突出变更价值的 Git 提交信息。当用户要求提交或保存暂存区/非暂存区的修改，并希望使用符合当前仓库规范且能清晰表达价值的提交信息时使用。
everyinc
commit
Create git commits with user approval and no Claude attribution
parcadei