agent-commit
Analyze changes and create a meaningful commit with agent authorship. Internal skill for evolve_loop.
Best use case
agent-commit is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Analyze changes and create a meaningful commit with agent authorship. Internal skill for evolve_loop.
Teams using agent-commit should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/agent-commit/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How agent-commit Compares
| Feature / Agent | agent-commit | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Analyze changes and create a meaningful commit with agent authorship. Internal skill for evolve_loop.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Agent Commit Creates a git commit with meaningful message based on skill output and actual file changes. ## When to Use This skill is called automatically by `evolve_loop.py` after a content-modifying skill completes. It is not intended for manual invocation. ## Input You will receive: 1. The name of the skill that just ran 2. A summary or excerpt of that skill's output ## Instructions ### 1. Check for Changes Run `git status --porcelain` to see if there are uncommitted changes. If there are no changes, output "No changes to commit" and stop. ### 2. Analyze the Changes Run `git diff` (or `git diff --cached` if files are staged) to understand what was modified. Focus on: - Which files were changed (especially content files in `obsidian/`) - The nature of the changes (new content, edits, deletions) - Key themes or topics affected ### 3. Generate Commit Message Create a commit message with a summary line and body: ``` <type>(<skill>): <summary> <body> ``` **Summary line** (required, under 72 chars): - `<type>` is one of: `feat`, `fix`, `refine`, `research`, `chore` - `<skill>` is the skill name (e.g., `deep-review`, `condense`, `expand-topic`) - `<summary>` describes WHAT was done and to WHICH file(s) - **File paths must include parent directory** (e.g., `topics/free-will.md` not just `free-will.md`) **Body** (required for content changes): - 2-5 bullet points summarizing key changes - For condense: before/after word counts, what was cut vs preserved - For deep-review: what issues were found and fixed - For expand-topic: key themes covered - For research: sources consulted, main findings **Good examples:** ``` refine(condense): reduce topics/free-will.md from 9567 to 2985 words - Cut quantum Zeno redundancy (7+ mentions → 1 via link) - Removed extended sections on altered states, process philosophy - Preserved core phenomenology arguments and Mary's Room - Kept tenet connections and cross-links intact ``` ``` refine(deep-review): improve clarity in concepts/qualia.md - Fixed circular definition in opening paragraph - Added concrete examples for inverted spectrum argument - Strengthened connection to hard problem article ``` **Bad examples:** - `auto(deep-review): Automated execution` (too vague, no body) - `Updated files` (no context) - `refine(condense): reduce free-will.md` (missing parent directory - is it topics/ or concepts?) ### 4. Create the Commit Stage all changes and commit with agent authorship. Use a HEREDOC for the multi-line message: ```bash git add -A git commit --author "unfinishablemap.org Agent <agent@unfinishablemap.org>" -m "$(cat <<'EOF' <summary line> - bullet point 1 - bullet point 2 EOF )" ``` ### 5. Output the Result Output the commit hash and message so the calling system can log it. ## Important - Keep commit messages under 72 characters for the summary line - **Always include parent directory in file paths** (e.g., `topics/free-will.md`, `concepts/qualia.md`, `research/notes.md`) - Focus on the "what" and "which file" - the skill name already tells us "how" - If multiple files changed, mention the primary one and note others exist - Never include time estimates or subjective assessments in commit messages
Related Skills
git-commit-for-ai-agents
Commit changes to a git repository. Use whenever a git commit is to be executed.
adversarial-committee
Committee of personas with opposing propensities forcing genuine debate
push-commit
Stage all changes, commit with a descriptive message, and push to the remote. Trigger with "push commit", "commit and push", "push changes", "/push-commit".
git-create-commit-skill
Use when creating git commits - mandates commits format with required scopes for all new commits, provides scope discovery from codebase structure, and prevents rationalization under pressure (emergency, fatigue, ambiguity)
git-commit-push
This skill should be used when the user wants to commit their work to git and push to GitHub. It guides through reviewing changes, crafting meaningful commit messages following project conventions (including Conventional Commits when detected), creating commits with security checks, and pushing to remote repositories.
Git Commit Helper
Creates well-formatted conventional commits with intelligent change analysis. Use when creating commits, committing changes, staging files, or when the user mentions "commit", "git commit", or wants to save their work to version control. Analyzes diffs to suggest splitting commits when multiple concerns are detected.
commit
diff分析 → 論理的に分割コミット。conventional commitメッセージを自動生成。
commit-quick
codemapの更新をスキップして素早くgit commitする。変更内容を分析し、適切なコミットメッセージを自動生成してコミットを作成する。
commit-feature
Stage changes, create conventional commit (no co-author), push to origin, and add detailed PR comment with session context
commit-conventions
This skill should be used when writing commit messages, when asked about commit format, when reviewing a commit message, or when creating a git commit. Provides Conventional Commits format and project-specific conventions.
commit-assistant
Provides conventional commits guidance and auto-generates commit messages from git changes. Integrates with /ccpm:commit for automated git commits linked to Linear issues. Auto-activates when users ask about committing, creating git commits, or discussing commit message formats.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.