Commit, pull, and push changes using make push with a ticket-prefixed message.
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
Commit the current working tree changes using this project's `make push` target.
`make push` = `make commit` + `git push`. `make commit` alone typechecks, pulls, builds, tests,
ownership-lints, stages and commits, but does NOT push — so this skill uses `make push`.
The ticket ID is: $ARGUMENTS
## 1. Validate the ticket ID
If `$ARGUMENTS` is empty or non-numeric, stop and ask the user to provide a numeric ticket ID (e.g., `/commit 1234`). Do not proceed.
## 2. Analyze changes
Run these commands in parallel to understand what will be committed:
- `git status` (never use `-uall`)
- `git diff`
- `git diff --cached`
- `git log --oneline -5`
If the working tree is clean (no staged, unstaged, or untracked changes), inform the user there is nothing to commit and stop.
Remember: `make push` runs `git add --verbose :/ .` before committing, so ALL working tree changes will be included, not just staged files. It also runs `git pull` BETWEEN typecheck and build, so the build/test/ownership gates run against the MERGED tree rather than a stale one.
## 3. Check for secrets
…
The line at the top of this page pins the label git:20260830.6386046, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_tvudaxweicvbwxha
GET https://markdownregistry.com/api/v1/resolve?ref=appshapes/brigade/commit
GET https://markdownregistry.com/api/v1/blob/6f9bbd062f61bed15b9a9be22c4969c74e4a5086bc1d93e251072f5d1491a945
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.
appshapes/brigade · .claude/skills/trello-done/SKILL.md · Close a Trello card whose work is done — post the closing comment, mark the card complete and archive it — with the…
appshapes/brigade · codex/brigade/skills/email/SKILL.md · Email a person through the team's Brigade mail gateway: `$brigade:email <address> <text>` sends the text to that email…
appshapes/brigade · codex/brigade/skills/join/SKILL.md · Join this project's Brigade team from inside the session: `$brigade:join <path>` runs `brigade team join --secret-file…
appshapes/brigade · codex/brigade/skills/sessions/SKILL.md · Show the team's sessions: the `$brigade:sessions` skill runs `brigade sessions` and prints its output unchanged. with…
appshapes/brigade · codex/brigade/skills/setup/SKILL.md · How a HUMAN creates or joins a Brigade team — `team create` from a terminal, `$brigade:join <path>` (or `brigade team…
appshapes/brigade · codex/brigade/skills/slack/SKILL.md · Message a person or a channel on Slack through the team's Brigade Slack gateway: `$brigade:slack <to> <text>` sends the…
appshapes/brigade · codex/brigade/skills/team-messaging/SKILL.md · Message the coding sessions of OTHER PEOPLE on your Brigade team (cross-user, cross-machine; Codex CLI, Claude Code and…
pedrohcgs/claude-code-my-workflow · .claude/skills/commit/SKILL.md · Commit the current work — runs the quality, consistency and passport gates, branches off main if needed, stages…
openonion/connectonion · connectonion/useful_skills/commit/SKILL.md · Create git commits with good messages. Use when user says "commit", "create commit", or asks to commit changes.
aiskillstore/marketplace · skills/0xmsc/commit/SKILL.md · Helps write conventional commit messages, create atomic commits, and follow git best practices. Use when the agent…
asymmetric-al/core · .agents/skills/commit/SKILL.md · Create a Conventional Commit message for staged changes and run git commit. Use when changes are staged and you need a…
justxor/claude-code-pro-course · starter-kit/.claude/skills/commit/SKILL.md · Создаёт git-коммит в формате Conventional Commits по текущим изменениям. Используй, когда просят закоммитить или…