Skip to content
Back to skills

Safe Commit

ASecurity

Stage and commit DockTerm changes safely with a clear, conventional message.

  • 7 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 1, 2026
ai-agentsgit

Security analysis

A100/100

Scanned October 1, 2026

npx -y skills add munvard/dockterm --skill safe-commit --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Safe Commit?

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

Security grade badge for Safe Commit
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/munvard-safe-commit/badge)](https://www.skillsdirectory.com/skills/munvard-safe-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: safe-commit
description: Stage and commit DockTerm changes safely with a clear, conventional message.
---

# Safe commit

1. Run `git status` and review exactly what will be committed.
2. Stage intentionally — don't blindly `git add -A`. Keep unrelated changes out.
3. Make sure `npm run typecheck && npm test && npm run build` pass first.
4. Write a clear conventional message (`feat:`, `fix:`, `chore:`, `docs:`) that
   says what changed and why.
5. Never force-push or rewrite shared history without explicit confirmation; if a
   force push is truly needed, use `--force-with-lease`.

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…