Stage current changes and create a Conventional Commits-style commit matching this repo's history. Use when the user says "commit", "commit this", or asks for a commit message. Pre-commit hooks will run automatically.
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
Create a single commit using Conventional Commits format, matching the style in `git log`.
## Workflow
1. Run these in parallel:
- `git status` (see what's untracked / modified)
- `git diff` and `git diff --staged` (see what will be committed)
- `git log --oneline -10` (match recent style)
2. Review the changes and group them into ONE commit. If the diff spans clearly unrelated changes, ask the user whether to split.
3. Stage explicitly (avoid `git add -A` / `git add .`):
- Add the specific files that belong in this commit by name.
- Never stage `.env`, credentials, or other secrets. If `gitleaks` would flag it, don't stage it.
4. Compose the commit message:
- Subject: `<type>: <short imperative summary>` — lowercase, no trailing period, ≤72 chars.
- Types in use here: `feat`, `fix`, `chore`, `docs`, `refactor`, `test`.
- Body (optional): explain the **why**, not the **what**. Wrap at 72 chars.
5. Commit with a HEREDOC so formatting survives:
```bash
git commit -m "$(cat <<'EOF'
feat: <subject>
<optional body>
EOF
)"
```
…
The line at the top of this page pins the label git:20260710.ecf66e2, 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.
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 (1948 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
tam159/next-role · 62 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ans2f4gqb57poo75
GET https://markdownregistry.com/api/v1/resolve?ref=tam159/next-role/commit
GET https://markdownregistry.com/api/v1/blob/e9e0a721e4c2175bf194b1e63c393abfe730e4e4bf3be80d29823a9942b2fb00
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.
tam159/next-role · .agents/skills/agent-browser/SKILL.md · Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages…
tam159/next-role · .agents/skills/archify-review/SKILL.md · Review Archify issues, PRs, or code through value, cost, and impact to support evidence-based maintenance decisions…
tam159/next-role · .agents/skills/frontend-design/SKILL.md · Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to…
tam159/next-role · .agents/skills/quality/SKILL.md · Run the repo's quality gate — pre-commit on the files you changed by default, or the full `pre-commit run --all-files`…
tam159/next-role · .agents/skills/upgrade-backend-deps/SKILL.md · Upgrade Python backend dependencies to their latest compatible versions. Resolves the lockfile with `uv lock…
tam159/next-role · .agents/skills/upgrade-frontend-deps/SKILL.md · Upgrade the Next.js frontend's pnpm dependencies to their latest versions in verified waves. Inventories with `pnpm…
tam159/next-role · .agents/skills/write-prd/SKILL.md · Generate a concise PRD for the feature built in the current session and save it to docs/prd/. Use this skill whenever…
tam159/next-role · .claude/skills/agent-browser/SKILL.md · Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages…
tam159/next-role · .claude/skills/archify-review/SKILL.md · Review Archify issues, PRs, or code through value, cost, and impact to support evidence-based maintenance decisions…
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 по текущим изменениям. Используй, когда просят закоммитить или…
