ad-commit

Draft atomic Conventional Commits with DCO Signed-off-by sign-off.

728|16|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ad-commit
Source: https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime/tree/main/.agents/skills/ad-commit
Command: npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Atomic commits with DCO sign-off to ensure traceable, clean histories. ad-commit guides you through a four-phase workflow to ensure each commit is atomic and properly signed.

Core Features & Use Cases

  • Four-phase workflow: scope intake, stage-split when concerns mix, draft message in Conventional Commits format, and sign + write.
  • Uses git config user.name and user.email to populate Signed-off-by metadata for accountability.
  • Helps teams maintain compliant, review-friendly commit histories in local and CI workflows.

Quick Start

Tell ad-commit to prepare and sign off on your staged changes.

Frequently Asked Questions about ad-commit

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

FAQPage Schema
How do I automate atomic Conventional Commits with DCO sign-off in Git?

You can enforce atomic Conventional Commits with DCO sign-off by using a four-phase workflow that drafts commit messages and applies Signed-off-by metadata. This ensures traceable, clean Git histories.

How do I split mixed concerns into separate staged commits?

To split mixed concerns into separate staged commits, a stage-split phase separates intertwined changes before drafting. This ensures each commit remains atomic and properly documented as a single concern.

How does a DCO Signed-off-by line get populated for local Git workflows?

The DCO Signed-off-by line gets populated by reading git config user.name and user.email. This automatically injects your identity metadata into the commit message for accountability.

When do I need to use Conventional Commits format for my changelist?

You need the Conventional Commits format when maintaining review-friendly histories and ensuring changelist integrity. It is essential for teams requiring traceable, compliant commit documentation in local or CI workflows.

Can I use this commit management workflow in CI environments?

Yes, this commit management workflow supports CI environments. It helps teams maintain compliant, review-friendly commit histories by enforcing consistent atomic commits and DCO sign-off across automated pipelines.

What is the best way to enforce a four-phase commit signing process?

The best way to enforce a four-phase commit signing process is applying a structured workflow of scope intake, stage-split, message drafting, and sign and write. This guarantees atomic commits and proper DCO sign-off.