commit-crafter

Formats and executes Conventional Commits with E-## task IDs and UACS verification stamps.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Vimurai/ai-os --skill commit-crafter-vimurai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-crafter
Source: https://github.com/Vimurai/ai-os/tree/main/.claude/skills/commit-crafter
Command: npx skills add https://github.com/Vimurai/ai-os --skill commit-crafter-vimurai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing compliant git commit messages in the AI-OS workflow requires remembering Conventional Commit types, task ID suffixes, tier stamps, and strict git identity rules — this Skill automates that entire process so every commit passes project policy. ## Core Features & Use Cases - Conventional Commit formatting: Classifies changes into feat/fix/refactor/test/chore/docs, builds a scoped subject line under 72 characters, and appends the correct E-## task IDs from .ai/TASKS.md. - Policy enforcement: Blocks --author flags, Co-authored-by trailers, git add -A, --no-verify, and staging of secrets files, per the Git Identity Mandate. - Tier-gated verification: Checks .ai/REVIEWS.md for critic stamps (Tier 2+) and requires a [UACS_VERIFIED] entry in .ai/LOG.md before allowing Tier 3 commits. - Use Case: After finishing a bug fix, ask the agent to commit — it reads open tasks, inspects the staged diff, and produces fix(ai-exec): handle empty task list (E-129) with the correct tier stamp. ## Quick Start Ask the agent to commit my current staged changes following the AI-OS commit format with the matching E-## task ID.

Frequently Asked Questions about commit-crafter

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

FAQPage Schema
How do I write a Conventional Commit message with a task ID?▼

Use the format type(scope): summary (E-##), keeping the subject under 72 characters including the task suffix. The Skill classifies the change type from the staged diff and pulls the matching E-## IDs from .ai/TASKS.md automatically.

How do I commit changes in an AI-OS project?▼

Stage specific named files rather than git add -A, then let the Skill build the commit message from the staged diff and open tasks. It verifies the required review stamps exist before executing git commit.

Why is my Tier 3 commit blocked by the UACS check?▼

Tier 3 commits require a [UACS_VERIFIED] entry in the last 20 lines of .ai/LOG.md. If it is missing, the Skill stops and instructs you to run the security_engineer agent to produce the verification stamp first.

Can I use Co-authored-by trailers or --author flags in commits?▼

No. The Git Identity Mandate strictly forbids --author flags and Co-authored-by trailers; commits are attributed only to the repository's configured git identity. Amending existing commits is also disallowed unless explicitly requested.

What files should never be staged in a commit?▼

Never stage .env, *.key, credentials.*, or secrets.* files. The Skill also warns against git add -A after conflicted operations, since conflict markers in files like .ai/state.json can be committed unread.