Agent skill

brain-commit

Analyze changes in the Brain repo and create semantic commits. Use when the user wants to commit their brain changes with meaningful, organized commit messages. Analyzes staged/unstaged changes, groups related files, creates appropriate commits, and pushes without user interaction.

View SKILL.md on GitHub Repository
Stars 4
Forks 0

Install this agent skill to your Project

npx add-skill https://github.com/jonmagic/skills/tree/main/skills/brain-commit

SKILL.md

Brain Commit

Intelligently commit changes to the Brain repository (~/Brain) with semantic commit messages, then push to the remote. This skill is non-interactive: it should do its best without asking for confirmation.

Workflow

  1. Navigate to Brain: cd ~/Brain

  2. Sync from remote (non-interactive, prefer remote changes):

    • git pull --rebase --autostash -X theirs
    • If rebase fails, fallback to merge without prompts: git rebase --abort then git pull --no-rebase -X theirs --no-edit

  3. Check status: Run git status to see what's changed

  4. Analyze changes: Group files by type/purpose:

    • Weekly Notes/ → docs(weekly): ...
    • Daily Projects/ → docs(daily): ...
    • Meeting Notes/ → docs(meetings): ...
    • Snippets/ → docs(snippets): ...
    • Executive Summaries/ → docs(summaries): ...
    • Transcripts/ → docs(transcripts): ...
    • Projects/ → docs(projects): ...
    • Archive/ → chore(archive): ...
    • Skills/config files → chore: ...
    • Multiple directories in one logical session → can combine if related

  5. Create commits: For each logical group:

    • Stage the related files: git add <files>
    • Commit with semantic message: git commit -m "type(scope): description"

  6. Push: git push after all commits are created

  7. Report: Show what was committed and pushed

Semantic Commit Format

type(scope): short description

- Optional bullet points for details

Types for Brain

  • docs - Most content (notes, projects, snippets)
  • chore - Maintenance (archiving, config changes)
  • feat - New templates or structural additions

Scopes

  • weekly - Weekly Notes
  • daily - Daily Projects
  • meetings - Meeting Notes
  • snippets - Snippets
  • summaries - Executive Summaries
  • transcripts - Transcripts
  • projects - Projects folder
  • archive - Archive folder

Examples

Single directory changed

docs(daily): add queue outcomes migration plan

- Researched spamurai-next and hamzo codebases
- Documented migration approach for 14 outcomes
- Created implementation checklist

Multiple related changes

docs(weekly): update week of 2026-01-11

- Added TODO items
- Logged Monday activities

Mixed changes (multiple commits)

First commit:

docs(daily): add auto-archive queue entries plan

Second commit:

docs(meetings): add notes from team sync

Edge Cases

  • No changes: Report "Nothing to commit, working tree clean"
  • Only untracked files: Add them to the most sensible group and proceed
  • Large number of files: Group by directory, don't create too many commits
  • Single file change: One simple commit is fine
  • Non-fast-forward push: Re-run the sync step once, then retry push

Safety

  • Always show what will be committed before committing, but do not pause for confirmation
  • Conflict resolution strategy: always prefer remote changes by using -X theirs during rebase/merge to avoid interactive conflict prompts
  • Never force push
  • Never amend commits unless explicitly asked

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

jonmagic/skills

markdown-to-standalone-html

Convert Markdown documents (*.md files) to self-contained HTML files with embedded images. Use when you need a portable, offline-friendly single HTML file from Markdown—ideal for blog posts, essays, reports, or any content that should work without external dependencies.

4 0
Explore
jonmagic/skills

brain-operating-system

Quick reference for operating within jonmagic's second-brain workspace. Use when working with files in the brain repository—provides directory structure, naming conventions, append-only norms, wikilink patterns, frontmatter requirements, project conventions, and file organization rules. Essential for understanding where to create files, how to name them, and how to maintain continuity with existing structures.

4 0
Explore
jonmagic/skills

semantic-commit

Generate semantic commit messages from staged changes. Use when committing code to produce consistent, well-structured commit messages following conventional commit format.

4 0
Explore
jonmagic/skills

archive-meeting

Archive one or more meetings into the brain repo by importing Zoom transcript folders (~/Documents/Zoom/*) and/or downloaded Teams .vtt files (~/Downloads/*.vtt), then generating a transcript markdown file, an executive summary, and creating meeting notes. Use when the user says "archive meeting", "archive my last meeting", "process these transcripts", or similar.

4 0
Explore
jonmagic/skills

session-to-brain

Archive a Copilot CLI session to the brain. Creates a daily project file with the session transcript and adds a resume link to the weekly note. Use when ending a significant work session to preserve context for future reference.

4 0
Explore
jonmagic/skills

create-bookmark

Save a URL as a bookmark with frontmatter and a blurb or AI summary. Use when the user says "bookmark this", "save this link", or shares a URL they want to remember.

4 0
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results