commit

Summarize worktree changes and generate a semantic commit message.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inspect the current trading-bot worktree, summarize the meaningful changes, propose a semantic commit message, and warn about unsafe or misleading diffs. Use when preparing a commit after runtime, operator panel, experiment, analytics, or skill-system changes.

Core Features & Use Cases

  • Group changes by operational purpose and produce a single, semantic commit message.
  • Flag risky edits in risk, execution, operator actions, config, startup, or secrets handling.
  • Validate that generated diffs do not include secrets, local data, logs, dist, or environment files; provide a clear validation report.

Quick Start

Summarize the current worktree changes and propose a semantic commit message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate a semantic commit message from my worktree changes?

This Skill summarizes worktree changes and generates a semantic commit message by grouping modifications by operational purpose. It applies across runtime, operator panel, experiment, analytics, and skill-system modifications.

How can I check if my staged diff contains secrets or unintended artifacts?

You can validate that your staged diff excludes secrets, local data, logs, dist, or environment files by using the Skill's built-in validation report. It checks generated diffs and warns about unsafe or misleading changes before committing.

What is the best way to group repository changes by operational purpose for a commit?

The best way to group repository changes by operational purpose is to let the Skill analyze your worktree diff and categorize runtime, operator panel, experiment, and analytics updates into a single semantic commit message.

Can I flag risky execution or config edits before committing worktree changes?

Yes, you can flag risky execution, operator action, config, startup, or secrets handling edits. The Skill automatically detects these risky edits in your worktree and warns you before you finalize the commit.

Does this commit summarizer work with experiment and analytics modifications?

Yes, this commit summarizer works with experiment and analytics modifications. It explicitly supports summarizing changes across runtime updates, operator panels, experiments, analytics, and skill-system modifications within the repository.