Skip to content

docs: define skills_version for runs of this repository - #260

Merged
ultimatile merged 3 commits into
mainfrom
fix/258-skills-version-merge-parent
Oct 13, 2026
Merged

ultimatile merged 3 commits into
mainfrom
fix/258-skills-version-merge-parent

Conversation

@ultimatile

Copy link
Copy Markdown
Owner

Summary

skills/review-telemetry/SKILL.md reads the record field skills_version by running git describe in the checkout the skills are installed from, and has the recording session attest that the result names the state the review gates ran under. For a run on this repository the record is written after the change has landed. When the skills are installed as symlinks into the main checkout, that checkout has by then moved to the commit and the tag the change itself introduced, so the read returns one state past the one intended. CLAUDE.md now defines the field for such a run as the published state the change landed on, which the history fixes.

Closes #258

Changes

  • CLAUDE.md has a section, Telemetry record for a run of this repository, that defines skills_version for a run whose change has landed on main: what git describe --tags --always prints for the parent of the landing commit, recorded as returned. For such a run it replaces both the skill's command and its attestation.
  • The landing commit is the squash-merge commit, read with gh pr view <N> --json mergeCommit --jq .mergeCommit.oid and brought in with git fetch origin, or the commit itself for a direct commit to main.
  • A run whose change has not landed keeps the skill's definition.
  • skills/review-telemetry/SKILL.md is unchanged, so a run on any other repository is recorded as before.

Verification

Notes

  • The value is the state the change landed on, not an attested gate-time state. When another branch lands between a run's gates and its own merge, the value names that later state.
  • skills_version now means one thing for a landed run of this repository and another for every other run, and a record carries no marker of which applied. The record schema stays 4.
  • The rule sits in CLAUDE.md because only this repository's runs are affected and that file is loaded exactly when an agent works here. A session that records one of this repository's runs without that file loaded falls back to the skill's command.

A telemetry record for a change to this repository is written after the
change has landed, by which point the installed checkout has moved to the
commit and tag the change introduced. The skill's own read then returns
one state past the one the run's gates used.

For such a run, define the field as the published state the change landed
on: the describe of the landing commit's parent. A run whose change has
not landed keeps the skill's definition.
The landing steps pull main only as part of tagging, which docs, chore
and style merges skip, and a worktree cannot check out main at all. State
the fetch that makes the squash-merge commit available instead of
pointing at those steps.
gh pr view --json mergeCommit prints an object, which cannot stand in
for the commit in the describe command. Add the jq filter that yields
the SHA.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The documentation consistently resolves the post-merge telemetry ambiguity described in issue #258.

0 open findings

What changed in this PR

Defines deterministic skills_version telemetry for landed changes in this repository.

Changes:

  • Derives the value from the landing commit’s parent.
  • Preserves existing behavior for unlanded changes.
File Description
CLAUDE.md Documents repository-specific telemetry version resolution.

🧠 Review effort: Balanced


💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@ultimatile
ultimatile merged commit 7b6b1ba into main Oct 13, 2026
1 check passed
@ultimatile
ultimatile deleted the fix/258-skills-version-merge-parent branch October 14, 2026 05:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

review-telemetry: skills_version names a state no record-time command can read

2 participants