Regenerate plugins/*/skills/ from plugins/*/.apm/ after the previous four commits, via scripts/sync-plugin-content.sh --all. The mirror is generated output (ADR-0017) that check-plugin-content-sync's pre-push hook diffs against .apm/; nothing here is hand-edited. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EeH8SCbcrCAQrtymkNuhKP
1.2 KiB
source_keys
| source_keys | ||
|---|---|---|
|
Creating a .pre-commit-config.yaml
Reached from SKILL.md's Route table when the repo has no config yet. Self-contained — the modify
flow's file is not needed here. SKILL.md's three common gates still apply.
Steps
-
Detect what languages are actually in the repo with a shallow extension scan, rather than inferring them from the project's name or README:
rtk git ls-files | grep -oE '\.[a-z]+$' | sort | uniq -c | sort -rn -
Read
references/hooks-by-language.mdand map the detected extensions to recommended hooks. Take the repo URL,revand args from that file rather than from memory — arevthat does not exist is the most common way a fresh config fails on its first run.For a deliberately minimal starting point instead of a full recommendation set,
pre-commit sample-config > .pre-commit-config.yamlprints a small starter config to build on. -
State the proposed config in full and wait for the user's confirmation.
-
Write
.pre-commit-config.yaml, then runpre-commit validate-config. If it exits non-zero, show the error, fix it in place, and re-validate.