vcs-commit

Generate and apply Conventional Commits messages across Git and JJ workflows.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/MisLink/agentry --skill vcs-commit-mislink
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vcs-commit
Source: https://github.com/MisLink/agentry/tree/main/agents/.agents/skills/vcs-commit
Command: npx skills add https://github.com/MisLink/agentry --skill vcs-commit-mislink

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional commits bring consistent, machine-readable history to every change by automatically generating and applying commit messages that reflect intent and scope.

Core Features & Use Cases

  • Detects the active VCS (Git or JJ) and follows colocated mode when both exist.
  • Analyzes the current changes (status and diff) to infer intent and propose a Conventional Commit message.
  • Prompts for file inclusion when changes are ambiguous and executes the final commit after user confirmation.

Quick Start

Describe the changes you want committed, and I will generate and run a Conventional Commits message.

Frequently Asked Questions about vcs-commit

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

FAQPage Schema
How do I automatically generate conventional commit messages from my git diff?

To generate conventional commit messages from your git diff, this Skill analyzes repository status and changes to infer intent and proposes a formatted commit message. It decides which files to include based on the diff and executes the commit after you confirm.

Does this conventional commits tool work with both Git and JJ version control?

Yes, this conventional commits tool works with both Git and JJ version control. It automatically detects the active VCS and follows colocated mode when both exist, ensuring compatibility across your workflows.

How do I create a conventional commit when only some modified files are relevant?

To create a conventional commit with ambiguous file changes, the Skill prompts you for file inclusion when changes are unclear. It analyzes the diff to decide which files to include and commits only the confirmed files.

Can I infer the commit language automatically from my existing version control history?

Yes, you can infer the commit language automatically from your existing version control history. The Skill analyzes your past commits to match the language and enforces conventional commits syntax for the new message.

What is the best way to automate version-control commit management for consistent history?

The best way to automate version-control commit management is by analyzing diffs to generate machine-readable conventional commits. This enforces consistent syntax, reflects change intent and scope, and applies the commit directly after confirmation.