Skip to content

docs: replace restated upstream facts with pointers in fleet, harness-memory, repo-hygiene, rate-limit-guard and 1 more #12696

Description

@kyle-sexton

Refs: #7292

Outcome

28 passages in 13 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: fleet, harness-memory, repo-hygiene, rate-limit-guard, visualization.

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

fleet

harness-memory

  • plugins/harness-memory/skills/audit/SKILL.md:203-207 (r254). Pointer: https://github.com/anthropics/claude-plugins-official/tree/main/plugins/claude-md-management#usage Drop the descriptions of what the plugin's skill and command do; keep 'run this audit first, fix mode stands alone without the plugin', and point at the plugin README.
  • plugins/harness-memory/skills/stateless/SKILL.md:22-26,39 (r255). Pointer: https://code.claude.com/docs/en/memory#storage-location Drop the store path and relocation statement in the intro and Scope table; keep that the skill governs the auto-memory store, and point at the storage section. Same text also at: plugins/harness-memory/skills/stateless/reference/official-guidance.md:76, plugins/harness-memory/skills/stateless/context/status.md:50; a row of its own covers it only if listed.
  • plugins/harness-memory/skills/stateless/SKILL.md:22-24 (r257). Pointer: https://code.claude.com/docs/en/memory#storage-location Drop the default directory and the relocation setting from the intro sentence; keep that the skill governs the auto-memory store, and point at the storage section. Same text also at: plugins/harness-memory/skills/stateless/reference/official-guidance.md:77; a row of its own covers it only if listed.
  • plugins/harness-memory/skills/stateless/SKILL.md:97-98,103-106 (r256). Pointer: https://code.claude.com/docs/en/memory#view-and-edit-with-memory Drop the description of what /memory edits and the gate-basis note; keep that this skill never runs it and the offer-when-resolves routing, and point at the section.
  • plugins/harness-memory/skills/stateless/context/purge.md:28-30 (r259). Pointer: https://code.claude.com/docs/en/settings-reference#automemorydirectory Drop the list of scopes that can set autoMemoryDirectory; keep the decision to resolve it from every present scope before purging, and point at the section. Same text also at: plugins/harness-memory/skills/stateless/SKILL.md:124; a row of its own covers it only if listed.
  • plugins/harness-memory/skills/stateless/context/status.md:38-40 (r260). Pointer: https://code.claude.com/docs/en/memory#enable-or-disable-auto-memory Drop the override semantics and the =1/=0 meanings; keep the decision that the env var is checked first and is authoritative when set, and point at the section. Same text also at: plugins/harness-memory/skills/stateless/SKILL.md:65, plugins/harness-memory/skills/stateless/reference/official-guidance.md:57; a row of its own covers it only if listed.

repo-hygiene

  • plugins/repo-hygiene/skills/clean/SKILL.md:76-78 (r411). Pointer: https://code.claude.com/docs/en/tools-reference#output-limits Drop the description of what the Bash tool returns into context; keep the decision to bound output with a pipe in the command, and point at the section.
  • plugins/repo-hygiene/skills/clean/SKILL.md:81-85 (r409). Pointer: https://code.claude.com/docs/en/skills#how-injected-commands-run Drop the claim about how the harness runs the pre-compute block and the worktree refusal; keep the decision to use separate body Bash calls, pointing at the section.
  • plugins/repo-hygiene/skills/clean/context/git-branch-cleanup.md:49 (r413). Pointer: https://cli.github.com/manual/gh_pr_list#options Drop the statements about gh having no unlimited sentinel and rejecting a zero limit; keep the batched PR map, truncation check and CLEAN_PR_LIST_LIMIT override, pointing at the options.
  • plugins/repo-hygiene/skills/clean/context/git-branch-cleanup.md:76,100 (r414). Pointer: https://git-scm.com/docs/git-cherry#description Drop the explanations of git cherry skipping merges and git branch --merged missing squash merges; keep the row 8b skip and squash-handling decisions, pointing at git-cherry and git-branch --merged docs.
  • plugins/repo-hygiene/skills/clean/reference/cleanup-config.md:58 (r417). Pointer: https://git-scm.com/docs/git-clean#options Drop the claim that git clean traverses reparse points into tracked source; keep the default of excluding node_modules/ from clean, pointing at git-clean options.
  • plugins/repo-hygiene/skills/clean/reference/invocation-forms.md:35-37 (r418). Pointer: https://code.claude.com/docs/en/skills#available-string-substitutions Drop the description of how each token expands when unset or unresolved; keep the rule that reference files carry no substitution tokens, pointing at the substitutions section.

rate-limit-guard

  • plugins/rate-limit-guard/README.md:117-122 (r396). Pointer: https://code.claude.com/docs/en/settings#change-a-setting-for-one-session Drop the claims about --bg first-prompt reporting and what --settings can set; keep the guidance that a lane wanting lines at once supplies its own options, with a pointer.
  • plugins/rate-limit-guard/README.md:161-163 (r398). Pointer: https://code.claude.com/docs/en/plugins/mods/overview#where-mods-run Drop the claim that mods can start host processes only in the CLI; keep the module's own process-cost statement and the write-nothing-and-log-once fallback, with a pointer.
  • plugins/rate-limit-guard/README.md:242-244 (r399). Pointer: https://code.claude.com/docs/en/plugins/cli-reference#reload-plugins Drop when a plugin becomes active and the /reload-plugins mechanics; keep that nothing needs wiring and that setup check verifies the result, with a pointer.
  • plugins/rate-limit-guard/README.md:325-330 (r400). Pointer: https://code.claude.com/docs/en/plugins/cli-reference#what-an-uninstall-deletes-and-keeps Drop the install --config mechanics and the description of what uninstall deletes; keep the rule never to uninstall to reconfigure, pointing at this section and #plugin-install.
  • plugins/rate-limit-guard/reference/reader-contract.md:27-31 (r402). Pointer: none found; No public page documents ~/.claude.json fields; the PR must search the settings and authentication docs for oauthAccount and, if none, reword to state only the local observation and fallback. Drop the assertion about what upstream promises; keep the key name, the cannot-attribute fallback and the re-verify trigger, citing the dated observation instead of a claim about the docs.

visualization

  • plugins/visualization/skills/visualize/SKILL.md:117-122,247-251 (r469). Pointer: https://code.claude.com/docs/en/plugins/manifest-reference#reference-a-saved-value Drop the description of how Claude Code substitutes configured values and what an unresolved token looks like; keep that unset or auto defers to the next rung, and point at the section.
  • plugins/visualization/skills/visualize/SKILL.md:190-195 (r470). Pointer: https://code.claude.com/docs/en/artifacts#page-constraints (confirm the section) Drop the statement of where mermaid renders natively; keep the decision that local pages stay self-contained with no network-loaded renderer, and point at the artifact page constraints.
  • plugins/visualization/skills/visualize/SKILL.md:263-266 (r471). Pointer: none found; Find the Claude Code docs section that states how terminal output renders markdown and fenced blocks (interactive-mode, fullscreen or terminal-config); none of the fetched headings covers it. Drop the description of what the terminal renders and shows for a mermaid block; keep the decision to emit portable source and prefer a page when the rendered diagram matters. Same text also at: plugins/visualization/skills/visualize/SKILL.md:282; a row of its own covers it only if listed.
  • plugins/visualization/skills/visualize/SKILL.md:291-293 (r472). Pointer: https://code.claude.com/docs/en/artifacts#page-constraints (confirm the section) Drop the stable-family count and the claim about which families render; keep the decision to prefer a family known to render or verify first, pointing at the artifact constraints.
  • plugins/visualization/skills/visualize/SKILL.md:348-350 (r473). Pointer: https://code.claude.com/docs/en/artifacts#draft-a-design-canvas Drop the description of what the ClaudeDesign tool lists, reads and writes; keep that new Design artifacts come from the bundled design skill the person runs, and point at the 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 13 files in five plugins (fleet, harness-memory, repo-hygiene, rate-limit-guard, visualization) restate facts that upstream sources own. Each becomes a pointer to the live upstream section, with an as-of date and a recheck trigger. The local decision stays in the repository's own words. The PR must pass check-stamps.sh --trigger-less on the files it touches, and each touched plugin needs a changelog fragment. Several pointers are marked "confirm the section" or "none found", so the implementer has to fetch and verify them first. I found no likely duplicates among the open issues.

    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. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor

    The triage sweep dispatched intake triage for this issue (attempt 1 of 2).

  5. 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
  6. added
    admission-deferredAdmitted but waiting for WIP room; the hourly work-unblock sweep labels it agent-ready.
    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
  7. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor
    No description provided.
  8. melodic-automation-lanes commented on Nov 3, 2026

    @melodic-automation-lanes
    Contributor

    This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41591279055, the work-resolve-issue run that agent-ready started, before it did any work; that run ended at 2026-11-03T08:44:19Z. work-unblock has now removed and added agent-ready back to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last added agent-ready or a run last reported, work-unblock waits longer before each one, up to 24 hours.

  9. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    and removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 3, 2026
  10. github-actions commented on Nov 3, 2026

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

    @github-actions
    Contributor
    No description provided.
  12. removed
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 3, 2026
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

    priority: lowNice-to-have, cosmetic, or speculative; opportunistic.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