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/backtocimacoppi/praxis/commit-changesnpx skills add BackToCimaCoppi/Praxis --skill commit-changesgit clone --depth 1 https://github.com/BackToCimaCoppi/PraxisWhat 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.00100 | $0.00993 |
| Opus 5 | $0.00050 | $0.00496 |
| Sonnet 5 | $0.00020 | $0.00199 |
| Haiku 4.5 | $0.00010 | $0.00099 |
Grade A, and why
commit-changes 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 yesterday.
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
Commit Changes
用户明确要求提交、推送或说"帮我提交"时使用。本 skill 是用户级通用引擎：只固定流程与红线；提交规范原文、门禁脚本、额外前缀规则由项目注入，本 skill 不硬编码任何项目值。
项目注入（挂载点）
| 槽位 | 来源（按顺序探测，先命中先用） | 缺省 |
|---|---|---|
| 提交规范原文 | 项目指令文件（CLAUDE.md / AGENTS.md）的「提交规范」节 → CONTRIBUTING.md |
本 skill「Rules」的默认格式 |
| 提交前门禁命令 | 项目补丁 skill 显式声明的命令 → .claude/hooks/pre-handoff-check.sh → .claude/hooks/pre-commit-check.sh |
无门禁，跳过 Step 0 |
| 额外首行规则 | 提交规范里声明的特殊前缀（如跨域提交标记、任务编号） | 无 |
Required reads
- 上表命中的提交规范原文——每次都读，不凭记忆写格式。
Rules
- 提交信息用简体中文，格式
<类型>: <简要描述>；项目提交规范另有规定时以项目为准 - 提交前必须读 diff
- 未经用户明确要求，不 amend、不 force-push、不 push
- 不提交自己不理解、与本次任务无关的改动
- 永远不用
git add -A/git add .
Default flow
Step 0 — 门禁（项目有门禁脚本时必跑，不可跳过）
# 按挂载点顺序探测；命中哪条跑哪条，全部不存在则跳过本步
bash .claude/hooks/pre-handoff-check.sh
- 退出码非 0 → 立即停止，告知用户失败项，等修复后再触发本 skill
[WARN]输出 → 记录警告，在 Report back 中提及，不阻断流程
Step 1 — 确认变更文件清单
git status --short
读取输出，理解当前工作区状态（哪些是 tracked 修改、哪些是 untracked 新文件）。
Step 2 — 阅读 diff，理解改动性质
git diff
git diff --cached
判断：改动主题（功能/修复/文档/重构/规范/配置）、涉及模块、是否含无关改动需拆分。
Step 3 — 拟定 stage 清单并等待确认
[!CAUTION] 禁止
git add -A或git add .。必须逐文件或逐目录精确 stage。
列出拟 stage 的文件清单（git add <具体路径> 形式），明确告知用户并等待确认，用户确认后再执行 stage。
Step 4 — 拟写 commit message
默认格式：<类型>: <简要描述>，类型限：修复 / 功能 / 重构 / 规范 / 文档 / 配置。
项目提交规范声明了额外首行规则时优先遵守（例：一次提交改动多个业务域目录时，首行用项目规定的跨域标记并说明原因）。
Step 5 — 执行提交
git commit -m "<commit message>"
Step 6 — 推送（仅在用户明确要求时执行）
用户未说"push"或"推送"时，不自动推送。
Report back
用中文总结：
- staged 了哪些文件（列出完整路径）
- commit message 是什么
- 是否已 push
- 若门禁脚本有
[WARN]输出，说明具体警告内容 - 若接口面有变更但未更新测试脚本，说明原因
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 91 lines · 100 tokens per session scan A 1c1758ecaa44
commit-changes is a skill published in the GitHub repository BackToCimaCoppi/Praxis (4 stars, last pushed 7d ago), licensed Apache-2.0. It adds 100 tokens to every session and 993 once invoked, about $0.0005 per session on Opus 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
triz-synergy
Разрешает противоречия в разработке: формулирует пару взаимоисключающих требований к одному объекту, ищет уже существующий ресурс в коде и в структуре данных, разделяет по структуре/времени/условию/отношению и проверяет решение различающим опытом. On-demand only — вызывать явно, когда виден признак противоречия. Use…
code-writing
Universal quality coding process: plan, TDD, reviews. Use whenever code needs to be written — ad-hoc or as part of a task. Use when: "напиши код", "закодь", "реализуй", "write code", "implement" For planning tasks → tech-spec-planning skill. For specs → user-spec-planning skill.
feature-execution
Orchestrate feature delivery as team lead: spawn agents by wave, manage review cycles (max 3 rounds), commit per wave. Use when: "выполни фичу", "do feature", "execute feature", "запусти фичу", "выполни все задачи", "execute all tasks".
task-decomposition
Decompose approved tech-spec into atomic task files with parallel creation and validation. Use when: "разбей на задачи", "декомпозиция", "decompose tech-spec", "создай задачи из техспека", "/decompose-tech-spec".
tech-spec-planning
Creates tech-spec.md with architecture, decisions, testing strategy, and implementation plan. Use when: "сделай техспек", "составь техспек", "техническая спецификация", "tech spec", "создай тз", "составь тз", "new-tech-spec", "/new-tech-spec" Requires existing user-spec.md as input (create with user-spec-planning…
methodology
AI-First development methodology: spec-driven pipeline, project structure, skills/agents ecosystem, quality gates. Use when: "изучи методологию", "изучи глобальную папку", "как работает методология", "what is the pipeline", "покажи пайплайн", "расскажи о процессе разработки", "how does the methodology work", "explain…