Skip to content

docs: replace restated upstream facts with pointers in evals, source-control #12691

Description

@kyle-sexton

Refs: #7292

Outcome

28 passages in 10 files state a fact an external source owns. Rewrite each as a pointer to the live upstream section, or remove it, so the next upstream change cannot leave a stale copy here. Plugins: evals, source-control.

Done when

  • Every row below is fixed: the restated value is deleted, the local decision stays in this repository's own words, and the pointer goes to the exact upstream section with an as-of date and a recheck trigger, per .claude/rules/skill-bodies-state-current-rules.md. A record beside a restated value does not fix it. A row marked Remove has no local dependency on the fact.
  • The PR passes check-stamps.sh --trigger-less (plugins/attribution/skills/audit/scripts/check-stamps.sh) on the files it touches.
  • Each touched plugin has a changelog fragment.

Rows

evals

source-control

  • plugins/source-control/reference/worktree-root-convention.md:33-36 (r445). Pointer: https://github.com/x-motemen/ghq (confirm the section) Drop the parenthetical about what ghq list enumerates and the dot-hiding claim; keep that the worktree root sits outside every repository and discovery root, and point at the ghq README.
  • plugins/source-control/reference/worktree-root-convention.md:130-134 (r447). Pointer: https://git-scm.com/docs/git-config#conditional-includes Drop the per-client support claims for libgit2, JGit and go-git; keep the decision to use gitdir/i: for identity and hasconfig: for worktreeroot.*, and point at git-config conditional includes.
  • plugins/source-control/reference/worktree-root-convention.md:157-162 (r448). Pointer: https://git-scm.com/docs/git-config#variables (confirm the section) Drop the list of leaking keys, the Good-locally verification claim and the useConfigOnly behavior; keep the rule that identity includes set more than user.email, and point at git-config variables.
  • plugins/source-control/skills/babysit-prs/reference/orchestration.md:50-55 (r451). Pointer: none found; Find the GitHub GraphQL MergeStateStatus enum section; docs.github.com/en/graphql/reference/enums is only an index and did not show it (likely the pull-requests reference page). Drop the claim about what mergeStateStatus integrates; keep that these arms are re-validated by the direct merge gate and could dispatch a worker with nothing to do, and point at the enum.
  • plugins/source-control/skills/babysit-prs/reference/orchestration.md:114-119 (r452). Pointer: none found; Find the GitHub GraphQL MergeStateStatus enum section; docs.github.com/en/graphql/reference/enums is only an index and did not show it. Drop the claim that GitHub recomputes mergeStateStatus asynchronously and flaps; keep the decision that the event fires only on a transition into CLEAN or HAS_HOOKS, and point at the enum.
  • plugins/source-control/skills/babysit-prs/reference/orchestration.md:326-331 (r453). Pointer: https://code.claude.com/docs/en/sub-agents#resume-subagents Drop the statement that a new Agent call always starts a fresh agent; keep the rule to continue a possibly-running worker by message, not redispatch, and point at the section.
  • plugins/source-control/skills/babysit-prs/reference/orchestration.md:609-612 (r454). Pointer: none found; Find the git-merge or git-commit docs section on switching branches mid-merge and on hooks; the fetched git-checkout page does not mention it. Drop the quoted git refusal message and the description of what porcelain commit runs; keep the decision to preserve the merge state with a sequence hooks cannot interrupt, and point at the git docs.
  • plugins/source-control/skills/babysit-prs/reference/orchestration.md:831-834,950-953 (r455). Pointer: https://code.claude.com/docs/en/tools-reference#what-persists-between-commands Drop both explanations of why a one-time cd fails and how cwd drifts; keep the rule to set the worktree explicitly on every command, and point at the section.
  • plugins/source-control/skills/pull-request/reference/watch-handoff.md:10-11 (r456). Pointer: https://code.claude.com/docs/en/claude-code-on-the-web (confirm the section) Drop the claim that a cloud session spends plan limits; keep the rule to read the rate-limit snapshot before recommending or starting a route, and point at the page.
  • plugins/source-control/skills/pull-request/reference/watch-handoff.md:21-24 (r457). Pointer: https://code.claude.com/docs/en/statusline#available-data Drop the list of cases where rate_limits is absent; keep the Unknown branch that says so and points at /usage, and point at the status line data section.
  • plugins/source-control/skills/pull-request/reference/watch-handoff.md:26-28 (r458). Pointer: https://code.claude.com/docs/en/claude-code-on-the-web#auto-fix-pull-requests Drop the statement that /autofix-pr runs in a cloud session with no snapshot; keep that the launch-time check is the only check and a local monitor follows the floor, and point at the section.
  • plugins/source-control/skills/pull-request/reference/watch-handoff.md:92,103-105,109-113 (r460). Pointer: https://code.claude.com/docs/en/claude-code-on-the-web#auto-fix-pull-requests Drop the restated /autofix-pr behavior (finds the PR from the current branch); keep the route-table choice and the prompt text this repository supplies, and point at the section.
  • plugins/source-control/skills/worktree/context/audit.md:107-109 (r461). Pointer: https://code.claude.com/docs/en/plugins/cli-reference#plugin-uninstall Drop the claim about what record removal requires and which scope flags exist; keep the decision that no audit recreates paths and the user runs the remedy, pointing at the uninstall section. Same text also at: plugins/source-control/skills/worktree/fixtures/README.md:189; a row of its own covers it only if listed.
  • plugins/source-control/skills/worktree/fixtures/README.md:251-253 (r462). Pointer: https://jqlang.org/manual/#format-strings-and-escaping Drop the CRLF and tsv-escaping descriptions; keep the rule that consumers must normalize paths before comparing, and point at jq's format-strings section.

Notes

Lines are as of 3bd42cabfe (https://github.com/melodic-software/claude-code-plugins/blob/3bd42cabfe6bdef37a05778d396869af0381bb51); locate each passage by its text if main has moved. Each rNNN is that row's number in the order of #7292's "Findings by plugin". Every row was upheld by three blind judges and survived a refutation pass, run report-only for #12072. Pointers are candidates: fetch each before writing it, and confirm the section still documents the fact.

Parent: #7292

Activity

  1. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 3, 2026
  2. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor

    Proposed work class: work-class: scoped
    Basis: automated intake triage; the lanes App applied this class.

    Size: Medium
    Complexity: Low
    Uncertainty: Knowable
    Flags: none
    Blocked by: none

    Understood: a docs-only cleanup. 28 passages across 10 files in the evals and source-control plugins restate facts that upstream sources own. Each one becomes a pointer to the live upstream section, with an as-of date and a recheck trigger. The local decisions stay in this repository's own words. Each touched plugin gets a changelog fragment, and check-stamps.sh --trigger-less must pass on the touched files.

    Four rows (r451, r452, r454 and a few "confirm the section" rows) have no confirmed pointer yet. Finding those sections is research, not a blocker.

    No duplicate found among open issues. It is a child of #7292.

    Automated triage, applied by the lanes App.

  3. added
    priority: lowNice-to-have, cosmetic, or speculative; opportunistic.
    and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 3, 2026
  4. added
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.
    on Nov 3, 2026
  5. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    and removed
    admission-deferredAdmitted but waiting for WIP room; the hourly work-unblock sweep labels it agent-ready.
    on Nov 3, 2026
  6. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor
    No description provided.
  7. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor
    No description provided.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.priority: lowNice-to-have, cosmetic, or speculative; opportunistic.status: readyTriaged, unblocked, and fully specified; eligible to pick up.work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.

    Type

    Fields

    Work status

    agent-ready

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions