commit

Generates Conventional Commits messages from staged git changes with sensitive-file detection.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/real-case/marvin-toolkit --skill commit-real-case
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/real-case/marvin-toolkit/tree/main/plugins/marvin/skills/commit
Command: npx skills add https://github.com/real-case/marvin-toolkit --skill commit-real-case

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, safe git commits is repetitive and error-prone: developers forget to check for leaked secrets, write vague messages, or bypass failing pre-commit hooks. This Skill inspects the repository state, stages files intentionally, blocks credential-shaped files, and drafts a Conventional Commits message before confirming with you. ## Core Features & Use Cases - Sensitive file detection: Scans staged files for .env, keys, tokens, and credential patterns, unstaging and warning before any commit lands. - Conventional Commits drafting: Analyzes the staged diff and produces a type/scope/subject message matching your repo's existing style, with no AI attribution. - Task board linking: Appends a Refs footer tying the commit to the current branch's board task when a .marvin/track board exists. - Hook failure recovery: Fixes pre-commit hook failures and creates a new commit, never using --amend or --no-verify. - Use Case: After finishing a feature branch, say "commit my changes" and get a reviewed, secret-free commit message linked to your task, confirmed before anything is written. ## Quick Start Ask the assistant to commit your current changes, for example: "commit my staged changes with a conventional commit message."

Frequently Asked Questions about commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a conventional commit message from staged changes?▼

Stage your files, then let the commit workflow analyze the diff and draft a type(scope): subject message in imperative mood under 72 characters. It matches your repo's existing commit style from git log and adds a body explaining why, not what.

How to prevent committing secrets like .env files or API keys?▼

The workflow scans staged filenames against patterns for .env, .pem, .key, credentials, tokens, and similar sensitive files. Matches are automatically unstaged with a warning, and the commit does not proceed until you resolve them.

What happens when a pre-commit hook fails during git commit?▼

The workflow reads the hook error output, fixes the lint, format, or type issues, stages the fixes, and creates a new commit. It never uses --amend after a hook failure and never bypasses hooks with --no-verify.

Can I provide my own commit message instead of generating one?▼

Yes, pass your message as an argument and the workflow uses it directly, skipping generation. It still runs sensitive-file detection and appends the board task Refs footer if your branch matches a tracked task.

Does the commit message include AI attribution or co-author lines?▼

No, messages never mention Claude, AI, generated-by notices, or Co-Authored-By lines. Commits appear as regular developer work following the Conventional Commits format.