Menu
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/nearai/ironclaw --skill commitThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Use when adding or changing a Reborn integration — a new extension, a channel surface, model-callable tools, or a shared auth provider — or when deciding whether something is "a channel", "an extension", or "a tool". Maps the unified extension model (NEA-25) to the exact manifest sections, crates, seams, and tests.
Use when creating or editing agent guidance in this repo — anything under .claude/ (skills, commands, rules), AGENTS.md or CLAUDE.md files, or the runtime skills/ directory — or when guidance is found citing files, branches, or checks that no longer exist.
Use when adding or reviewing tests for Reborn behavior — choosing a test tier, covering a bug fix, testing model/tool-choice behavior, touching tests/integration or tests/fixtures/llm_traces, or when a test needs Postgres, Docker, or a live LLM.
Based on SOC occupation classification
Showing SKILL.md
| name | commit |
| version | 1.0.0 |
| description | Generate git commit messages from staged changes |
| activation | {"keywords":["commit","git commit"],"patterns":["(?i)(create|make|write|generate)\\s.*commit","(?i)commit\\s.*(message|changes|staged)"],"tags":["git","version-control"],"max_context_tokens":1000} |
When the user asks to create a commit:
shell with git status to see what files are staged and unstaged.shell with git diff --cached to see the exact changes that will be committed.shell with git log --oneline -5 to understand the repo's commit message style..env, credentials.json, API keys). Warn the user if such files are staged.git commit.git add <specific files> (never use git add -A or git add .).If the repo doesn't have a clear style, use:
<type>: <concise description>
<optional body explaining why>
Where type is: fix, feat, refactor, test, docs, chore.