ork-commit SKILL.md skillA

ork-commit from yonatangross/orchestkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add yonatangross/orchestkit/ork-commit@git:20261116.0625e64

Pins git:20261116.0625e64 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
yonatangross/orchestkit
Path
plugins/ork-codex/skills/ork-commit/SKILL.md
Versions recorded
1
Latest version
git:20261116.0625e64, committed Nov 16, 2026
Size
1,340 bytes
Repository stars
304
License
MIT

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.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# 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.

Read the whole file at its exact version.

How to install

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 git:20261116.0625e64, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add yonatangross/orchestkit/ork-commit@sha256:72c001098330234b

The line at the top of this page pins the label git:20261116.0625e64, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_cu3sbx7lyxxd3eme.svg)](https://markdownregistry.com/a/art_cu3sbx7lyxxd3eme)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in yonatangross/orchestkit/ork-commit since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of ork-commit from somewhere else? Ask it: where did my ork-commit come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 1 version of this file, committed on Nov 16, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261116.0625e64 latest2026-11-16 0625e64 1,340 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (1340 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

yonatangross/orchestkit · 304 stars · license MIT · pushed 2026-11-16 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_cu3sbx7lyxxd3eme
GET https://markdownregistry.com/api/v1/resolve?ref=yonatangross/orchestkit/ork-commit
GET https://markdownregistry.com/api/v1/blob/72c001098330234bd87347c46c77f36a9807c5d27a42ae269d45a0d575659d54

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from yonatangross/orchestkit

AGENTS.md AGENTS.md file
yonatangross/orchestkit · AGENTS.md
git:20261022.980c9bf · audit A · 304 stars
CLAUDE.md CLAUDE.md file
yonatangross/orchestkit · CLAUDE.md
git:20261029.22dfd98 · audit A · 304 stars
AGENTS.md@docs/site AGENTS.md file
yonatangross/orchestkit · docs/site/AGENTS.md
git:20260823.5e31893 · audit A · 304 stars
CLAUDE.md@docs/site CLAUDE.md file
yonatangross/orchestkit · docs/site/CLAUDE.md
git:20260823.5e31893 · audit B · 304 stars
ork-assess SKILL.md skill
yonatangross/orchestkit · plugins/ork-codex/skills/ork-assess/SKILL.md · Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use…
git:20260819.cf231c6 · audit A · 304 stars
ork-brainstorm SKILL.md skill
yonatangross/orchestkit · plugins/ork-codex/skills/ork-brainstorm/SKILL.md · Compare plausible implementation, architecture, product, or operational approaches before committing to one. Use when a…
git:20260819.cf231c6 · audit A · 304 stars
ork-create-pr SKILL.md skill
yonatangross/orchestkit · plugins/ork-codex/skills/ork-create-pr/SKILL.md · Push the current feature branch and open a pull request with a conventional title and a summary of what changed and how…
git:20261116.0625e64 · audit A · 304 stars
ork-explore SKILL.md skill
yonatangross/orchestkit · plugins/ork-codex/skills/ork-explore/SKILL.md · Map an unfamiliar codebase, feature, architecture, data flow, or operational path with file-backed evidence. Use when a…
git:20260819.cf231c6 · audit A · 304 stars
ork-glyph SKILL.md skill
yonatangross/orchestkit · plugins/ork-codex/skills/ork-glyph/SKILL.md · Render an answer inline as compact ASCII or box-drawing art with semantic status icons. Use for status, inventories…
git:20260919.ab8d756 · audit A · 304 stars
ork-implement SKILL.md skill
yonatangross/orchestkit · plugins/ork-codex/skills/ork-implement/SKILL.md · Make an approved, scoped change and prove the affected behavior. Use when a request asks to implement, build, add, or…
git:20260825.dc3bfe8 · audit A · 304 stars
ork-review-pr SKILL.md skill
yonatangross/orchestkit · plugins/ork-codex/skills/ork-review-pr/SKILL.md · Review a pull request or branch for correctness, regressions, security, operational risk, and missing evidence. Use…
git:20260819.cf231c6 · audit A · 304 stars
ork-verify SKILL.md skill
yonatangross/orchestkit · plugins/ork-codex/skills/ork-verify/SKILL.md · Verify that existing work is ready to merge, release, or hand off using an explicit evidence contract. Use when a…
git:20260819.cf231c6 · audit A · 304 stars

Every file in yonatangross/orchestkit

Browse by kind, by grade A, or by owner.