katopz/katgpt-rs / .agents/skills/doc-sync
doc-sync
VerifiedSynchronize each repo's `.docs/` and `README.md` with recently succeeded plans/issues/benchmarks by diffing git history against the last documented entry. Use after landing a GOAT-passing plan, closing a batch of issues, or quarterly as a doc-hygiene gate. Covers every workspace repo and knows each repo's doc layout + where to record what, including each repo's root BOUNDARY.md contract (drift rows vs issue state).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 57.4 KB |
| tools/link_fix.py | script | 11.6 KB |
| tools/linkcheck_sweep.py | script | 5.4 KB |
| tools/sync_commit.shexecutable | script | 2.5 KB |
tools/sync_commit.sh
View on GitHub#!/bin/sh
# sync_commit.sh — doc-sync's mechanical commit gate.
#
# Makes the standing lesson ("the staged-index check must GATE the commit, not
# precede it") the ONLY commit path for this lane. The #42 incident class: a
# run-log commit on a shared checkout swept 17 files of stale sibling staged
# content (another box's index state left in the shared tree), reverting
# landed work. Prose did not stop it; this does:
#
# 1. REFUSES a non-empty index up front — stale sibling state is adjudicated
# first, never swept (the incident's exact entry condition). Never
# auto-clear: the staged content may be a live sibling's work.
# 2. Stages ONLY the named paths.
# 3. REFUSES if anything is staged beyond the named pathspecs (a sibling
# `git add` landing concurrently between (1) and (3)).
# 4. Commits via the PARTIAL form `git commit -- <paths>` — a temporary
# index built from HEAD + the named paths — so anything staged
# concurrently between (3) and (4) stays in the real index, never the
# commit, and the real index is never disturbed.
#
# Usage: sync_commit.sh <repo-dir> <commit-message> <path>...
# Paths are git pathspecs relative to the repo root (directories allowed).
# Name exactly the paths the run edited — never a directory you did not
# touch.
set -eu
[ "$#" -ge 3 ] || {
echo "usage: sync_commit.sh <repo-dir> <commit-message> <path>..." >&2
exit 2
}
repo="$1"
msg="$2"
shift 2
[ -d "$repo/.git" ] || [ -f "$repo/.git" ] || {
echo "sync_commit: not a git repo: $repo" >&2
exit 2
}
# Gate 1 — the index must start empty.
stale=$(git -C "$repo" diff --cached --name-only)
if [ -n "$stale" ]; then
echo "sync_commit: REFUSED — staged index not empty in $repo (stale sibling state; adjudicate before committing):" >&2
echo "$stale" >&2
exit 1
fi
git -C "$repo" add -- "$@"
# Gate 2 — everything staged must match the named pathspecs.
all_staged=$(git -C "$repo" diff --cached --name-only)
scoped=$(git -C "$repo" diff --cached --name-only -- "$@")
if [ "$all_staged" != "$scoped" ]; then
echo "sync_commit: REFUSED — staged set exceeds the named paths (concurrent sibling staging?):" >&2
echo "--- all staged:" >&2
echo "$all_staged" >&2
echo "--- within named paths:" >&2
echo "$scoped" >&2
exit 1
fi
# Partial commit — temporary index from HEAD + the named paths.
git -C "$repo" commit -m "$msg" -- "$@"
hash=$(git -C "$repo" rev-parse --short HEAD)
echo "sync_commit: $hash — named paths only; real index untouched."
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |