awesome-openclaw-agents is a curated collection of ready-to-use SOUL.md configurations that define AI agents for tasks across areas such as development, marketing, finance, support, and automation. It is for OpenClaw users who want predefined agent roles and workflows to adapt or deploy. The catalogue entries are agent-related skills drawn from this collection.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/mergisi/awesome-openclaw-agents/git-commit-writernpx skills add mergisi/awesome-openclaw-agents --skill git-commit-writergit clone --depth 1 https://github.com/mergisi/awesome-openclaw-agentsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/mergisi/awesome-openclaw-agents/git-commit-writer)<a href="https://agentmods.dev/skills/mergisi/awesome-openclaw-agents/git-commit-writer"><img src="https://agentmods.dev/badge/skills/mergisi/awesome-openclaw-agents/git-commit-writer.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00053 | $0.00647 |
| Opus 5 | $0.00026 | $0.00324 |
| Sonnet 5 | $0.00011 | $0.00129 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
git-commit-writer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Writer
Generate a disciplined commit message from the currently staged changes. Opinionated about style: imperative mood, concise title, body that explains why not what.
When to use
- User says "write a commit message", "/commit", "commit this"
- User has staged changes and asks to review them before committing
- User asks "what should this commit be called"
Do NOT use this skill to actually run git commit unless the user explicitly asks — just draft the message and show it.
Instructions
- Run
git status --shortwith the Bash tool. Confirm there are staged changes. If nothing is staged, stop and tell the user. - Run
git diff --stagedto read the full staged diff. If the diff is large (>500 lines), also rungit diff --staged --statto get a file-level overview first. - Run
git log --oneline -10to learn the repo's commit convention. Look for:- Conventional Commits prefixes (
feat:,fix:,chore:) — if present, match the style. - Title case vs sentence case.
- Whether bodies are used or not.
- Any ticket / issue prefix (e.g.
[PROJ-123]).
- Conventional Commits prefixes (
- Draft a message following these rules:
- Title: imperative mood ("Add X", not "Added X" or "Adds X"), max 70 characters, no trailing period.
- Body (if needed): blank line after title, then 1-3 short paragraphs or bullets explaining why the change is necessary, what problem it solves, what trade-offs were made.
- Never use the word "refactor" alone — always say what was refactored and why ("Extract retry loop into helper to share with job runner").
- Never write "Update file.js" — describe the behavior change, not the file touched.
- Never invent a ticket number. If the repo uses them but you can't infer one, leave it out.
- Show the drafted message in a fenced code block. Ask the user if they want you to run
git commitwith it. Do not commit automatically.
Anti-patterns to reject
- "Various fixes" / "Updates" / "WIP" — reject and ask for specifics from the diff.
- "Refactor code" — must name the unit being refactored.
- Title >70 chars — shorten or move detail to body.
- Past tense or "-ing" forms — rewrite to imperative.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 48 lines · 53 tokens per session scan A a7d6021dd614
git-commit-writer is a skill published in the GitHub repository mergisi/awesome-openclaw-agents (3,952 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 647 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
squash-merge
Squash-merge a PR into zeroclaw-labs/zeroclaw master with fully preserved commit history in the squash message body. Use this skill when the user explicitly mentions squash-merging, merging a specific PR number, landing a PR, or 合入 — e.g. "squash-merge #123", "merge PR 456", "land #789", "合入 #123", "/squash-merge…
pr-submission
PR title format, commit conventions, and pre-PR checklist for SkillHub. Use when preparing or reviewing pull requests.
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
run-work
Execute a work unit end-to-end: sequence tasks by dependency, implement, test between tasks, commit, and track progress. Use to deliver a complete feature in one session. Invoked as /agiflow:run-work . Uses getworkunit, listtasks, updatetask, getworkunitprogress.
create-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
commit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.