commit

Automate conventional-commit style commits for SpecD projects.

12|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/specd-sdd/SpecD --skill commit-specd-sdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/specd-sdd/SpecD/tree/main/.gemini/skills/commit
Command: npx skills add https://github.com/specd-sdd/SpecD --skill commit-specd-sdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit operations can drift from SpecD conventions and leave metadata out of sync; this skill enforces conventional commits, groups related changes, and runs metadata validation before a commit.

Core Features & Use Cases

  • Group changes into a single commit following SpecD conventions and scopes.
  • Craft and verify conventional commit messages, regenerate .specd-metadata.yaml when needed, and stage changes for a single, atomic commit.
  • Prevent direct git commits by routing everything through the skill, providing guardrails and consistency across spec directories.

Quick Start

Invoke the commit skill after completing changes to produce a single, conventional, metadata-validated commit.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I enforce conventional commit messages in a spec-driven codebase?

To enforce conventional commit messages in a spec-driven codebase, the skill automates conventional commit formatting, groups related changes, and stages them within a single guided flow to prevent convention drift.

Why does my direct git commit fail when using SpecD workflows?

Direct git commits fail because the skill prevents them to provide guardrails and consistency across spec directories. It routes operations through a guided flow to ensure metadata integrity and spec compliance before committing.

How do I regenerate and validate metadata before staging a commit?

To regenerate and validate metadata before staging a commit, the skill automatically handles metadata regeneration and validation during its guided flow. It ensures your .specd-metadata.yaml remains in sync with the latest codebase changes.

Can I group multiple spec directory changes into a single atomic commit?

Yes, you can group multiple spec directory changes into a single atomic commit. The skill operates across multiple spec directories to group related changes, apply guardrails, and stage everything for one conventional commit.

Do I need specific spec files to use automated commit guardrails?

Yes, automated commit guardrails require specific spec files to function. The skill reads specs/_global/commits/spec.md and verify.md to enforce conventions, verify messages, and apply the necessary guardrails before finalizing the commit.