Aicommit
Create git commits that match repo style and append AI-Assisted trailers for later attribution and analysis.
Overview
aicommit is an agent skill most often used in Ship (also Build integrations, Operate iterate) that creates git commits with AI-Assisted trailers and optional AI-Agent and AI-Model metadata.
Install
npx skills add https://github.com/berend/my-skills --skill aicommitWhat is this skill?
- Seven-step workflow: status, diff, staged diff, recent log, selective stage, message, commit with trailers
- Requires AI-Assisted: true trailer; adds AI-Agent and AI-Model when Harness Identity Resolution succeeds
- Uses git commit --trailer when available; falls back to manual trailer lines at message end
- Explicit rule not to stage unrelated user changes
- Matches existing repository commit message style from git log --oneline -10
- Seven-step required workflow before committing
- Inspects recent commit style with git log --oneline -10
Adoption & trust: 1 installs on skills.sh; trending (+100% hot-view momentum).
What problem does it solve?
You want a proper git commit but also need consistent machine-readable markers that later prove which changes were AI-assisted.
Who is it for?
Solo developers who commit from the agent daily and want analyzable AI attribution without a separate commit bot.
Skip if: Repos where policy forbids AI trailers, or users who only need conventional commits with no metadata—use plain git instructions instead.
When should I use this skill?
User asks to commit, create a git commit, or mark a commit as AI-assisted.
What do I get? / Deliverables
You get a scoped commit matching repo style with AI-Assisted (and resolved AI-Agent/AI-Model) trailers ready for push or PR follow-up.
- Git commit with message matching repo style
- AI-Assisted trailer plus optional AI-Agent and AI-Model trailers
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Ship/review is the canonical shelf because disciplined commits with explicit AI metadata support pre-release hygiene and audit-friendly history, even though you invoke it throughout development. Review subphase reflects inspecting diffs, staging scope, and message quality before changes land on the mainline—not merely running tests or deploying.
Where it fits
After wiring an API client, run aicommit so only integration files ship with AI-Assisted trailers.
Before opening a PR, commit the final diff with trailers aligned to the last ten oneline messages.
Hotfix production config with a scoped commit that records AI-Agent for post-incident attribution.
How it compares
Use instead of improvised one-line agent commits that omit trailers and mix unrelated staged files.
Common Questions / FAQ
Who is aicommit for?
Solo and indie builders using AI coding agents who still commit from the terminal and want stable AI-Assisted trailers for later measurement.
When should I use aicommit?
During Build while landing feature slices, during Ship before opening or merging PRs, and during Operate when iterating fixes—whenever the user says commit, create a git commit, or mark a commit AI-assisted.
Is aicommit safe to install?
It instructs git write and staging only for requested changes; review the Security Audits panel on this page and your org’s policy on AI commit metadata before use.
SKILL.md
READMESKILL.md - Aicommit
# AI-Assisted Commit Use this skill when creating a git commit that should be marked as AI-assisted. ## Goal Create normal, high-quality git commits while adding stable commit trailers that make AI-assisted commits easy to analyze later. ## Required Workflow Before committing: 1. Inspect the working tree with `git status`. 2. Inspect the changes with `git diff` and, if relevant, staged changes with `git diff --staged`. 3. Inspect recent commit style with `git log --oneline -10`. 4. Stage only the files that belong to the requested change. 5. Do not stage unrelated user changes. 6. Write a concise commit message matching the repository's existing style. 7. Add the AI trailers with `git commit --trailer` when available. If `--trailer` is unavailable, place the same trailer lines manually at the very end of the commit message. ## Trailer Format Always include: ```text AI-Assisted: true ``` Also include `AI-Agent` and `AI-Model` when they can be resolved by the Harness Identity Resolution rules. Prefer this form when all values are available: ```sh git commit -m "Commit message" \ --trailer "AI-Assisted=true" \ --trailer "AI-Agent=<resolved-agent>" \ --trailer "AI-Model=<resolved-model>" ``` Omit only the unresolved trailer if either `AI-Agent` or `AI-Model` cannot be resolved. ## Harness Identity Resolution Before committing, derive trailer values from explicit coding harness context. Use `AI-Agent` when the harness explicitly names the coding agent or product identity. Normalize to a stable lowercase identifier when the identity is unambiguous. Examples: - "You are Codex" -> `AI-Agent: codex` - "You are opencode" -> `AI-Agent: opencode` Use `AI-Model` when the harness explicitly names the model identity. Prefer canonical provider/model IDs when the provider is explicit or obvious from the harness. Examples: - "based on GPT-5" in an OpenAI/Codex harness -> `AI-Model: openai/gpt-5` - "openai/gpt-5.5" -> `AI-Model: openai/gpt-5.5` - "claude-sonnet-4" in an Anthropic harness -> `AI-Model: anthropic/claude-sonnet-4` If either value is not explicitly available from the harness context, omit only that trailer. Do not infer values from general knowledge, marketing names, or user preference unless the user explicitly provides the trailer value for this commit. ## Commit Message Example ```text Commit message AI-Assisted: true AI-Agent: <resolved-agent> AI-Model: <resolved-model> ``` ## Rules - Keep the trailers at the very end of the commit message. - Prefer `git commit --trailer` over writing trailer lines manually. - Use exactly `AI-Assisted`, `AI-Agent`, and `AI-Model` as trailer keys. - Do not add `Co-authored-by` unless the user explicitly asks for it. - Do not commit secrets, generated junk, or unrelated files. - If tests or checks were run, mention the result to the user after committing, not in the trailers.