Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/u9401066/rootcause-mcp/git-precommitnpx skills add u9401066/rootcause-mcp --skill git-precommitgit clone --depth 1 https://github.com/u9401066/rootcause-mcpWhat 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 | $0.00000 | $0.01633 |
| Opus 5 | $0.00000 | $0.00816 |
| Sonnet 5 | $0.00000 | $0.00327 |
| Haiku 4.5 | $0.00000 | $0.00163 |
Grade A, and why
git-precommit 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 2d 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.
This is a copy
100% identical to git-precommit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: git-precommit description: Orchestrate pre-commit workflow including Memory Bank sync, README/CHANGELOG/ROADMAP updates. Triggers: GIT, gc, push, commit, 提交, 準備 commit, 要提交了, git commit, pre-commit, 推送, stage, 暫存, checkin, 簽入, submit, save, 準備發布, ready to commit, 要推了. version: 2.2.0 category: workflow compatibility:
- claude-code
- github-copilot
- vscode
- codex-cli dependencies:
- memory-updater
- readme-updater
- changelog-updater
- roadmap-updater
- ddd-architect allowed-tools:
- read_file
- write_file
- list_dir
- grep_search
- get_changed_files
- run_in_terminal
Git 提交前工作流（編排器）
描述
協調多個 Skills 完成 Git 提交前的所有準備工作。這是一個「編排器」Skill，負責調用其他 Skills。
觸發條件
- 「準備 commit」「GIT」「gc」
- 「要提交了」「git commit」
- 「推送」「push」
法規依據
- 憲法：CONSTITUTION.md 第三章
- 子法：.github/bylaws/git-workflow.md
🔧 操作步驟（編排流程）
Step 1: 收集變更資訊
git status --short
git diff --name-only --cached
使用工具：
get_changed_files() # 取得變更清單
Step 2: 執行 memory-updater（必要）
呼叫條件：永遠執行
調用 memory-updater skill：
- 更新 activeContext.md（當前焦點）
- 更新 progress.md（移動 Done/Doing）
Step 3: 執行 readme-updater（條件）
呼叫條件：
- 新增功能（src/ 有新檔案）
- 依賴變更（pyproject.toml/package.json 變更）
- API 變更
若需要，調用 readme-updater skill
Step 4: 執行 changelog-updater（條件）
呼叫條件：
- 有功能性變更（非純文檔）
- 有 bug 修復
- 有安全性修補
若需要，調用 changelog-updater skill
Step 5: 執行 roadmap-updater（條件）
呼叫條件：
- 完成了 ROADMAP 中列出的功能
若需要，調用 roadmap-updater skill
Step 6: 架構文檔檢查（條件）
呼叫條件：
- 有結構性變更（新增 domain/application 層）
若需要，更新 memory-bank/architect.md
Step 7: 生成 Commit Message
依據 Conventional Commits 格式：
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
類型對照：
| 變更內容 | type |
|---|---|
| 新功能 | feat |
| Bug 修復 | fix |
| 文檔 | docs |
| 重構 | refactor |
| 測試 | test |
| 建構/CI | chore |
Step 8: 執行 Git 命令
# 檢查狀態
git status
# Stage 變更
git add .
# 提交
git commit -m "feat(auth): 新增用戶認證模組"
# 推送（如果用戶確認）
git push origin main
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.
- 2d ago First seen · 246 lines · 0 tokens per session scan A df55882ce3bf
git-precommit is a skill published in the GitHub repository u9401066/rootcause-mcp (0 stars, last pushed 15d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,633 tokens. A static security scan graded it A with 0 findings. It is 100% identical to git-precommit, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
setup-husky-dotnet
Use when configuring Git hooks in .NET projects before team commits occur, to enforce commit message standards and code formatting automatically.
git-commit
ワーキングディレクトリの変更をConventional Commitsに従ってコミットするスキル。 意味のある変更単位ごとにステージングし、英語でコミットメッセージを作成する。 co-authorやエージェント名をコミットメッセージに含めない。 ユーザーが「コミットして」「変更をコミット」「git commit」「commitして」 「この変更をコミット」「コミットメッセージを書いて」「コミットお願い」 などコミット関連のリクエストをした場合に必ず使用すること。 pushは含まない（コミットのみ）。.
conventional-commits
Write clear, conventional git commit messages — type(scope): summary, imperative mood, a body that explains the why.
ci
Create high-quality Git commits for all pending changes.
git-precommit
Orchestrate pre-commit workflow including Memory Bank sync, README/CHANGELOG/ROADMAP updates. Triggers: GIT, gc, push, commit, 提交, 準備 commit, 要提交了, git commit, pre-commit, 推送, stage, 暫存, checkin, 簽入, submit, save, 準備發布, ready to commit, 要推了.
git-doc-updater
Auto-check and update key documentation before Git commits to keep docs in sync with code. Triggers: docs, 文檔, 更新文檔, sync docs, release, 發布, documentation, 同步文件, 文件檢查, doc check, 發布前, before release, 準備發布.