Borrowing it
Nothing to install: this file belongs to TechHU-GS/cc-discipline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TechHU-GS/cc-discipline/main/.claude/skills/commit/SKILL.mdgit clone --depth 1 https://github.com/TechHU-GS/cc-disciplineWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/techhu-gs/cc-discipline/commit)<a href="https://agentmods.dev/skills/techhu-gs/cc-discipline/commit"><img src="https://agentmods.dev/badge/skills/techhu-gs/cc-discipline/commit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/techhu-gs/cc-discipline/commit"><img src="https://agentmods.dev/badge/skills/techhu-gs/cc-discipline/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00021 | $0.00475 |
| Opus 5.5 | $0.00008 | $0.00190 |
| Sonnet 5.5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
commit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Execute the smart commit flow. Core principle: commit code and knowledge together.
1. Run Tests
Check the test command in CLAUDE.md and execute it. If tests fail, stop the commit and report. Skip this step for projects with no configured test command.
2. Update Knowledge Files
Check each in order (simple changes may skip):
docs/progress.md — Does this change constitute a milestone or significant progress? If so, append a record. Also check the "Working Context" section: are Key Commands, Current Workflow, Tools & Scripts, Environment State, and Gotchas up to date? These are your lifeline after compact — if they're stale, a post-compact Claude starts from scratch.
docs/todo.md — Did this change finish anything listed there? Delete it. Did it turn up follow-up work? Add it under Now, or under Later with a condition for revisiting it.
docs/debug-log.md — Are there debug sessions that need to be closed or updated?
CLAUDE.md — Are there new components, interfaces, known pitfalls, or architectural changes to sync? Did you create any helper scripts or tools this session? If so, register them in the "Project Tools" section of CLAUDE.md NOW — not in progress.md (which is ephemeral), but in CLAUDE.md (which is permanent).
Auto Memory — Are there cross-session lessons worth remembering? (bug patterns, API pitfalls, debugging tips) Update memory files, keeping MEMORY.md under 200 lines.
3. Execute git commit
git status
git diff --staged && git diff
git log --oneline -5
- Selectively
git add(don't usegit add -A) - Include docs/ and CLAUDE.md changes in the commit if modified
- Don't commit .env, credentials, or other sensitive files
- Follow existing commit message style
- Don't push (unless user explicitly requests it)
- If pre-commit hook fails, fix the issue and create a new commit (don't --amend)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed · +2 lines dc9ccfe019d8
- 2mo ago First seen · 41 lines · 21 tokens per session scan A d57ca8d8fa5b
commit is a skill published in the GitHub repository TechHU-GS/cc-discipline (0 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 475 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
commit
Create git commits with user approval and no Claude attribution.
omh-github-issue-intake
This is an OMH github-issue-intake workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
omh-commit-pr-authoring
This is an OMH commit-pr-authoring workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
git-flow
Use this skill when committing, branching, opening a pull request, resolving conflicts, or recovering from a git mistake in any repository. Triggers: user mentions "commit", "branch", "PR", "pull request", "merge", "rebase", "conflict", "stash", "cherry-pick", "revert", "bisect", "reflog", "force push".
ring:generating-pr-descriptions
Generating pull request descriptions from git branch changes with automatic title generation, change-type detection, and smart analysis. Uses branch-only scope to avoid full history analysis. Use when preparing a PR for review. Skip when the PR is a single trivial commit or description already exists.