feat: adopt the shared docs lookup across fetching skills and agents
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 64/100
- Tipo di issue
- Refactoring
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- bash, shell
- Ambito
- documentation, tooling
Direzione di ricerca
Start by reading the shared lookup delivered in #6348: lib/fetch-docs.sh, lib/docs-cache.sh, and the /discovery:read-docs skill, plus scripts/sync-shared-copies.sh. Build the inventory.txt from the caller paths listed in the issue, then update each to invoke the lookup (or add the one-line WebFetch pointer for discovery-only callers), syncing the scripts into discipline, knowledge, plugin-quality, instruction-placement and harness-memory. Done means the grep -L command over inventory.txt prints 0 and scripts/sync-shared-copies.sh --check, scripts/check-changelog-parity.sh --check, and the tests for changelog-status and check-doc-citations all exit 0.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
No related issue: follow-up to #6020 (Phase 10 of the docs-cache plan); part of #6020.
Summary
#6020 asks to replace copied upstream docs content with pointers plus a cached lookup layer. #6348 (merged) delivered the shared docs cache, the fetcher (lib/fetch-docs.sh, lib/docs-cache.sh) and /discovery:read-docs. No existing skill or agent uses it yet. This issue adopts the lookup in every skill and agent that fetches upstream documentation.
Fix
Every caller below goes through the lookup (/discovery:read-docs, or lib/fetch-docs.sh and lib/docs-cache.sh from scripts). A caller that only discovers pages (finds candidate URLs, never relies on page content) keeps WebFetch and gains a one-line pointer to the rungs in the upstream-drift convention.
Each plugin that newly carries the lookup gets the synced scripts and the procedure text, plus a version bump and a CHANGELOG line (a changelog fragment for plugins listed in scripts/fragment-plugins.txt).
Freshness per caller:
--max-age 0(fresh bytes required):/harness-config:audit(audit-engine.sh,check-doc-citations.sh,check-effort-pins.sh; it runs after a Claude Code update),/harness-ops:changelog(changelog-status.sh; its purpose is the newest release), and/knowledge:docpage-digestabsence-establishing reads (the Anthropic docs profile binds absence to a fresh raw fetch with a recorded length). A failed forced fetch returnsunread, never stale bytes.- Default TTL with the age shown: all other callers. The read reports
retrieved(bytes first fetched) andvalidated(last confirmed current); age counts fromvalidated.
Callers named in the plan:
- discovery:
research(context/discipline.mdlines about ad-hoc curl and WebFetch,SKILL.md),research-deep(SKILL.md),researcheragent - discipline:
recheck-against-upstream,recheck-against-upstream-deep,do-your-research,sweep-all(reference/batched-pass.md) - harness-config:
audit(SKILL.md,scripts/audit-engine.sh,scripts/check-doc-citations.sh;--cache --max-age 0) - harness-ops:
changelog(scripts/changelog-status.sh,context/read-actions.md),inventory,audit-native-overlap,known-issues(context/action-status.md) - plugin-quality:
auditoragent - instruction-placement:
migrate(SKILL.md,reference/sources.md) - harness-memory:
audit(context/update.md) - knowledge:
docpage-digest(context/anthropic-docs-profile.md),map-corpus(discovery/link-map-format.md)
Plugins that need the synced scripts added: discipline, knowledge, plugin-quality, instruction-placement, harness-memory.
Verification
- A written inventory file lists every path above, one per line.
grep -L -F -e '<exact pointer line>' -e 'docs-cache.sh' -e 'fetch-docs.sh' $(cat inventory.txt) | wc -lprints 0, where the pointer line is the fixed one-line WebFetch pointer and the other two patterns match a lookup invocation. A bare/discovery:match does not count, since every discovery skill already contains it. scripts/sync-shared-copies.sh --checkexits 0.scripts/check-changelog-parity.sh --checkexits 0.- Per-caller tests for the
--max-age 0scripts (changelog-status,check-doc-citations) still pass.
Related
- #6020 (umbrella)
- #6348 (shared docs cache, fetcher,
/discovery:read-docs) - Sibling follow-ups: the copied-content sweep (Phase 11) is filed separately.
- Lingua principale
- Shell
- Stelle
- 22
- Fork
- 2
- Merge medio
- 5h 15m
- PR unite (30g)
- 833
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di melodic-software/claude-code-plugins
-
good first issue needs-triage priority: medium
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
melodic-software/claude-code-plugins#6631 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
melodic-software/claude-code-plugins#6547 ·
I maintainer di solito rispondono entro 1 giorno
-
needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
melodic-software/claude-code-plugins#6535 ·
I maintainer di solito rispondono entro 1 giorno
-
test_comment_census.py: SccArgv flag-shaped-filename test errors on Windows (#!/bin/sh scc shim)Apertagood first issue needs-triage priority: low
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
melodic-software/claude-code-plugins#6532 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
good first issue needs-triage priority: low
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
melodic-software/claude-code-plugins#6390 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di melodic-software/claude-code-plugins
Issue simili
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
influxdata/openapi#660 ·
-
documentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
I maintainer di solito rispondono entro 3 giorni
-
`check_java_version()` fails when Java path contains spaces (Windows / Git Bash, `C:\Program Files`)Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
egoist/mygo#175 · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
I maintainer di solito rispondono entro 1 giorno