本文へ移動
cccskills
無料GitHub で公開

git-commit

Conventional commits with project conventions. Use when the user asks to commit, make a commit, or wants to follow the project's git commit standard.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Git Commit Standard

All commits in this project follow the Conventional Commits spec, tailored for a monorepo with packages/core/, packages/cli/, and packages/web/.

Subject Line

type(scope): description
  • Lowercase everything
  • Imperative mood ("add", not "added" or "adds")
  • No trailing period
  • Max 72 characters

Types

TypeUse for
featNew functionality visible to users
fixBug fixes
docsDocumentation-only changes
styleFormatting, whitespace, no logic change
refactorCode restructuring, no behavior change
testAdding or updating tests only
buildBuild system, dependencies, Docker
ciCI/CD pipeline changes
choreMaintenance that doesn't fit elsewhere

Scopes

  • core — changes scoped to packages/core/
  • cli — changes scoped to packages/cli/
  • web — changes scoped to packages/web/
  • architecture — changes scoped to packages/architecture/
  • eslint-config — changes scoped to packages/eslint-config/
  • deps / deps-dev — dependency bumps
  • release — release automation changes
  • Omit scope for repo-wide or cross-package changes

Body

  • Explain why, not what (the diff shows what)
  • Wrap at 72 characters
  • Include Resolves ABC-123 when closing a Linear issue

Instructions

When asked to commit:

  1. Run git status (never use -uall) and git diff --cached to understand staged changes
  2. If nothing is staged, identify which files should be staged based on the user's intent
  3. Pick the correct type and scope from the tables above
  4. Write a concise subject line in imperative mood
  5. Add a body only when the "why" isn't obvious from the subject
  6. Use a HEREDOC for the commit message to preserve formatting
  7. Never amend unless the user explicitly asks
  8. Never skip hooks (no --no-verify)

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

adr

無料

Create and manage Architecture Decision Records (ADRs). Use when making architectural changes (refactoring, API versioning, new domain layers, schema changes), when reviewing recent commits for documentation needs, or when the user mentions ADR, architecture decisions, or documenting technical decisions.

日本語の概要は準備中です。原文の説明を表示しています。

erode-app/erode522026年10月8日 更新

doc-sync

無料

Detect documentation and architecture-model drift by comparing source-of-truth code (CLI commands, flags, env vars, GH Action inputs/outputs, package structure, pipeline stages, providers, adapters, platforms) against web docs, README, and LikeC4 architecture model (.c4 files). Use when files that define the user-facing interface or internal structure change, when the user asks to check docs, or when mentioning doc drift, architecture drift, stale docs, or documentation sync.

日本語の概要は準備中です。原文の説明を表示しています。

erode-app/erode522026年10月8日 更新

Enforce the project's documentation voice when writing or reviewing public-facing content. Triggers on edits to doc files (packages/web/src/content/docs/**/*.md) and README.md. Catches LLM prose patterns, marketing language, and messaging drift.

日本語の概要は準備中です。原文の説明を表示しています。

erode-app/erode522026年10月8日 更新

Use this skill whenever code changes introduce new imports, API calls, database connections, message queues, or service-to-service communication. Also use before any commit or push. Catches undeclared dependencies and architecture violations using Erode.

日本語の概要は準備中です。原文の説明を表示しています。

erode-app/erode522026年10月8日 更新

Generate product pitch videos for the Erode project from screenshots. Use this skill whenever the user wants to create, update, or regenerate the product demo video, landing page animation, or pitch clip for erode.dev or the GitHub repo. Also trigger when the user mentions "product video", "demo video", "pitch video", "update the video", "regenerate video", or "landing page animation" in the context of Erode.

日本語の概要は準備中です。原文の説明を表示しています。

erode-app/erode522026年10月8日 更新

Sync the local LikeC4 syntax guide with the upstream LikeC4 skills repository (github.com/likec4/likec4/tree/main/skills/likec4-dsl). Use when the user asks to update, sync, or check the LikeC4 syntax guide, when upstream LikeC4 DSL changes are suspected, or when mentioning likec4 syntax sync, DSL drift, or syntax guide update.

日本語の概要は準備中です。原文の説明を表示しています。

erode-app/erode522026年10月8日 更新

erode-app のスキルをすべて見る

このスキルの問題を報告する