ork-commit · git:20261116.0625e64 · 2026-11-16 · sha256 72c001098330234b

ork-commit git:20261116.0625e64A

Immutable. This exact content never changes and is served at /api/v1/blob/72c001098330234b.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_cu3sbx7lyxxd3eme/72c001098330234bd87347c46c77f36a9807c5d27a42ae269d45a0d575659d54.json

Then /plugin install ork-commit@markdownregistry-cu3sbx7lyxxd3eme in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: ork-commit
description: Create one Conventional Commit of the intended changes on a feature branch, with the repository's own hooks and signing left on. Use when a request asks to commit, save progress as a commit, or write a commit message. Do not use for incidental commits inside other work, to push, or to open a pull request.
---

# Ork Commit

Refuse to commit on the default branch (`main`, `master`, `dev`, or what `origin/HEAD` names); ask for a feature branch instead. Read `git status` and `git diff --staged` first, and stage only the files that belong to the change. Never stage secrets, `.env` files, credentials, or a diff that is only generated output.

Write the message as `type(scope): subject`, with type one of feat, fix, docs, refactor, test, chore, perf, ci, build. Keep the subject under 72 characters and match the type to what the diff does. Reference the issue number (`#N`) when the branch names one. Add a short body that says why when the subject cannot.

Run the commit with the repository's hooks and signing as configured. Never pass `--no-verify` or `--no-gpg-sign`, and never change the signing config. If a hook or the signer fails, report its exact output and stop; fix the cause, then commit again.

Finish by showing `git log -1 --stat`, so the files in the commit are visible. Do not push.