commit

Create conventional commits with embedded generation metadata from staged changes.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/jburns24/skills --skill commit-jburns24
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/jburns24/skills/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/jburns24/skills --skill commit-jburns24

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill creates a structured git commit message that includes embedded generation metadata — the model used, the full contents of the driving plan file, and any changes that deviated from the plan. This provides traceability between what was planned and what was actually shipped.

Core Features & Use Cases

  • Create conventional commits with embedded generation metadata such as the model name, plan contents, and any unplanned changes.
  • Read and verify the relevant plan file from the user's context to ensure changes align with the plan.
  • Detect unplanned changes by comparing staged files against the plan and surface deviations for confirmation.

Quick Start

Ask the AI to create a plan-driven commit of your staged changes with embedded generation metadata.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I embed plan metadata in conventional commits for traceability?

To embed plan metadata in conventional commits, this skill reads your plan file, detects unplanned changes by comparing staged files, and outputs a commit message with an HTML comment containing JSON metadata of the model, plan, and deviations.

Can I track planned versus delivered changes in git commit messages?

Yes, you can track planned versus delivered changes in git by generating commit messages that embed the original plan contents and any unplanned modifications as JSON metadata within an HTML comment for full traceability.

How do I automatically detect unplanned changes before committing staged files?

You can detect unplanned changes before committing by comparing your currently staged files against the driving plan file, which surfaces deviations for confirmation and records them in the commit metadata.

What is a conventional commit with embedded generation metadata?

A conventional commit with embedded generation metadata is a structured git commit message that includes an HTML comment containing JSON with the model name, full plan contents, and any deviations to trace planned versus delivered changes.

Do I need a plan file to create traceable commits with generation metadata?

Yes, you need a plan file in your context to create traceable commits, as the skill reads and verifies the plan file to compare against staged changes and embed the plan contents in the commit metadata.