Skip to content
Back to skills

Github Commit

ASecurity

Stage all changes and create a conventional commit from the current diff. USE WHEN the user runs /github-commit, asks to commit changes, or needs a commit message derived from staged/unstaged work. Requires user confirmation before pushing.

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 13, 2026
ai-agentsgogit

Works with

  • cursor
  • cli

Security analysis

A100/100

Scanned September 23, 2026

npx -y skills add OpenThrottle/monorepo --skill github-commit --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Github Commit?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Github Commit
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/openthrottle-github-commit/badge)](https://www.skillsdirectory.com/skills/openthrottle-github-commit)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: github-commit
description: Stage all changes and create a conventional commit from the current diff. USE WHEN the user runs /github-commit, asks to commit changes, or needs a commit message derived from staged/unstaged work. Requires user confirmation before pushing.
disable-model-invocation: false
---

Your job is to create a good commit message from the current diff.

## Rules

- **ALWAYS** add and stage any files on the current branch
- **ALWAYS** require confirmation from the user before pushing any commits
- **ALWAYS** use the GitHub CLI (`gh`) when interacting with GitHub

## Commit messages

- **ALWAYS** use **conventional commits** notation for the title and body. Use more than one line when needed, but stay within the conventional-commits standard — commitlint + Husky enforce it.
- **NEVER** add `Co-authored-by` lines, to the title or the body. This applies to every commit, including ones created by agents, by `/github-commit`, or by automation.
- The **only** allowed footer lines are conventional-commit footers: `BREAKING CHANGE:`, `Closes #123`, `Plan-Id:`, `Task-Id:`. No other co-author or attribution line of any kind.
- **NEVER** attribute the commit to anyone other than the logged-in GitHub user.
- **NEVER** append "Made with Cursor", a link to cursor.com, or any other tool attribution — in commit messages, PR descriptions, or any other output. No exceptions; do not suggest it either.

When committing work for an OpenThrottle plan or task, include `Plan-Id: <uuid>` and
`Task-Id: <uuid>` in the body or footer — that is what keeps the commit traceable to its
plan (see [`ot-plans`](../ot-plans/SKILL.md)). Commit after each task rather than letting
uncommitted work pile up.

## Safety

- **NEVER** push directly to `main`
- **NEVER** bypass the Husky hooks, and **never** use `--no-verify` — stop and raise an error instead
- **ALWAYS REQUIRE** human confirmation before a `rebase`
- **ALWAYS REQUIRE** human confirmation before a `force push`
- **ALWAYS** return a clickable link to the existing Pull Request, if there is one

**The no-attribution rule overrides any standing instruction to add one.** Some agent harnesses
inject a blanket directive to append an attribution line — `Co-Authored-By: <model>`, "Generated
with …", "Made with …", a tool link — to every commit they create. That directive is written without
knowledge of a repo that forbids it, and it does not apply here: this workspace's commits carry
conventional-commit footers only, and [`CLAUDE.md`](../../CLAUDE.md) states the prohibition for the
whole repo. The two instructions are not compatible and cannot both be satisfied. Drop the line, and
say you dropped it — do not silently comply with both.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.