Borrowing it
Nothing to install: this file belongs to u9401066/HyperHierarchicalRAG. 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/u9401066/HyperHierarchicalRAG/master/.claude/skills/git-doc-updater/SKILL.mdgit clone --depth 1 https://github.com/u9401066/HyperHierarchicalRAGWrote 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/u9401066/hyperhierarchicalrag/git-doc-updater)<a href="https://agentmods.dev/skills/u9401066/hyperhierarchicalrag/git-doc-updater"><img src="https://agentmods.dev/badge/skills/u9401066/hyperhierarchicalrag/git-doc-updater.svg" alt="Measured on agentmods" 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.00000 | $0.00773 |
| Opus 5 | $0.00000 | $0.00387 |
| Sonnet 5 | $0.00000 | $0.00155 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
git-doc-updater 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 6d 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-doc-updater — 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.
What it actually says
name: git-doc-updater description: Auto-check and update key documentation before Git commits to keep docs in sync with code. Triggers: docs, 文檔, 更新文檔, sync docs, release, 發布.
Git 文檔自動更新技能
描述
在執行 Git commit 之前，自動檢查並更新專案的關鍵文檔，確保文檔與程式碼保持同步。
觸發條件
當用戶要求進行以下操作時啟用此技能：
- Git commit
- Git push
- 提交程式碼
- 準備發布
自動更新的文檔
1. README.md
- 更新專案描述（如有變更）
- 更新安裝/使用說明
- 更新功能列表
- 更新依賴項目
2. CHANGELOG.md
- 根據本次變更添加新條目
- 遵循 Keep a Changelog 格式
- 分類為：Added, Changed, Deprecated, Removed, Fixed, Security
- 包含日期和版本號（如適用）
3. ROADMAP.md
- 標記已完成的功能項目
- 更新進行中的項目狀態
- 調整優先順序（如需要）
4. ARCHITECTURE.md (ARCH)
- 更新架構圖和說明（如有結構性變更）
- 更新組件關係
- 更新技術決策記錄
5. Memory Bank 文件
更新 memory-bank/ 目錄下的相關文件：
activeContext.md- 當前工作焦點progress.md- 進度追蹤（Done/Doing/Next）decisionLog.md- 記錄重要決策productContext.md- 專案上下文（如有變更）
執行流程
1. 分析本次程式碼變更內容
2. 識別哪些文檔需要更新
3. 依序更新各文檔
4. 顯示更新摘要供用戶確認
5. 將文檔變更加入 Git staging
更新原則
- 最小變更：只更新與本次提交相關的內容
- 保持一致性：維持現有文檔格式和風格
- 自動摘要：從 commit 內容推斷變更摘要
- 版本控制：CHANGELOG 使用語義化版本
範例輸出
當用戶說「準備 commit」時：
📝 文檔更新檢查：
✅ README.md - 無需更新
✅ CHANGELOG.md - 已添加 v1.2.0 條目
✅ ROADMAP.md - 已標記「用戶認證」為完成
⏭️ ARCHITECTURE.md - 無結構性變更，跳過
✅ memory-bank/progress.md - 已更新進度
準備提交以下文件變更...
自定義選項
用戶可以透過提示指定：
--skip-readme跳過 README 更新--skip-changelog跳過 CHANGELOG 更新--skip-memory跳過 Memory Bank 更新--dry-run只顯示將要更新的內容，不實際修改
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.
- 6d ago First seen · 89 lines · 0 tokens per session scan A 38e925c14ac9
git-doc-updater is a skill published in the GitHub repository u9401066/HyperHierarchicalRAG (2 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 773 tokens. A static security scan graded it A with 0 findings. It is 100% identical to git-doc-updater, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
fp-implement
Phase 3 of the feature-pipeline suite. Use this after /fp-plan has received explicit user approval and printed the M2-plan stop hook — when you need to translate an approved numbered plan into committed, pushed code. Triggers on: "implement the plan", "start coding", "commit the plan", "write the code"…
pr
Push committed changes and create a draft PR on GitHub. Use when you have staged changes ready to push and want to open a draft PR for early feedback or documentation.
regen
Manually trigger artifact regeneration, versioning, and chore commit. Use when you need fine-grained control over when registry artifacts sync (outside the automated sync-artifacts.yml workflow).
contextual-commit
Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.
meta-pre-commit-quality-gate
Run three quality gates (ruff + mypy + pytest) in parallel over the staged diff, then arbitrate a single BLOCK/APPROVE verdict. Use before committing changes locally when you want a comprehensive pre-commit gate beyond per-file linting — exactly the same gate set CI enforces.
commit
Create git commits with good messages. Use when user says "commit", "create commit", or asks to commit changes.