Commit Discipline
How to structure commits: atomic, conventional messages, never push to main/master directly.
Install
$ agentstack add skill-eoeboh-agent-skills-commit-discipline ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-eoeboh-agent-skills-commit-discipline) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Commit discipline
Run this whenever committing changes, opening a PR, or when asked to "commit this" / "push this."
Rules
- Commits are atomic: one logical change per commit. If a task touched two unrelated
things (e.g. a bug fix and an unrelated formatting pass), split into separate commits rather than bundling them.
- Commit messages follow conventional-commit style:
type(scope): summary, where type
is one of feat, fix, refactor, test, docs, chore, style, perf. Summary is imperative mood ("add", not "added" or "adds"), under ~72 chars on the first line. Add a body only if the "why" isn't obvious from the summary and diff.
- Never commit directly to main or master. If already on main/master, create a branch
first and say which branch name you're using before committing.
- Never force-push to a shared branch unless explicitly told to.
- Never commit files matching common secret patterns (.env, .pem, _key, credentials.*)
even if they were staged by something else — flag them and stop instead of committing silently.
- Never use
git add .orgit add -Ablindly. Review what's staged (git status)
and add specific files. If genuinely everything changed is meant to be committed, say so explicitly in the report rather than defaulting to it.
- After committing, show the commit hash and message, and confirm the branch. Do not
push unless explicitly asked to.
Edge cases
- If the working tree has unrelated uncommitted changes from a previous session mixed
in with the current task's changes: stop and ask which files belong to this commit rather than guessing.
- If a repo has its own CONTRIBUTING.md or commit convention documented, defer to that
over this skill's defaults and say so.
- If a pre-commit hook fails: report the failure verbatim, do not bypass with
--no-verify unless explicitly told to.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: EOEboh
- Source: EOEboh/agent-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.