Repository navigation
docs(config-cascade): one editable list of config locations, cited where docs teach them - #18015
Conversation
docs/contracts/config-cascade/locations.md lists the four layers, the .local naming and the paths outside the contract, pointing at the README sections. Every plugin the old-path docs grep hit carries a generated copy at reference/config-locations.md through the sync gate. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015XWwmfSVU9f2by5nqbM3Ak
Each doc that names a ~/.claude/<name> or .claude/<name>.local.* path for plugin config keeps the fact (its resolver still reads or retires that path) and gains one pointer to the plugin's reference/config-locations.md, or to the canonical page from docs/. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015XWwmfSVU9f2by5nqbM3Ak
…fig belongs The pointer now states that the plugin still reads, or reports as retired, the .claude/ paths beside it, and that new config goes where the config locations page says, so a skill-text resolver keeps reading its current path. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015XWwmfSVU9f2by5nqbM3Ak
…ites them The 39 plugins whose docs cite no reference/config-locations.md lose the generated copy, its registry line and its changelog fragment. The 15 remaining copies are registered as one cross-plugin cluster. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015XWwmfSVU9f2by5nqbM3Ak
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1d043e02a4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
… migrates The pointer sentence told readers to put new config where config locations says, but the resolvers still read their old paths (for example code-metrics' personal override), so following it silently dropped the setting. Say to keep config where the page says it is read until the plugin migrates, then move it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015XWwmfSVU9f2by5nqbM3Ak
Lane run report
Run 44938718351, attempt 1
Failed GitHub API callsNo failed call recorded by the run job's scripts. |
Lane-Activity: pr-refine/fix-docs
Lane run report
Run 44938718351, attempt 1
Failed GitHub API callsNo failed call recorded by the run job's scripts. |
…ware/claude-code-plugins into docs/config-locations
|
claude-security-review reviewed Chunk 1 of 2 (40 files)Security review, chunk 1 of 2 (PR #18015)I found no security issues in this chunk. This lane already reviewed an earlier head ( Scope. I read every hunk of the 40 files in
The copies sit at changelog-fragment paths ( What changed. Every change in this chunk is Markdown about where plugin config lives:
No code, resolver, hook, workflow, manifest or permission changes. Instruction-surface lens. Several changed files are skill bodies (
No protected-class rule is removed, so I didn't need the instruction exception register. Trust controls and manifests. No file in this chunk is a trust control, merge-hold path, workflow, action or plugin manifest. There are no Settled threads and prior findings. Every settled thread is marked Embedded text. I found no directives aimed at the review lane in the diff or the PR context. Spend. None. This chunk changes no lane, schedule, model or billing setting. Chunk 2 of 2 (16 files)Security review: chunk 2 of 2 (PR #18015, head
|
|
claude-review reviewed Chunk 1 of 2 (40 files)Code review, chunk 1 of 2 (blocking only)Blocking only. This lane already reviewed three earlier heads of this PR ( Scope. I read all 40 files in Result: no blocking findings.
Settled threads and prior findings. Every settled thread is marked PR context. There is no closing issue. AC11 comes from the PR body, and nothing in this chunk goes against it. The author says Loosened checks. The prompt had no Plugin manifests. This chunk changes no Spend: none (docs only). Uncovered rules (1)
Verifier dropped 0 of 0 candidates. Chunk 2 of 2 (16 files)Code review, chunk 2 of 2 (blocking only)No blocking findings in this chunk. This lane has already reviewed 3 earlier heads of this PR, so this review reports blocking findings only. What I checked. I read all 16 files in this chunk: the plugin-quality, source-control and testing docs, plus
Settled threads and prior findings. The testing README and PR context. There is no closing issue. AC11 comes from the PR body, and nothing in this chunk goes against it. The author says Loosened checks. The prompt had no Plugin manifests. This chunk changes no Spend: none (docs only). Verifier dropped 0 of 0 candidates. critical-findings: 0 Uncovered rules (1)
|
…ch old-path pointer - bugs, improvement config.md: scope the .claude/**/*.local.* line to the plugin's own override and name <home>/**/*.local.* for the rest - locations.md: keep the tracked .claude/<name> team file as a supported fallback, as the contract does - locations.md: name the canonical file by path so each generated copy reads correctly - discovery README: say the multi-agent plugin reads .claude/multi-agent.local.yaml (#17998), not discovery - run-e2e SKILL.md: name the two old paths and say the control skill path is a Claude Code project skill - testing README, run-e2e SKILL.md: say e2e.md, worst-case.md and the user-global and local layers are still read, then point to config locations Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015XWwmfSVU9f2by5nqbM3Ak
|
The pr-verify verifier failed head What it wrote (32 lines)This pull request leaves the merge queue, and ci-status holds it out while it carries |
…config locations - multi-agent README, reference/config.md, setup SKILL.md: say the plugin still reads ~/.claude/multi-agent.yaml and .claude/multi-agent.local.yaml (#17998), then point to config locations - ai-slop audit SKILL.md: say the plugin still reads $HOME/.claude/ai-slop.json (#18004), then point to config locations - add the generated reference/config-locations.md copy, its shared-copies line and a changelog fragment to both plugins Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015XWwmfSVU9f2by5nqbM3Ak
No related issue: config-location docs cleanup from the external-agents plan; the follow-up resolver issues are listed under Related.
Summary
Problem: docs across the marketplace taught
~/.claude/<name>and.claude/*.localas places for plugin config, which the config-cascade contract does not define. Intent: "I don't want you or future agents to be confused by that"docs/contracts/config-cascade/locations.md, the one editable list of config locations.reference/config-locations.mdcopy, checked by the shared-copies sync gate.Fix
locations.md(layers, homes,.localnaming) that points to the contract README's sections, and says a tracked.claude/<name>team file is still a supported fallback.scripts/shared-copies.txtregisters one copy per citing plugin; no copy is uncited.scripts/cross-plugin-source-registry.txtgets the block the pre-push cross-plugin-source-drift check requires.Verification
bash scripts/sync-shared-copies.sh --checkexits 0 on the branch (1022 copies).Acceptance criteria
docs/contracts/config-cascade/locations.mdis the one editable source of config locations; every plugin that teaches config locations carries a generatedreference/config-locations.mdchecked by the sync gate; no doc in claude-code-plugins teaches~/.claude/<name>or.claude/*.localfor non-Claude config; one issue exists per resolver still reading old paths.Related
Resolver issues (search
gh issue list -R melodic-software/claude-code-plugins --search "config path in:title" --state openreturned no existing match before filing). Each requires a dual-read window, so no setting in an old file is dropped:Not in scope:
~/.claude/ecosystems/<ecosystem>.yaml(plugins/review/agents/ecosystem-specialist.md) and~/.claude/standards/(plugins/review/reference/standards-contract.md) belong to the ecosystem-commands and standards contracts, not the config cascade, so they get no pointer here. The review-digest paths (#18006) appear in no review-plugin doc.Sibling plugin work: external-agents plugin, #17954.
🤖 Generated with Claude Code
https://claude.ai/code/session_015XWwmfSVU9f2by5nqbM3Ak