governance-sync
Skill1 starsChanged 2 months agoMITView on GitHub
Use when a session is ending, handover/roadmap may be stale, or the operator runs /governance-sync. Keep {{docs.roadmap_path}} and {{docs.handover_path}} aligned with true VCS state and phase truth. This automates the SD-17 obligation — it does not invent new policy. Default: dry-run. Writes nothing except the local .overseer/last_governance_sync marker when D1/D2 are aligned (GFG carve-out). Governance-doc patches, commits, and realign apply only on explicit non-dry-run; never on {{vcs.git.main_branch}}. After apply/write of living docs, run ok next (or equivalent Read) and include…
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ariaxhan/kernel-claudetheir own version, first seen Jul 29, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ariaxhan/kernel-claude★ 15same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/build-verification-required.mdcCursor rule
- .cursor/rules/check-ok-thinking.mdcCursor rule
- .cursor/rules/governance-sync.mdcCursor rule
- .cursor/rules/l1-checkpoints-consumer-owned.mdcCursor rule
- .cursor/rules/no-docs-only-pr-to-main.mdcCursor rule
- .cursor/rules/orchestrator.mdcCursor rule
- .cursor/rules/print-next-closeout.mdcCursor rule
- .cursor/rules/tier-authority.mdcCursor rule
- .cursor/rules/workspace-authority.mdcCursor rule
- build-verification-reviewSkill
- check-okSkill
- deploy-verification-reviewSkill
- freeze-review-loopSkill
- freeze-reviewSkill
- print-nextSkill
- workspace-statusSkill
- build-verification-reviewSkill
- check-okSkill
- deploy-verification-reviewSkill
- freeze-review-loopSkill
- freeze-reviewSkill
- governance-syncSkill
- knowtationSkill
- print-nextSkill
- workspace-statusSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 3 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
Use when a session is ending, handover/roadmap may be stale, or the operator runs /governance-sync.
- Very specific: line 7
Keep {{docs.roadmap_path}} and {{docs.handover_path}} aligned with true VCS state and phase truth.
- Very specific: line 19
Read VCS status via the kit adapter for {{vcs.regime}} (fail-closed on read errors).
- Very specific: line 24
If NEXT is Thinking → Auto, emit {step}a or {step}b only — not both unless {step}a incomplete.
- Very specific: line 37
After apply/write of living docs, run ok next (or equivalent Read) and include the ## CURRENT NEXT — paste this heading+fence in the …
- Very specific: line 42
When the handover NEXT is land-phase=land-a and D1 is drifted (the merge landed on {{vcs.git.main_branch}}), the plan emits the land-b …
- Very specific: line 52
No merge to {{vcs.git.main_branch}} without Tier 3
- Distinctive: line 53
No staging push without Tier 3
- Distinctive: line 54
No live posture flips
- Distinctive: line 55
No peer-repo writes from this command — workspace relay check is read-only (§MR.8)
- Very specific: line 59
After advancing product_order PRIMARY, refresh each relay: true tip (role=relay or ## PRODUCT RELAY —) and run:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Governance sync skill
Use when a session is ending, handover/roadmap may be stale, or the operator runs /governance-sync.
Purpose
Keep {{docs.roadmap_path}} and {{docs.handover_path}} aligned with true VCS state and phase
truth. This automates the SD-17 obligation — it does not invent new policy.
Read first
{{docs.handover_path}}— current NEXT block{{docs.roadmap_path}}— build status tablepolicy/tiers.yaml,policy/model-labels.yaml.overseer/config.yaml— regime and doc paths
Workflow (docs-first)
- Read VCS status via the kit adapter for
{{vcs.regime}}(fail-closed on read errors). - Compare docs to reality; list drift (phase status, branch/sha, NEXT prompt staleness).
- Update
{{docs.roadmap_path}}first. - Regenerate
{{docs.handover_path}}from updated roadmap + VCS snapshot. - Include
Model:on every NEXT block perpolicy/model-labels.yaml. - If NEXT is Thinking → Auto, emit
{step}aor{step}bonly — not both unless{step}aincomplete.
CLI (when K4/K5 land)
/path/to/overseer-kit/cli/ok governance-sync --dry-run
/path/to/overseer-kit/cli/ok governance-syncDefault: dry-run. Writes nothing except the local .overseer/last_governance_sync
marker when D1/D2 are aligned (GFG carve-out). Governance-doc patches, commits, and
realign apply only on explicit non-dry-run; never on {{vcs.git.main_branch}}.
After apply/write of living docs, run ok next (or equivalent Read) and include the
## CURRENT NEXT — paste this heading+fence in the user-visible close.
Post-merge land closeout (PMHF)
When the handover NEXT is land-phase=land-a and D1 is drifted (the merge landed on
{{vcs.git.main_branch}}), the plan emits the land-b paste for the same slice.
land-b required: ok governance-sync --dry-run then apply; paste land-b; do not re-paste land-a.
Closing commit
Feature branch only. Message pattern: governance: sync handover + roadmap (<date>). Bundle both docs.
Hard stops
- No merge to
{{vcs.git.main_branch}}without Tier 3 - No staging push without Tier 3
- No live posture flips
- No peer-repo writes from this command — workspace relay check is read-only (§MR.8)
Multi-repo (when workspace: configured)
After advancing product_order PRIMARY, refresh each relay: true tip
(role=relay or ## PRODUCT RELAY —) and run:
ok workspace check-nextgovernance-sync footer / JSON key workspace_relay reports
not_configured|ok|stale_relay|ambiguous_primary|missing_member|error. Multi-repo SD-17
is incomplete until check-next exits 0. Single-repo docs↔VCS sync remains required.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

