brain-commit

Analyze Brain repository changes and push semantic commits non-interactively.

4|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/jonmagic/skills --skill brain-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brain-commit
Source: https://github.com/jonmagic/skills/tree/main/skills/brain-commit
Command: npx skills add https://github.com/jonmagic/skills --skill brain-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires claude, and includes scripts (resource) components.

What problem does it solve?

Brain developers often struggle to translate ad-hoc changes into meaningful, organized commits. This skill automates that process, producing semantic messages that reflect the intent of each change and ensuring a clean project history.

Core Features & Use Cases

  • Semantic grouping: Automatically cluster related file changes into logical commits (docs, meetings, summaries, transcripts, projects, etc.).
  • Non-interactive workflow: Performs pulls, analyzes, commits, and pushes without prompting for confirmation.
  • Consistent history: Formats commits using the conventional commit style and ensures remote consistency by preferring remote changes during merges.

Quick Start

From the Brain repository, run the brain-commit workflow to analyze unstaged/staged changes, generate semantic commits, and push them to origin.

Frequently Asked Questions about brain-commit

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

FAQPage Schema
How do I automatically group git changes into semantic commits?

You can automate semantic commits by running the brain-commit workflow, which analyzes unstaged and staged changes across Brain folders, clusters related files, and formats them using conventional commit style.

Can I push git commits to a remote repository without interactive prompts?

Yes, you can push git commits without interactive prompts. The workflow performs pulls, analyzes changes, commits, and pushes automatically to the remote without prompting for confirmation.

What is the best way to maintain a clean git history when syncing Brain repository changes?

The best way to maintain a clean git history is using a remote-friendly rebase and merge strategy. This Skill prefers remote changes during merges with a -X theirs strategy to ensure consistency without manual intervention.

Does this semantic commit automation work with the Brain repository structure?

Yes, this semantic commit automation is specifically designed for the Brain repository structure. It analyzes changes across Brain folders like docs, meetings, summaries, transcripts, and projects to generate meaningful commit messages.

Why does the automated commit process prefer remote changes during a merge?

The automated commit process prefers remote changes during a merge to ensure remote consistency and a clean project history. Using the -X theirs strategy prevents merge conflicts from blocking the non-interactively push workflow.

Do I need Claude to run the brain-commit workflow for version control?

Yes, you need Claude to run the brain-commit workflow for version control. Claude is a required dependency for executing the scripts that analyze Brain repository changes and generate semantic commits.