A commit-and-push workflow that reviews code changes, updates the project’s documentation and shared context, prepares a commit message, and asks for approval before pushing.

Use it when saving work, committing changes, pushing a fix, or shipping a feature that may require updates to project maps and agent instructions.

It keeps the project’s notes about services, contracts, decisions, and known bugs aligned with the code. It also helps prevent incomplete context updates, secrets, or unwanted changes from being committed.

commit-sync — Skill for Claude Code by OneDro1d/dark-factory

Install

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.

Any agent

npx skills add OneDro1d/dark-factory --skill commit-sync

Clone the repo

git clone --depth 1 https://github.com/OneDro1d/dark-factory

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/onedro1d/dark-factory/commit-sync/github.svg)](https://agentmods.dev/skills/onedro1d/dark-factory/commit-sync)

Your own site

<a href="https://agentmods.dev/skills/onedro1d/dark-factory/commit-sync"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/commit-sync/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/onedro1d/dark-factory/commit-sync"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/commit-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,023 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00072	$0.01023
Opus 5.5	$0.00029	$0.00409
Sonnet 5.5	$0.00014	$0.00205
Haiku 4.5	$0.00007	$0.00102

Measured 1mo ago against content hash 8fa9eebde25a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

commit-sync 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.

skills/df-context-store/substrate-template/dotclaude/skills/commit-sync/SKILL.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

commit-sync

Goal: never let code and the knowledge layer drift apart, and never push junk or secrets. One procedure: sync → message → confirm → commit → push.

Step 1 — Review what changed

git status --porcelain
git diff --stat
git diff           # actually read it

Identify which services/contracts/agents/skills the change touches.

Step 2 — Sync the knowledge layer (the "update skills and agents" part)

The pre-commit staleness gate (.claude/hooks/pre-commit) enforces the structural floor automatically — it will block the commit if a contract/ schema/service or an agent/skill changed without its map/README staged. This step is how you satisfy that gate, plus the semantic part it can't check (findings/ decisions). Don't rely on --no-verify to skip it.

Apply the context-management skill (knowledge-keeper discipline). For this diff:

Contract/routing-key/table/object-store-key changed → update the shared-models index CLAUDE.md + the service CLAUDE.md + .claude/context/SERVICE-MAP.md + .claude/context/DATA-FLOW.md (nodes/authority/rules if the data shape or ownership moved).
A bug fixed / root cause confirmed → update its F-### in .claude/context/FINDINGS.md (status OPEN→FIXED, add the fixing commit).
A design decision made → add a D-### to .claude/context/DECISIONS.md.
An agent or skill added/removed/renamed → update .claude/agents/README.md (routing table) so it stays the source of truth.
A CLAUDE.md claim the diff makes stale → fix it, cite the code. Only touch what this change actually affects. Cite sources; no guessing.

Step 3 — Safety gate (block on any hit)

git diff --cached -U0 | grep -nEi 'api[_-]?key|secret|password|token|sk-ant|BEGIN .*PRIVATE KEY|bearer ' || echo "no obvious secrets"

Also confirm no PII in fixtures/data. If anything trips, STOP and report — do not commit.

Step 4 — Handle the gitignored knowledge files

If .claude/** and new CLAUDE.md files are gitignored in this repo, and the user wants them shared, force-add explicitly and say so:

git add -f .claude/agents .claude/skills .claude/context <service>/CLAUDE.md

Otherwise leave them local. Never silently change .gitignore — flag it and let the user decide.

Read the full file on GitHub · 80 lines

Changes

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 First seen · 80 lines · 72 tokens per session scan A 8fa9eebde25a

Subscribe to this mod's changes

commit-sync is a skill published in the GitHub repository OneDro1d/dark-factory (4 stars, last pushed 6d ago), licensed Apache-2.0. It adds 72 tokens to every session and 1,023 once invoked, about $0.0003 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-09-01.

Claude Code Commits Git and workflow Releases agent-skills mcp

github-automation

GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.

ruvnet/ruflo · 61 tokens

commit-sync

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

commit-sync

Step 1 — Review what changed

Step 2 — Sync the knowledge layer (the "update skills and agents" part)

Step 3 — Safety gate (block on any hit)

Step 4 — Handle the gitignored knowledge files

What this file has done since we first saw it

Other skills, from other repositories

github-automation

changelog

comet-safe-delivery

git-workflow

git-push

close-task-commit-push-pr