Retrofits all 39 skills to ADR-0020's description/body context contract, then fixes what six rounds of independent review found in that retrofit — including four ways the hot gate itself failed open. Closes #99, #107, #108, #110, #111, #114, #115, #120. ## The retrofit (waves 1-5) | | Start | Now | |---|---|---| | Description FAILs (>400 chars) | 26 | **0** | | Body FAILs (>900 words, body-only) | 9 | **0** | | Dangling routing targets | 2 | **0** | | `Kyberforge.CompositionNote` | 10 | **0** | | Preload tax | 21,005 chars | **~10,500** | Under the 12,000-char success criterion. Per-wave detail is on #99. ## The review fixes **The gate failed open four ways, three of them found after the retrofit shipped.** An unrecognised follower token made a dangling target vanish. A skill directory with no `SKILL.md` resolved as a valid target, so a commit could be green locally and red in a fresh clone — three existing fixtures were relying on that, one of which made the install-leak A/B pass vacuously. Then the free-standing `/name` sweep turned out to be gated on the sentence carrying a boundary marker, so route notation in any other sentence was invisible — not an ERROR, not a SUGGESTION, not an INFO — which left the documented "`/name` always blocks" promise false from a second direction. All four fixed and pinned. **Two checks were silently not running.** `validate-provenance.sh` checks 7-8 were dead across nine skills. Waking them exposed a deeper problem: they assume `Research doc:` names a source index, but 30 of 121 entries point at topic content documents, so every new check-7 INFO was a false positive and check 8 was saved from a false-FAIL flood only by an *unannounced* skip. Checks 7/8 are now scoped to source indexes and every skip announces itself (#121). **The retrofit's own anti-goal, four times.** ADR-0020 warns that a blunt gate gets satisfied by deleting content rather than relocating it. `diagnose` and `skill-audit` relocated prose and then read it unconditionally; `prototype` and `vale-config` deleted rules outright that survived nowhere. All four addressed. ## Verification - `bash tests/run-tests.sh --strict` — 24 suites, 0 skipped, 0 failed - `bash tests/run-bats.sh` — 325 tests, 0 failures - `pre-commit run --all-files` — 17/17 - `pre-commit run --hook-stage pre-push --all-files` — 16/16, with `apm marketplace check` and `apm pack --check-clean` run against the remote, not skipped - `scripts/skill-size-check.sh` over all 39 skills — rc 0, 0 ERROR/FAIL, SUGGESTION-only - Preload tax measured at **10,498 chars**, max description 390 — both inside budget - Every new test proven non-vacuous by a deliberate mutation of the behaviour it covers **Per-commit sync, stated accurately:** the ten commits from the latest review round each pass `check-plugin-content-sync` in isolation, verified by checking each out in a detached worktree with a clean between. The earlier gitea window (`dfacf05..bedbd1d`, nine commits) does **not** — its mirror was regenerated in one batch at `bbc7300`. An earlier revision of this description claimed the property held for every commit; it does not, and a bisect through that window lands on a red commit. **Squash-merge** to collapse it, or accept that this range is not bisectable. ## Version bump Six plugins and the catalog take a **patch**, not a minor. The branch is **89 commits — 40 `fix` / 30 `refactor` / 12 `docs` / 5 `chore` / 2 `test` — zero `feat`, zero `!`, zero `BREAKING CHANGE`** — and adds no skill, agent, command or hook. (Two earlier revisions of this section cited a stale histogram, most recently 78 commits; the figures above are measured at HEAD.) Both rules this repo ships (`forge/references/version-bump.md`, landing in this PR, and `git-commits/references/conventional-commits-spec.md`) make that a patch, and the catalog set is unchanged at 7 entries. Not settled by that: four published files were removed from the installed tree, three moved, and `caveman` gained `disable-model-invocation`, retiring its old triggers. Under a strict reading those are major-class and currently ship under `refactor:` with no marker. Whether the deployed skill surface is a public contract is written down nowhere — worth deciding, but it outlives this PR. ## Deliberately not in scope #112 (cherry-pick ownership, now resolved in favour of `git-commits`), #113 (`rtk git` normalisation), #116 (research fan-out), #101 (audit-skill merge), #122 (non-spec skill-root files), #123 (no PRD producer) stay open. #117 is the one worth reading: the contract's remedy is to move prose into `references/`, which is exactly where neither the size gate nor Vale looks — and the blind spot is wider than #117 currently records, since there is no root `.vale.ini` at all, so every ADR, `CONTEXT.md` and `README.md` is unlinted too. That blind spot let this branch carry two `level: error` `Kyberforge.SentenceOpenerThereIs` violations into `references/` files it created — `provider-adapter-author/references/provider-matrix.md:31` and `agent-audit/references/finding-criteria.md:95`. Both are reworded in `afadaae`, confirmed by routing each file through the audit's own `vale-wrap.sh` (1 error each before, 0 after). Five further occurrences sit in `references/` files already on `main`; those are the pre-existing corpus and stay with #117, which is the real fix. Also unfixed and not this PR's: `apm install` appends a duplicate `SessionStart` entry to `.claude/settings.json`, so a fresh clone cannot get pre-push green without an edit AGENTS.md warns against. Reproduces identically on `main`. Co-authored-by: Defame1297 <gitea@rkdr.net> Reviewed-on: https://git.dev.rkdr.net/Defame1297/holocron/pulls/129 Co-authored-by: Claude Code AI - Gitea MCP <claude@noreply.git.dev.rkdr.net> Co-committed-by: Claude Code AI - Gitea MCP <claude@noreply.git.dev.rkdr.net>
7.6 KiB
topic, source_keys
| topic | source_keys | ||
|---|---|---|---|
| git-log-format |
|
Named Format Presets (--format / --pretty)
| Name | Output |
|---|---|
oneline |
<hash> <title> |
short |
hash, author, title |
medium |
hash, author, date, full message (default) |
full |
adds committer |
fuller |
separate author/committer dates |
reference |
<abbrev> (<title>, <date>) — for use in commit messages |
email |
RFC 2822 email format |
raw |
full object as stored in the object database |
format:<str> |
custom template with placeholders |
Custom Format Placeholders
Commit identity:
| Placeholder | Meaning |
|---|---|
%H |
full commit hash |
%h |
abbreviated commit hash |
%T |
tree hash |
%t |
abbreviated tree hash |
%P |
full parent hashes |
%p |
abbreviated parent hashes |
Author:
| Placeholder | Meaning |
|---|---|
%an |
author name |
%aN |
author name (mailmap-resolved) |
%ae |
author email |
%aE |
author email (mailmap-resolved) |
%ad |
author date (respects --date=) |
%ar |
author date, relative |
%at |
author date, UNIX timestamp |
%ai |
author date, ISO 8601-like |
%aI |
author date, strict ISO 8601 |
%as |
author date, short (YYYY-MM-DD) |
Committer:
| Placeholder | Meaning |
|---|---|
%cn |
committer name |
%ce |
committer email |
%cd |
committer date (respects --date=) |
%cr |
committer date, relative |
%ct |
committer date, UNIX timestamp |
%ci |
committer date, ISO 8601-like |
%cs |
committer date, short |
Message:
| Placeholder | Meaning |
|---|---|
%s |
subject (first line) |
%f |
sanitized subject (filename-safe) |
%b |
body (everything after blank line following subject) |
%B |
raw body (subject + body) |
%N |
commit notes |
Refs and decorations:
| Placeholder | Meaning |
|---|---|
%d |
ref names (like --decorate) |
%D |
ref names without surrounding parentheses |
%S |
ref name by which commit was reached (requires --source) |
%(decorate[:opts]) |
custom decorated refs; options: prefix=, suffix=, separator=, pointer=, tag= |
%(describe[:opts]) |
like git describe; options: tags=, abbrev=, match=, exclude= |
GPG signature:
| Placeholder | Meaning |
|---|---|
%G? |
status: G=good, B=bad, U=unknown, X=expired, R=revoked, N=no signature |
%GS |
signer name |
%GK |
signing key ID |
Trailers:
%(trailers[:key=<k>][,only][,separator=<s>][,unfold][,keyonly][,valueonly])
Formatting / color:
| Placeholder | Meaning |
|---|---|
%n |
newline |
%% |
literal % |
%Cred / %Cgreen / %Cblue / %Creset |
terminal colors |
%C(<spec>) |
color per git-config spec |
%<(<n>[,trunc]) |
right-pad field to width n |
%>(<n>) |
left-pad to width |
Reflog (requires -g / --walk-reflogs):
| Placeholder | Meaning |
|---|---|
%gD |
reflog selector (e.g. refs/stash@{1}) |
%gd |
shortened reflog selector |
%gs |
reflog subject |
Pickaxe Search: -S and -G
-S<string> — finds commits where the count of <string> changed (i.e. the string was added or removed net). Does not match commits where the string merely appears in a diff hunk without a count change.
git log -S"my_function"
git log -S"my_function" --pickaxe-regex # treat as POSIX ERE
git log -S"my_function" --pickaxe-all # show all files in matching changesets
-G<regex> — finds commits where any added or removed line in the patch matches <regex>. Broader than -S: matches whenever the pattern appears in diff text regardless of count.
git log -G"frotz\(nitfol"
Critical distinction: given a diff that removes one occurrence of foo and adds one occurrence of foo (net change = 0):
-S"foo"— does not match (count unchanged)-G"foo"— matches (pattern appears in patch text)
Binary files are searched by -S; ignored by -G unless --text is supplied.
--diff-filter (full table)
Selects commits (in git log) or files (in git diff) by change type:
| Letter | Meaning |
|---|---|
A |
Added |
C |
Copied |
D |
Deleted |
M |
Modified |
R |
Renamed |
T |
Type changed (regular file ↔ symlink ↔ submodule) |
U |
Unmerged (conflict) |
X |
Unknown (indicates a git bug) |
B |
Pairing broken |
Lowercase letters exclude that type:
git log --diff-filter=ad # exclude added and deleted files
git log --diff-filter=M # only show commits with modified files
C and R only appear when copy/rename detection is enabled (-C, -M flags or diff.renames config).
-L — Line Range History (full syntax)
Traces the evolution of a specific range of lines or a named function through commits. Implies --patch.
git log -L 10,20:file.txt
git log -L /start_pattern/,/end_pattern/:file.txt
git log -L :myfunction:src/app.c
git log -L /init/,+15:config.py # 15 lines after first match of /init/
Range formats:
| Format | Meaning |
|---|---|
<n> |
Absolute line number (1-based) |
/<regex>/ |
First line matching regex from previous range end |
^/<regex>/ |
First line matching regex from file start |
+<n> / -<n> |
Offset relative to <start> (end position only) |
Limitations: incompatible with --raw, --numstat, --shortstat, --name-only, --name-status, --check. Cannot use pathspec limiters alongside -L.
Graph and Ancestry Filters
git log --first-parent # at merges, follow only first parent (mainline evolution)
git log --merges # only merge commits (≥2 parents); equivalent to --min-parents=2
git log --no-merges # only non-merge commits; equivalent to --max-parents=1
git log --ancestry-path D..M # only commits actually on the path from D to M
git log --min-parents=<n> # include only commits with ≥ n parents
git log --max-parents=<n> # include only commits with ≤ n parents
--ancestry-path is significant: without it, D..M includes all commits reachable from M but not D — including side branches that merged into the path. With it, only commits directly between D and M are shown.
git diff — Output Control
--stat
git diff --stat # diffstat: file names + ± bar
git diff --stat=<width>,<name-width>,<count>
git diff --compact-summary # alongside --stat: shows new/gone, +x/-x (executable), +l (symlink)
git diff --numstat # machine-readable: <added>\t<deleted>\t<path>; - for binary
--name-only / --name-status
git diff --name-only # only filenames, one per line
git diff --name-status # status letter + filename per line
--name-status uses the same status letters as --diff-filter.
--word-diff
git diff --word-diff # inline word-level diff with [-removed-] {+added+} markers
git diff --word-diff=color # color only, no markers
git diff --word-diff=porcelain # machine-readable: +/- prefixed lines, ~ for newlines
git diff --word-diff-regex=<re> # define what counts as a "word"
Whitespace Flags
| Flag | Effect |
|---|---|
-b / --ignore-space-change |
Treat any run of whitespace as equivalent; ignore trailing whitespace |
-w / --ignore-all-space |
Ignore all whitespace completely |
--ignore-space-at-eol |
Ignore whitespace at end-of-line only |
--ignore-blank-lines |
Ignore changes consisting entirely of blank lines |
-I<regex> / --ignore-matching-lines=<re> |
Ignore changes where all changed lines match regex |