ワンクリックでManusで任意のスキルを実行

devops-commit

スター4

フォーク0

更新日2026年5月13日 12:40

Create a conventional commit for staged/changed files — enforces type, scope, co-author footer. Handles amend for "update/fix last commit". Do NOT trigger for push, PR, or ship operations.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

Jerry0022

Jerry0022/dotclaude

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Commit

Create a well-formed conventional commit.

Step 0 — Load Extensions

Check for optional overrides. Use Glob to verify each path exists before reading. Do NOT call Read on files that may not exist — skip missing files silently (no output).

Global: ~/.claude/skills/commit/SKILL.md + reference.md
Project: {project}/.claude/skills/commit/SKILL.md + reference.md
Merge: project > global > plugin defaults

Note on disable-model-invocation: true: This skill is only triggered by explicit user commands (/devops-commit), never by model initiative. Extensions are still loaded and merged normally — disable-model-invocation only controls trigger behavior, not extension resolution.

Step 0.5 — Repo-mode check

Before any git command, verify this directory is a git repository:

git rev-parse --is-inside-work-tree

If this fails (exit != 0), abort with a structured message:

Dieses Verzeichnis ist nicht versioniert. /devops-commit requires git. Options:

git init to start version control here

Or configure a non-git delivery target in .claude/skills/ship/reference.md (see skill-extension-guide.md -> Delivery targets)

Do NOT proceed with any git command. End the skill.

Step 1 — Detect intent

Amend: user says "amend", "update last commit", "fix last commit" → amend flow in Step 8
Normal: everything else → standard flow

Step 2 — Survey changes

git status --short

Identify staged, unstaged, and untracked files.

Step 3 — Smart staging

If nothing is staged:

≤5 changed files: Run git diff to see changes, then stage all relevant files with git add <specific files>.
>5 changed files: Use AskUserQuestion to present file groups and let the user choose. Group by directory or logical change.

Rules: Never use git add -A or git add .. See deep-knowledge/git-hygiene.md.

Step 4 — Read staged diff

git diff --cached

Read all staged changes carefully — this informs type, scope, and message.

Step 5 — Determine type and scope

Type:

Type	When
`feat`	New user-facing feature
`fix`	Bug fix
`refactor`	Internal restructure, no behavior change
`perf`	Performance improvement
`test`	Adding or fixing tests
`docs`	Documentation only
`chore`	Tooling, deps, CI, config
`style`	Formatting, whitespace

Scope: The module, component, or subsystem most affected. Derive from the file paths and project structure — no hardcoded list.

Step 6 — Write message

Subject: ≤72 chars, imperative mood, no period. Say what it does, not what changed.

Bad: "Updated the login screen"
Good: "add dark mode toggle to settings"

Body (optional but recommended): Explain the why, not the what. Wrap at 72 chars.

Step 7 — Add co-author

Extract the model name from the current session's system prompt and format:

Co-Authored-By: Claude {Model} <noreply@anthropic.com>

Always detect dynamically — never hardcode a specific model version.

Step 8 — Execute commit

Normal:

git commit -m "$(cat <<'EOF'
<type>(<scope>): <subject>

<body>

Co-Authored-By: Claude <Model> <noreply@anthropic.com>
EOF
)"

Amend (only when user explicitly requested):

git commit --amend -m "$(cat <<'EOF'
<type>(<scope>): <updated subject>

<updated body>

Co-Authored-By: Claude <Model> <noreply@anthropic.com>
EOF
)"

Step 9 — Report

Show commit hash, title, and stats:

git log --oneline -1 && git diff --stat HEAD~1

Step 10 — Completion Card

Call mcp__plugin_devops_dotclaude-completion__render_completion_card with variant ready (a commit is a code change, not a ship — shipped only after /devops-ship).

render_completion_card({
  variant: "ready",
  summary: "<~10 words, user's language>",
  lang: "<de|en>",
  session_id: "<from hook input>",
  changes: [{ area, description }, ...],   // top 3 FUNCTIONAL changes (user-perceived effect), derived from the staged diff but phrased as behavior — not file lists. See completion-card template § Changes.
  state: { branch, commit: "<short sha>", pushed: <bool>, merged: null }
})

Output the returned markdown VERBATIM as the LAST thing in the response — character-for-character, no text after the closing ---.

Rules

Never use --no-verify unless the user explicitly requests it.
Never use git add -A or git add ..
If a pre-commit hook fails, fix the issue and create a new commit — never --amend unless the user asks.
Do not commit files that may contain secrets (.env, credentials, keys).
Merge commits are out of scope — handle manually.

このリポジトリの他の Skills

同じリポジトリ

devops-claude-extend-skill

Jerry0022/dotclaude

Interactively scaffold or adapt a project-level extension for any plugin skill. Lists available skills, checks for existing extensions, and creates or opens the correct files. Triggers on: "extend skill", "customize skill", "skill extension".

2026-07-204

devops-claude-lint

Jerry0022/dotclaude

Audit CLAUDE.md files for size, structure, and token efficiency. Checks both project-level and global CLAUDE.md. Warns when files exceed 25 lines (the recommended maximum for index-style CLAUDE.md). Suggests creating one if missing. Triggers on: "lint claude md", "claude md check", "check claude md", "CLAUDE.md zu lang", "audit claude md", "claude md audit". Do NOT auto-trigger from user phrasing for editing CLAUDE.md content or for /devops-setup-project. MAY be invoked explicitly via the Skill tool by other skills (devops-learn, devops-setup-project) as a post-edit gate.

2026-07-204

devops-concept

Jerry0022/dotclaude

Generate an interactive HTML page for analysis, plans, concepts, prototypes, comparisons, or creative work — open it in the browser and monitor user decisions (toggles, selections, comments) to feed them back into the workflow. Triggers on: "concept", "concept page", "interactive plan", "show me this as a page", "visualize this". Also auto-suggest when Claude completes analysis, planning, comparison, or concept work that would benefit from interactive decision-making. Do NOT trigger for: simple code explanations, debugging (use /devops-fix), or static documentation (use /devops-setup-readme).

2026-07-204

devops-fix

Jerry0022/dotclaude

Read session logs, runtime errors, and crash output to diagnose and fix the current issue — root-cause analysis first. Use when something is broken or behaving unexpectedly. Triggers on: "debug", "this is broken", "doesn't work", "error", "crash", "blank screen", "warum geht das nicht", "funktioniert nicht". Also triggers on pasted error/stack traces or when post.flow.debug hook detects repeated Bash failures. Do NOT trigger for general code questions.

2026-07-204

devops-learn

Jerry0022/dotclaude

Capture a long-term learning/correction and route it to the correct project- specific instructions (skill, skill-extension, deep-knowledge, or as a last resort CLAUDE.md) — NOT to personal feedback memory. Also prunes now-duplicate `feedback_*.md` entries with confirmation. Routing details live in the skill body (Step 5 table). Triggers ONLY on explicit invocation: "/devops-learn", "lerne das", "merk dir das fürs Projekt", "remember this for the project", "capture learning". Do NOT trigger for one-off conversational corrections or for personal feedback memory.

2026-07-204

devops-plugin-update

Jerry0022/dotclaude

Manually update the devops plugin to latest from GitHub. Delegates to ss.plugin.update hook (pull + cache + registry), then adds changelog and verification report. Triggers on: "update plugin", "plugin updaten", "self update", "devops update", "neue version". Explicit user request only.

2026-07-204

name	devops-commit
version	0.1.0
description	Create a conventional commit for staged/changed files — enforces type, scope, co-author footer. Handles amend for "update/fix last commit". Do NOT trigger for push, PR, or ship operations.
disable-model-invocation	true
allowed-tools	Bash(git *), AskUserQuestion, mcp__plugin_devops_dotclaude-completion__render_completion_card

Commit

Create a well-formed conventional commit.

Step 0 — Load Extensions

Check for optional overrides. Use Glob to verify each path exists before reading. Do NOT call Read on files that may not exist — skip missing files silently (no output).

Global: ~/.claude/skills/commit/SKILL.md + reference.md
Project: {project}/.claude/skills/commit/SKILL.md + reference.md
Merge: project > global > plugin defaults

Step 0.5 — Repo-mode check

Before any git command, verify this directory is a git repository:

git rev-parse --is-inside-work-tree

If this fails (exit != 0), abort with a structured message:

Dieses Verzeichnis ist nicht versioniert. /devops-commit requires git. Options:

git init to start version control here

Or configure a non-git delivery target in .claude/skills/ship/reference.md (see skill-extension-guide.md -> Delivery targets)

Do NOT proceed with any git command. End the skill.

Step 1 — Detect intent

Amend: user says "amend", "update last commit", "fix last commit" → amend flow in Step 8
Normal: everything else → standard flow

Step 2 — Survey changes

git status --short

Identify staged, unstaged, and untracked files.

Step 3 — Smart staging

If nothing is staged:

≤5 changed files: Run git diff to see changes, then stage all relevant files with git add <specific files>.
>5 changed files: Use AskUserQuestion to present file groups and let the user choose. Group by directory or logical change.

Rules: Never use git add -A or git add .. See deep-knowledge/git-hygiene.md.

Step 4 — Read staged diff

git diff --cached

Read all staged changes carefully — this informs type, scope, and message.

Step 5 — Determine type and scope

Type:

Type	When
`feat`	New user-facing feature
`fix`	Bug fix
`refactor`	Internal restructure, no behavior change
`perf`	Performance improvement
`test`	Adding or fixing tests
`docs`	Documentation only
`chore`	Tooling, deps, CI, config
`style`	Formatting, whitespace

Scope: The module, component, or subsystem most affected. Derive from the file paths and project structure — no hardcoded list.

Step 6 — Write message

Subject: ≤72 chars, imperative mood, no period. Say what it does, not what changed.

Bad: "Updated the login screen"
Good: "add dark mode toggle to settings"

Body (optional but recommended): Explain the why, not the what. Wrap at 72 chars.

Step 7 — Add co-author

Extract the model name from the current session's system prompt and format:

Co-Authored-By: Claude {Model} <noreply@anthropic.com>

Always detect dynamically — never hardcode a specific model version.

Step 8 — Execute commit

Normal:

git commit -m "$(cat <<'EOF'
<type>(<scope>): <subject>

<body>

Co-Authored-By: Claude <Model> <noreply@anthropic.com>
EOF
)"

Amend (only when user explicitly requested):

git commit --amend -m "$(cat <<'EOF'
<type>(<scope>): <updated subject>

<updated body>

Co-Authored-By: Claude <Model> <noreply@anthropic.com>
EOF
)"

Step 9 — Report

Show commit hash, title, and stats:

git log --oneline -1 && git diff --stat HEAD~1

Step 10 — Completion Card

Call mcp__plugin_devops_dotclaude-completion__render_completion_card with variant ready (a commit is a code change, not a ship — shipped only after /devops-ship).

render_completion_card({
  variant: "ready",
  summary: "<~10 words, user's language>",
  lang: "<de|en>",
  session_id: "<from hook input>",
  changes: [{ area, description }, ...],   // top 3 FUNCTIONAL changes (user-perceived effect), derived from the staged diff but phrased as behavior — not file lists. See completion-card template § Changes.
  state: { branch, commit: "<short sha>", pushed: <bool>, merged: null }
})

Output the returned markdown VERBATIM as the LAST thing in the response — character-for-character, no text after the closing ---.

Rules

Never use --no-verify unless the user explicitly requests it.
Never use git add -A or git add ..
If a pre-commit hook fails, fix the issue and create a new commit — never --amend unless the user asks.
Do not commit files that may contain secrets (.env, credentials, keys).
Merge commits are out of scope — handle manually.