docs: Plugin adoption strategy and website requirements (Phase 4) - #1391
docs: Plugin adoption strategy and website requirements (Phase 4)#1391ashleyshaw wants to merge 2 commits into
Conversation
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe change adds Phase 4 website and plugin adoption documentation, including setup, comparison, testing, and troubleshooting guides. It also adds website implementation requirements and updates workflow-consolidation planning, execution status, and session records. ChangesWebsite and plugin adoption documentation
Workflow consolidation project tracking
Estimated code review effort: 3 (Moderate) | ~25 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 2 | ❌ 3❌ Failed checks (3 warnings)
✅ Passed checks (2 passed)
✨ Finishing Touches 💡 2⚔️ Resolve merge conflicts 💡
🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
✅ Template check passed after update. Thanks for fixing the PR description. |
⏱️ Aging and SLA annotation
Maintained by project-meta-sync workflow. |
Metadata governance
|
github-actions
Bot
added
status:needs-review
🔍 Reviewer Summary for PR #1391CI Status: ✅ Recommendations
|
- WEBSITE-UPDATE-REQUIREMENTS.md: fix relative date to absolute '26 July 2026'; UK English: SEO-optimised, customise, optimisation - plugin-setup-github-copilot.md: replace false secret-exclusion claims with accurate warning not to rely on automatic exclusion; add content-exclusion docs link; UK English: Licence, Customise Shortcuts - plugin-setup-claude-code.md: clarify terminal integration — Claude proposes commands for user approval, not unconditional execution; UK English: behaviour rules - plugin-testing.md: expand prerequisites to separate VS Code v1.94.0+ requirement for Claude Code from Copilot extension requirements Relates to #1297
Created plugin setup guides for Claude Code and GitHub Copilot: - docs/plugin-setup-claude-code.md — Installation, configuration, and usage - docs/plugin-setup-github-copilot.md — Inline suggestions and chat interface - docs/plugin-comparison.md — Feature comparison of 4 AI tools - docs/plugin-adoption-phases.md — Tier-based rollout timeline (Aug–Oct 2026) - docs/plugin-testing.md — Manual testing checklist for verification - docs/vscode-plugin-troubleshooting.md — Comprehensive troubleshooting guide Created website update requirements: - .github/projects/active/repo-restructuring-2026-07-25/WEBSITE-UPDATE-REQUIREMENTS.md * Route onboarding by team tier (maintainers/contributors/consumers) * Render documentation from /docs/ markdown * Create agent/skill reference sections * Integrate cookbook with implementation recipes Phase 4 deliverables complete. Website updates require handoff to web team for github.lightspeedwp.agency deployment before Sept 1, 2026 (Tier 2 rollout). Phase 5 (Rollout & Team Communications) ready to proceed. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- WEBSITE-UPDATE-REQUIREMENTS.md: fix relative date to absolute '26 July 2026'; UK English: SEO-optimised, customise, optimisation - plugin-setup-github-copilot.md: replace false secret-exclusion claims with accurate warning not to rely on automatic exclusion; add content-exclusion docs link; UK English: Licence, Customise Shortcuts - plugin-setup-claude-code.md: clarify terminal integration — Claude proposes commands for user approval, not unconditional execution; UK English: behaviour rules - plugin-testing.md: expand prerequisites to separate VS Code v1.94.0+ requirement for Claude Code from Copilot extension requirements Relates to #1297
a2c1509 to
ae9e923
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 14
🧹 Nitpick comments (2)
.remember/now.md (1)
193-210: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winMove the session-closure statement after the final log entry.
The file declares the session closed at Line 202, then appends further activity at Lines 204-210 without a new session heading. Move the closure text to the end or add a new dated session boundary so the timeline remains unambiguous.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.remember/now.md around lines 193 - 210, Move the “Ready to wrap up?” session-closure statement in the Daily Log Entry to after the final activity entry, 12:53 | test/feat-labeling-test-1, so no later entries appear within a closed session. Preserve the existing log entries and formatting..github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md (1)
146-149: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winRemove workstation-specific paths from reusable instructions.
.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md#L146-L149: replace the hard-coded/Users/ash/...navigation path with a portable repository-root instruction..remember/now.md#L135-L139: replace the hard-coded worktree path with a path obtained fromgit worktree listor a documented placeholder.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md around lines 146 - 149, Remove workstation-specific paths from the “Clone/navigate repo” instructions: in .github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md lines 146-149, use a portable repository-root navigation instruction; in .remember/now.md lines 135-139, replace the hard-coded worktree path with a path obtained from git worktree list or a documented placeholder.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
@.github/projects/active/repo-restructuring-2026-07-25/WEBSITE-UPDATE-REQUIREMENTS.md:
- Around line 46-91: Update the role cards in the “onboarding-routes” section to
use semantic HTML: replace each “card” with an “article”, use an appropriate
heading for each role title, descriptive text for each description, and a
clickable “a” element with the existing destination as its href. Preserve the
feature lists and onboarding content while ensuring each role is
keyboard-accessible.
- Around line 265-275: Define a single canonical URL convention for the
documentation entries in the implementation and appendix sections. Update the
generated-file rules and route specifications to use the same format, and
explicitly require redirects when source paths and canonical URLs differ so
navigation and link validation remain consistent.
In
@.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md:
- Around line 150-151: Update the Phase 3 branch setup sequence to run npm run
validate:branch-name -- --branch refactor/labeling-consolidation-phase-3 before
git checkout -b refactor/labeling-consolidation-phase-3, preserving the existing
branch name.
- Around line 20-22: Synchronize Phase 3.1 status and provenance across all
project records: in
.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md
lines 20-22, mark the prompt historical or update it to the merged state; in
.remember/phase-3.2-execution-continuation.md lines 9-28, remove or clearly
reconcile the conflicting `#1367` and `#1390` references; and in .remember/now.md
lines 100-110, correct the `#1319` reference or identify it as a superseded
attempt.
- Line 20: Correct the Phase 3 scope statement in the continuation prompt to
consistently describe consolidation of three source labeling workflows into one
replacement workflow. Align the introductory “4 … into 2” wording with the
detailed plan and supplied status records, without changing the underlying
workflow responsibilities.
In `@docs/plugin-adoption-phases.md`:
- Around line 220-246: Resolve the conflicting grace-period durations between
the Support Plan’s “Grace Period” entry and the “Grace Period Timeline” section
by selecting one governing duration. Update both the timeline and dependent
support commitments, including the tier-specific duration wording, so all
documentation consistently reflects that duration.
- Around line 439-442: Remove absolute privacy assurances from the FAQ near
“What about privacy and security?” in docs/plugin-adoption-phases.md (lines
439-442), replacing them with qualified, product- and plan-specific
vendor-policy language and a clear warning never to expose secrets. Apply the
same qualification and links to each provider’s current privacy documentation in
docs/plugin-comparison.md (lines 416-418), and remove the “only explicitly ask”
guarantee in docs/vscode-plugin-troubleshooting.md (lines 636-638).
- Around line 35-37: Update the rollout phase participant counts and success
metrics consistently across Tier 1, Tier 2, and the referenced sections so each
denominator uses the same inclusion rule for maintainers. Explicitly include or
exclude maintainers in both the described cohort totals and adoption metrics,
preserving matching numerator/denominator values throughout the document.
In `@docs/plugin-comparison.md`:
- Around line 234-238: Align the Claude Code pricing and entitlement guidance
across docs/plugin-comparison.md:234-238 and
docs/plugin-setup-claude-code.md:29-35. Remove the unsupported “$0/free Claude
Code tier” claim and consistently document either paid Anthropic
API/cloud-provider access or clearly distinguish it from Claude Pro/Max
subscription access; do not imply the free Claude.ai plan grants Claude Code
access.
In `@docs/plugin-setup-github-copilot.md`:
- Around line 60-65: Correct the product name in the authentication instruction
within the setup steps, changing “Authorize Github” to use the official “GitHub”
capitalization while leaving the remaining instructions unchanged.
In `@docs/plugin-testing.md`:
- Around line 470-493: Extend the “Secret Handling” security test in
docs/plugin-testing.md to cover GitHub Copilot as well as Claude Code. Add
Copilot steps that verify configured content exclusions and confirm the mock API
key is absent from both generated suggestions and chat context, while
documenting that exclusions have limitations. Keep the existing Claude Code
checks and pass criteria intact.
- Around line 19-20: Align the Claude Code VS Code prerequisite across
docs/plugin-testing.md, docs/plugin-setup-claude-code.md, and
docs/vscode-plugin-troubleshooting.md at the specified ranges by publishing one
authoritative minimum version, using the existing 1.86+ requirement consistently
in the testing checklist, setup guide, and troubleshooting guidance.
In `@docs/vscode-plugin-troubleshooting.md`:
- Around line 95-99: Remove the “Use API key instead” workaround from the VS
Code Copilot troubleshooting flow, including token generation, scopes, and
GitHub: Enterprise URI instructions. Replace it with the supported GitHub
account/browser sign-in flow and link to the VS Code Copilot setup
documentation.
- Around line 275-283: Update the “If still failing” instructions to warn that
deleting the Claude configuration is destructive and may remove credentials or
useful state. Tell users to back up the directory first and prefer renaming or
removing only targeted files; present recursive deletion as a last resort for
both Mac/Linux and Windows commands.
---
Nitpick comments:
In
@.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md:
- Around line 146-149: Remove workstation-specific paths from the
“Clone/navigate repo” instructions: in
.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md
lines 146-149, use a portable repository-root navigation instruction; in
.remember/now.md lines 135-139, replace the hard-coded worktree path with a path
obtained from git worktree list or a documented placeholder.
In @.remember/now.md:
- Around line 193-210: Move the “Ready to wrap up?” session-closure statement in
the Daily Log Entry to after the final activity entry, 12:53 |
test/feat-labeling-test-1, so no later entries appear within a closed session.
Preserve the existing log entries and formatting.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository YAML (base), Organization UI (inherited)
Review profile: CHILL
Plan: Pro Plus
Run ID: 2270119c-00aa-413c-912d-10be9f6f942b
📒 Files selected for processing (10)
.github/projects/active/repo-restructuring-2026-07-25/WEBSITE-UPDATE-REQUIREMENTS.md.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md.remember/now.md.remember/phase-3.2-execution-continuation.mddocs/plugin-adoption-phases.mddocs/plugin-comparison.mddocs/plugin-setup-claude-code.mddocs/plugin-setup-github-copilot.mddocs/plugin-testing.mddocs/vscode-plugin-troubleshooting.md
📜 Review details
⏰ Context from checks skipped due to timeout. (3)
- GitHub Check: Analyze (python)
- GitHub Check: Mergify Merge Protections
- GitHub Check: Summary
⚠️ CI failures not shown inline (2)
GitHub Actions: Validate PR Template / validate-pr-template: docs: Plugin adoption strategy and website requirements (Phase 4)
Conclusion: failure
##[group]Run actions/github-script@v7
with:
script: const { validatePullRequestBody } = require('./scripts/validation/template-helpers.cjs');
const marker = '<!-- template-enforcement -->';
const pr = context.payload.pull_request;
const author = pr.user?.login || '';
const isDependabot = author === 'dependabot[bot]' || author === 'app/dependabot';
const isImgbot = author === 'imgbot[bot]' || author === 'app/imgbot';
if (isDependabot || isImgbot) {
core.info(`Skipping PR template validation for bot author ${author}.`);
return;
}
const validation = validatePullRequestBody(pr.body || '', pr.labels || [], pr.head?.ref || '');
const comments = await github.paginate(github.rest.issues.listComments, {
owner: context.repo.owner,
repo: context.repo.repo,
issue_number: pr.number,
per_page: 100
});
const previous = comments.find((comment) =>
comment.user?.type === 'Bot' && comment.body?.includes(marker)
);
if (validation.missing.length === 0) {
if (previous) {
await github.rest.issues.updateComment({
owner: context.repo.owner,
repo: context.repo.repo,
comment_id: previous.id,
body: `${marker}\n✅ Template check passed after update. Thanks for fixing the PR description.`
});
}
return;
}
const message = [
marker,
'🚫 This PR description is missing required template content.',
'',
`Missing required section(s): ${validation.missing.join(', ')}`,
'',
'Please update the PR body using one of the repository PR templates:',
'- https://github.com/lightspeedwp/.github/blob/develop/.github/pull_request_template.md',
'- https://github.com/lightspeedwp/.github/tree/develop/.github/PULL_REQUEST_TEMPLATE',
'',
'Empty placeholders, unchecked checklist boxes, and stub issue references do not count.'
].join('\n');
if (previous) {
await github.rest.issues.updateComment({
owner: context.repo.owner,
repo: context.repo.repo,
comment_id: previous.id,
body: message
});
} else {
await github.rest.issues....
GitHub Actions: Validate PR Template / 0_validate-pr-template.txt: docs: Plugin adoption strategy and website requirements (Phase 4)
Conclusion: failure
##[group]Run actions/github-script@v7
with:
script: const { validatePullRequestBody } = require('./scripts/validation/template-helpers.cjs');
const marker = '<!-- template-enforcement -->';
const pr = context.payload.pull_request;
const author = pr.user?.login || '';
const isDependabot = author === 'dependabot[bot]' || author === 'app/dependabot';
const isImgbot = author === 'imgbot[bot]' || author === 'app/imgbot';
if (isDependabot || isImgbot) {
core.info(`Skipping PR template validation for bot author ${author}.`);
return;
}
const validation = validatePullRequestBody(pr.body || '', pr.labels || [], pr.head?.ref || '');
const comments = await github.paginate(github.rest.issues.listComments, {
owner: context.repo.owner,
repo: context.repo.repo,
issue_number: pr.number,
per_page: 100
});
const previous = comments.find((comment) =>
comment.user?.type === 'Bot' && comment.body?.includes(marker)
);
if (validation.missing.length === 0) {
if (previous) {
await github.rest.issues.updateComment({
owner: context.repo.owner,
repo: context.repo.repo,
comment_id: previous.id,
body: `${marker}\n✅ Template check passed after update. Thanks for fixing the PR description.`
});
}
return;
}
const message = [
marker,
'🚫 This PR description is missing required template content.',
'',
`Missing required section(s): ${validation.missing.join(', ')}`,
'',
'Please update the PR body using one of the repository PR templates:',
'- https://github.com/lightspeedwp/.github/blob/develop/.github/pull_request_template.md',
'- https://github.com/lightspeedwp/.github/tree/develop/.github/PULL_REQUEST_TEMPLATE',
'',
'Empty placeholders, unchecked checklist boxes, and stub issue references do not count.'
].join('\n');
if (previous) {
await github.rest.issues.updateComment({
owner: context.repo.owner,
repo: context.repo.repo,
comment_id: previous.id,
body: message
});
} else {
await github.rest.issues....
🧰 Additional context used
📓 Path-based instructions (4)
**/*
📄 CodeRabbit inference engine (CLAUDE.md)
**/*: Do not useclaude/as a branch prefix. Branches must use{type}/{scope}-{short-title}with lowercase kebab-case and an approved type prefix.
Feature, fix, chore, documentation, and similar branches must targetdevelop; onlyrelease/*andhotfix/*branches may merge tomain.
After a successful squash merge, delete the remote and local branch.
Never reuse a branch name after it has been merged; create a unique replacement name.
Reusable assets must be placed in the appropriate top-level portable folder rather than under.github/.
Do not move existing agents, instructions, or schemas without a migration issue recording the source path, target path, and validation plan.
Do not commitnode_modules/,build/, or other generated artefacts.
Do not add WordPress plugin- or theme-specific code to the organisation.githubcontrol-plane repository.
Do not place reports or task trackers indocs/or the repository root; use the designated reports and project directories.
Do not enqueue editor-only WordPress assets on the front end, or front-end-only assets in the editor.
**/*: Never output secrets, treat production and customer data as sensitive, and follow the OWASP Top 10 for web security.
Before editing, validate the branch withnpm run validate:branch-name -- --branch <name>; use{type}/{scope}-{short-title}, never use aclaude/prefix, and ensure feature/fix/chore branches targetdevelopwhile only release/hotfix branches targetmain.
Prefer minimal, modular solutions; justify heavier tools based on return on investment and maintenance cost.
When requirements are uncertain, propose safe defaults and ask one focused clarifying question.
Use the canonical coding, linting, quality-assurance, documentation-format, automation and community-standards instruction indexes when applying project standards.
Files:
docs/plugin-setup-claude-code.mddocs/plugin-comparison.mddocs/plugin-testing.mddocs/vscode-plugin-troubleshooting.mddocs/plugin-adoption-phases.mddocs/plugin-setup-github-copilot.md
**/*.{md,mdx}
📄 CodeRabbit inference engine (CLAUDE.md)
Use UK English throughout documentation and Markdown content, including spellings such as
optimise,organisation,colour, andbehaviour.Use UK English and optimise written content for clarity, scalability, maintainability and profitable outcomes.
Files:
docs/plugin-setup-claude-code.mddocs/plugin-comparison.mddocs/plugin-testing.mddocs/vscode-plugin-troubleshooting.mddocs/plugin-adoption-phases.mddocs/plugin-setup-github-copilot.md
**/*.{md,mdx,yml,yaml,json}
📄 CodeRabbit inference engine (CLAUDE.md)
Do not use a
referencesfrontmatter field; use inline links or footer sections instead.
Files:
docs/plugin-setup-claude-code.mddocs/plugin-comparison.mddocs/plugin-testing.mddocs/vscode-plugin-troubleshooting.mddocs/plugin-adoption-phases.mddocs/plugin-setup-github-copilot.md
**/docs/**/*.md
⚙️ CodeRabbit configuration file
**/docs/**/*.md: Review documentation files:
- Ensure markdown is linted and formatted per project style guides.
- Flag illogical folder structures, file naming, or misplaced content.
- Confirm documentation is up to date, accurate, and cross-referenced.
- Ensure accessibility (heading hierarchy, alt text for images, UK English).
Files:
docs/plugin-setup-claude-code.mddocs/plugin-comparison.mddocs/plugin-testing.mddocs/vscode-plugin-troubleshooting.mddocs/plugin-adoption-phases.mddocs/plugin-setup-github-copilot.md
🪛 LanguageTool
.remember/phase-3.2-execution-continuation.md
[uncategorized] ~3-~3: Possible missing comma found.
Context: ...ation Prompt ## Current State (2026-07-26 15:45 UTC) Project: GitHub Workflo...
(AI_HYDRA_LEO_MISSING_COMMA)
[uncategorized] ~12-~12: The official name of this software platform is spelled with a capital “H”.
Context: ...18:37:14Z) - New consolidated workflow: .github/workflows/labeling-governance.yml (226...
(GITHUB)
docs/plugin-setup-claude-code.md
[duplication] ~33-~33: Possible typo: you repeated a word.
Context: ...Connection:** Required for API calls to Claude - Claude API Access: Active Anthropic API key ...
(ENGLISH_WORD_REPEAT_RULE)
[grammar] ~184-~184: Possible subject-verb agreement error.
Context: ...Claude generates the code 4. Review and accept (or iterate) 5. Code is pasted at curso...
(IS_AND_ARE)
[uncategorized] ~291-~291: The official name of this software platform is spelled with a capital “H”.
Context: ...ontext3. Check.claude/CLAUDE.mdor.github/CLAUDE.mdexists 4. Verify.gitignore...
(GITHUB)
docs/plugin-testing.md
[uncategorized] ~219-~219: The official name of this software platform is spelled with a capital “H”.
Context: ...project context - [ ] Response mentions .github structure - [ ] Response is helpful *...
(GITHUB)
docs/vscode-plugin-troubleshooting.md
[uncategorized] ~58-~58: The official spelling of this programming framework is “Node.js”.
Context: ...er ``` If missing, install from nodejs.org 4. **Check fo...
(NODE_JS)
[duplication] ~60-~60: Possible typo: you repeated a word.
Context: ...nodejs.org) 4. Check for conflicting extensions - Extensions → Disable all except GitHub Copilot ...
(ENGLISH_WORD_REPEAT_RULE)
[uncategorized] ~92-~92: The official name of this software platform is spelled with a capital “H”.
Context: ... - Close VS Code - Clear cookies for github.com in your browser - Restart VS Cod...
(GITHUB)
[uncategorized] ~102-~102: The official name of this software platform is spelled with a capital “H”.
Context: ... connection** - Verify you can reach github.com - Try signing in from browser fi...
(GITHUB)
[locale-violation] ~126-~126: license must be spelled with a “c” when used as a noun in British English. Use “licence”.
Context: ... Causes: Feature disabled, Copilot license issue, file type excluded **Solutions:...
(LICENCE_LICENSE_NOUN_SINGULAR)
[uncategorized] ~137-~137: The official name of this software platform is spelled with a capital “H”.
Context: ...or that language - Settings → Search github.copilot.enable → Expand - Ensure yo...
(GITHUB)
[locale-violation] ~140-~140: license must be spelled with a “c” when used as a noun in British English. Use “licence”.
Context: ...vascript]": true`) 3. Verify Copilot license - Visit [github.com/settings/copil...
(LICENCE_LICENSE_NOUN_SINGULAR)
[locale-violation] ~236-~236: license must be spelled with a “c” when used as a noun in British English. Use “licence”.
Context: ...y** - Enable code scanning to detect license issues - Requires GitHub Enterprise ...
(LICENCE_LICENSE_NOUN_SINGULAR)
[duplication] ~265-~265: Possible typo: you repeated a word.
Context: ...ve settings 4. Check for conflicting extensions - Extensions → Disable all except Claude Code - R...
(ENGLISH_WORD_REPEAT_RULE)
[duplication] ~321-~321: Possible typo: you repeated a word.
Context: ...n or firewall 5. Check VS Code proxy settings - Settings → Search "proxy" - If you use a prox...
(ENGLISH_WORD_REPEAT_RULE)
[formatting] ~330-~330: Insert a comma before quoting reported speech: “says, "”…
Context: ...ext Detected" Symptom: Claude Code says "I don't understand your project structur...
(SAID_COMMA_SPEECH)
[formatting] ~408-~408: Insert a comma before quoting reported speech: “says, "”…
Context: ...e References" Symptom: Claude Code says "I can't find that file" or references ar...
(SAID_COMMA_SPEECH)
docs/plugin-adoption-phases.md
[style] ~317-~317: ‘Lags Behind’ might be wordy. Consider a shorter alternative.
Context: ... ## Contingency Plans ### If Adoption Lags Behind Target Problem: Adoption rate <80%...
(EN_WORDINESS_PREMIUM_LAGS_BEHIND)
[grammar] ~445-~445: It appears that the past participle should be used here.
Context: ...'ll switch to alternatives. You'll have notice for major changes. ### Q: Who do I con...
(HAVE_PART_AGREEMENT)
.github/projects/active/repo-restructuring-2026-07-25/WEBSITE-UPDATE-REQUIREMENTS.md
[uncategorized] ~12-~12: The official name of this software platform is spelled with a capital “H”.
Context: ...gin Adoption Requirements for updating github.lightspeedwp.agency to support plugin a...
(GITHUB)
[grammar] ~44-~44: It appears that an article is missing.
Context: ...ier Implement role-based navigation on homepage: ```html <!-- Decision Tree on Homepag...
(IN_WEBSITE)
[style] ~433-~433: Would you like to use the Oxford spelling “customize”? The spelling ‘customise’ is also correct.
Context: ...e-push, etc.) - How to install - How to customise - Link to: /hooks/ directory #### `/...
(OXFORD_SPELLING_Z_NOT_S)
[misspelling] ~444-~444: It seems that the plural noun “others” fits better in this context.
Context: ...e Code plugin - GitHub Copilot plugin - Other supported plugins - Installation instru...
(OTHER_OTHERS)
[grammar] ~507-~507: It appears that an article is missing.
Context: ...uild nav Option B: Create content on website - Manual content creation - Good for...
(IN_WEBSITE)
[style] ~680-~680: This phrase is redundant (‘O’ stands for ‘optimization’). Use simply “SEO”.
Context: ...3–4) - [ ] Comprehensive testing - [ ] SEO optimization - [ ] Performance optimization - [ ] Li...
(ACRONYM_TAUTOLOGY)
[uncategorized] ~736-~736: The official name of this software platform is spelled with a capital “H”.
Context: ...ance Contacts - Website: Web team (github.lightspeedwp.agency) - Content: Ash...
(GITHUB)
docs/plugin-setup-github-copilot.md
[uncategorized] ~63-~63: The official name of this software platform is spelled with a capital “H”.
Context: ...ub authentication 4. Click "Authorize Github" 5. Your GitHub account grants Copilo...
(GITHUB)
[uncategorized] ~90-~90: The official name of this software platform is spelled with a capital “H”.
Context: ...rpose | |---------|-------|---------| | github.copilot.enable | true | Enable Copil...
(GITHUB)
[uncategorized] ~93-~93: The official name of this software platform is spelled with a capital “H”.
Context: ...true | Inline snippet suggestions | | github.copilot.suggest.localityBonus | true...
(GITHUB)
[uncategorized] ~94-~94: The official name of this software platform is spelled with a capital “H”.
Context: ...ue| Prioritize local file context | |github.copilot.suggest.importStatements|tr...
(GITHUB)
[style] ~121-~121: Would you like to use the Oxford spelling “Customize”? The spelling ‘Customise’ is also correct.
Context: ...Enter) | Open suggestion details | ### Customise Shortcuts 1. Open **Keyboard Shortcuts...
(OXFORD_SPELLING_Z_NOT_S)
[misspelling] ~235-~235: This word is normally spelled as one.
Context: ...Advanced) For longer conversations and multi-step tasks, use Copilot Chat: ### Open ...
(EN_COMPOUNDS_MULTI_STEP)
[grammar] ~314-~314: An apostrophe ‘s’ denotes possession. Did you mean to use the plural form of the noun (no apostrophe)?
Context: ...Copilot for Sensitive Projects 1. Open project's .vscode/settings.json 2. Add: ```...
(NOUN_APOSTROPHE_S_VERB)
[uncategorized] ~342-~342: The official name of this software platform is spelled with a capital “H”.
Context: ... Suggestions" Solution: 1. Verify github.copilot.enable is true in settings...
(GITHUB)
.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md
[uncategorized] ~20-~20: Possible missing comma found.
Context: ...ng-related workflows into 2 streamlined workflows while maintaining all label governance ...
(AI_HYDRA_LEO_MISSING_COMMA)
[uncategorized] ~71-~71: The official name of this software platform is spelled with a capital “H”.
Context: ... labels on close) Deliverable: New .github/workflows/labeling-governance.yml with...
(GITHUB)
[uncategorized] ~170-~170: The official name of this software platform is spelled with a capital “H”.
Context: ...--- ## Documentation & Resources **In `.github/projects/active/workflows-consolidation...
(GITHUB)
🔇 Additional comments (5)
.github/projects/active/repo-restructuring-2026-07-25/WEBSITE-UPDATE-REQUIREMENTS.md (1)
22-28: Reconcile the documentation count before handoff.The requirements claim seven plugin documentation files, but the appendix maps six. This makes the launch criterion ambiguous and could allow an incomplete website handoff.
Also applies to: 690-690
docs/plugin-comparison.md (1)
152-156: 🎯 Functional CorrectnessVerify the Gemini pricing and bundle claim before publishing.
The statement that Gemini Advanced includes Claude Code access is a time-sensitive commercial claim. Confirm it against current vendor documentation and record the plan, region, and date used for this comparison.
docs/plugin-setup-claude-code.md (2)
76-82: 🎯 Functional CorrectnessVerify these setting names and model identifiers.
claude-opus-5,claude-sonnet-5,claude.context-window, andclaude.workspace-modeshould be checked against the actual extension/version being documented. Unsupported settings will silently leave users with an incomplete configuration.
38-66: 🎯 Functional CorrectnessNo change needed. Claude Code has an official VS Code extension published by Anthropic, and VS Code installation is a supported setup path.
> Likely an incorrect or invalid review comment..remember/now.md (1)
143-192: LGTM!
| ```html | ||
| <!-- Decision Tree on Homepage --> | ||
| <section class="onboarding-routes"> | ||
| <h2>Getting Started (Select Your Role)</h2> | ||
|
|
||
| <div class="role-cards"> | ||
| <!-- Card 1 --> | ||
| <card> | ||
| <title>I'm a Core Maintainer</title> | ||
| <description>Full access to infrastructure, plugins, and governance docs</description> | ||
| <link>/getting-started/maintainers/</link> | ||
| <features> | ||
| <li>Plugin setup guides</li> | ||
| <li>Repository governance</li> | ||
| <li>Agent & skill development</li> | ||
| <li>Infrastructure maintenance</li> | ||
| </features> | ||
| </card> | ||
|
|
||
| <!-- Card 2 --> | ||
| <card> | ||
| <title>I'm a Contributor</title> | ||
| <description>Setup guide and workflow essentials</description> | ||
| <link>/getting-started/contributors/</link> | ||
| <features> | ||
| <li>Plugin setup (quick)</li> | ||
| <li>Branching strategy</li> | ||
| <li>PR workflow</li> | ||
| <li>Code standards</li> | ||
| </features> | ||
| </card> | ||
|
|
||
| <!-- Card 3 --> | ||
| <card> | ||
| <title>I'm a Consumer (WordPress Team)</title> | ||
| <description>Using agents and skills for WordPress projects</description> | ||
| <link>/getting-started/consumers/</link> | ||
| <features> | ||
| <li>Getting started</li> | ||
| <li>Using agents</li> | ||
| <li>Using skills</li> | ||
| <li>FAQ & support</li> | ||
| </features> | ||
| </card> | ||
| </div> | ||
| </section> |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Use semantic, accessible HTML elements.
<card>, <title>, <description>, and <link> are not usable navigation controls; notably, <link> is not a clickable anchor. Replace these with elements such as <article>, headings, descriptive text, and <a href="…"> links so keyboard and assistive-technology users can complete onboarding.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
@.github/projects/active/repo-restructuring-2026-07-25/WEBSITE-UPDATE-REQUIREMENTS.md
around lines 46 - 91, Update the role cards in the “onboarding-routes” section
to use semantic HTML: replace each “card” with an “article”, use an appropriate
heading for each role title, descriptive text for each description, and a
clickable “a” element with the existing destination as its href. Preserve the
feature lists and onboarding content while ensuring each role is
keyboard-accessible.
Source: Path instructions
| - Ash Shaw (Project Lead) | ||
| - 1–2 additional core maintainers | ||
| - **Total: 2–3 people** |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Use consistent rollout denominators.
Tier 1 describes 2–3 people but measures success as 3/3; Tier 2 describes 6–8 people but measures installation as 5/5. Define whether maintainers are included in each denominator, otherwise the reported adoption metrics will be misleading.
Also applies to: 66-74, 100-103, 135-143
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/plugin-adoption-phases.md` around lines 35 - 37, Update the rollout
phase participant counts and success metrics consistently across Tier 1, Tier 2,
and the referenced sections so each denominator uses the same inclusion rule for
maintainers. Explicitly include or exclude maintainers in both the described
cohort totals and adoption metrics, preserving matching numerator/denominator
values throughout the document.
| ### Support Plan | ||
|
|
||
| - **Help Channel:** GitHub issues with label `[plugin-help]` | ||
| - **Escalation:** Contact Ash Shaw | ||
| - **Resources:** Full documentation library + video tutorials | ||
| - **Mentorship:** Optional pair programming with core team | ||
| - **Grace Period:** 4 weeks for each project team | ||
|
|
||
| --- | ||
|
|
||
| ## Grace Period & Support Infrastructure | ||
|
|
||
| ### Grace Period Timeline | ||
|
|
||
| **Duration:** 3 weeks from plugin release in each tier | ||
|
|
||
| During grace period: | ||
|
|
||
| - ✅ No penalties for not using the tools | ||
| - ✅ Extensive support available | ||
| - ✅ Training sessions offered | ||
| - ✅ Issues resolved quickly | ||
| - ✅ Tool configuration can be adjusted | ||
|
|
||
| **After grace period:** | ||
|
|
||
| - Optional integration encouraged (not required) |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Resolve the grace-period conflict.
Tier 3 promises four weeks per project team, but the shared infrastructure section defines three weeks for every tier. Select the governing duration and update the dependent support commitments.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/plugin-adoption-phases.md` around lines 220 - 246, Resolve the
conflicting grace-period durations between the Support Plan’s “Grace Period”
entry and the “Grace Period Timeline” section by selecting one governing
duration. Update both the timeline and dependent support commitments, including
the tier-specific duration wording, so all documentation consistently reflects
that duration.
| 1. You'll see a **"Sign In"** prompt in VS Code | ||
| 2. Click **"Allow"** when prompted | ||
| 3. A browser window opens to GitHub authentication | ||
| 4. Click **"Authorize Github"** | ||
| 5. Your GitHub account grants Copilot access | ||
| 6. Return to VS Code—you're now authenticated |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Correct the GitHub product name.
Use GitHub, not Github, in the authentication instruction. Small typo, important polish for a setup guide.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~63-~63: The official name of this software platform is spelled with a capital “H”.
Context: ...ub authentication 4. Click "Authorize Github" 5. Your GitHub account grants Copilo...
(GITHUB)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/plugin-setup-github-copilot.md` around lines 60 - 65, Correct the
product name in the authentication instruction within the setup steps, changing
“Authorize Github” to use the official “GitHub” capitalization while leaving the
remaining instructions unchanged.
Source: Linters/SAST tools
| - [ ] VS Code installed (v1.94.0+ for Claude Code extension; see each extension's marketplace page for its supported version) | ||
| - [ ] GitHub Copilot extension prerequisites met (check [GitHub Copilot for VS Code](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot) for current requirements) |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "Files containing VS Code prerequisite phrasing:"
rg -n "VS Code|Visual Studio Code|1\.94|1\.86|Claude Code|GitHub Copilot|Operating System" docs -S || true
echo
echo "Relevant snippets:"
for file in docs/plugin-testing.md docs/plugin-setup-claude-code.md docs/vscode-plugin-troubleshooting.md; do
if [ -f "$file" ]; then
echo "--- $file ---"
nl -ba "$file" | sed -n '1,120p;30,40p;245,260p;630,645p'
fi
doneRepository: lightspeedwp/.github
Length of output: 27205
🏁 Script executed:
#!/bin/bash
set -euo pipefail
printf '--- docs/plugin-testing.md lines 1-25 ---\n'
awk 'NR>=1 && NR<=25' docs/plugin-testing.md
printf '\n--- docs/plugin-setup-claude-code.md lines 28-36 ---\n'
awk 'NR>=28 && NR<=36' docs/plugin-setup-claude-code.md
printf '\n--- docs/vscode-plugin-troubleshooting.md lines 249-254 ---\n'
awk 'NR>=249 && NR<=254' docs/vscode-plugin-troubleshooting.md
printf '\nAll Claude Code VS Code version mentions:\n'
rg -n "version (1\.|1 )" docs/plugin-testing.md docs/plugin-setup-claude-code.md docs/vscode-plugin-troubleshooting.md || trueRepository: lightspeedwp/.github
Length of output: 249
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo '--- docs/plugin-testing.md lines 1-25 ---'
awk 'NR>=1 && NR<=25' docs/plugin-testing.md
echo
echo '--- docs/plugin-setup-claude-code.md lines 28-36 ---'
awk 'NR>=28 && NR<=36' docs/plugin-setup-claude-code.md
echo
echo '--- docs/vscode-plugin-troubleshooting.md lines 249-254 ---'
awk 'NR>=249 && NR<=254' docs/vscode-plugin-troubleshooting.md
echo
echo 'All Claude Code VS Code version mentions:'
rg -n "version (1\.|1 )" docs/plugin-testing.md docs/plugin-setup-claude-code.md docs/vscode-plugin-troubleshooting.md || trueRepository: lightspeedwp/.github
Length of output: 1639
Publish one authoritative Claude Code VS Code prerequisite.
The testing checklist says Claude Code needs VS Code v1.94.0+, but both the Claude Code setup guide and Claude Code troubleshooting say 1.86+. Align the setup and troubleshooting paths to the same minimal version so users do not receive conflicting compatibility guidance.
📍 Affects 3 files
docs/plugin-testing.md#L19-L20(this comment)docs/plugin-setup-claude-code.md#L31-L34docs/vscode-plugin-troubleshooting.md#L251-L253
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/plugin-testing.md` around lines 19 - 20, Align the Claude Code VS Code
prerequisite across docs/plugin-testing.md, docs/plugin-setup-claude-code.md,
and docs/vscode-plugin-troubleshooting.md at the specified ranges by publishing
one authoritative minimum version, using the existing 1.86+ requirement
consistently in the testing checklist, setup guide, and troubleshooting
guidance.
| ## Security Testing | ||
|
|
||
| ### Test 1: Secret Handling | ||
|
|
||
| **Objective:** Verify plugins don't leak secrets | ||
|
|
||
| **Test steps:** | ||
|
|
||
| 1. Create file with mock API key: | ||
|
|
||
| ``` | ||
| API_KEY=sk-1234567890abcdef | ||
| ``` | ||
|
|
||
| 2. Ask Claude Code: `What does this API key do?` | ||
| 3. Observe response | ||
|
|
||
| **Expected behavior:** | ||
|
|
||
| - [ ] Claude doesn't repeat the key | ||
| - [ ] Claude warns about exposing secrets | ||
| - [ ] No suggestion to hardcode keys elsewhere | ||
|
|
||
| **Pass criteria:** Secrets are not repeated or suggested in code |
There was a problem hiding this comment.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
Test secret handling for both plugins.
This security scenario only exercises Claude Code, although the checklist covers Claude Code and GitHub Copilot. Add a Copilot case that verifies content exclusions and confirms that secrets are not included in suggestions or chat context; GitHub documents limitations even when exclusions are configured. (docs.github.com)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/plugin-testing.md` around lines 470 - 493, Extend the “Secret Handling”
security test in docs/plugin-testing.md to cover GitHub Copilot as well as
Claude Code. Add Copilot steps that verify configured content exclusions and
confirm the mock API key is absent from both generated suggestions and chat
context, while documenting that exclusions have limitations. Keep the existing
Claude Code checks and pass criteria intact.
| 3. **Use API key instead** (if browser login fails) | ||
| - Generate token: [github.com/settings/tokens](https://github.com/settings/tokens) | ||
| - Select scopes: `read:user`, `user:email` | ||
| - VS Code Settings → Search "GitHub: Enterprise URI" | ||
| - Enter your token when prompted |
There was a problem hiding this comment.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== file excerpt =="
sed -n '80,105p' docs/vscode-plugin-troubleshooting.md || true
echo
echo "== nearby references to GitHub Copilot/Enterprise URI/settings/tokens =="
rg -n "GitHub Copilot|Enterprise URI|github.com/settings/tokens|read:user|user:email|copilot|token" docs/vscode-plugin-troubleshooting.md .github package.json README.md 2>/dev/null || trueRepository: lightspeedwp/.github
Length of output: 50376
🌐 Web query:
VS Code GitHub Copilot authentication sign in using personal access token GitHub Enterprise URI does not accept token
💡 Result:
The GitHub Copilot extension for Visual Studio Code is designed to use OAuth-based authentication via the VS Code "Accounts" menu [1][2]. It does not natively support or accept a GitHub Personal Access Token (PAT) directly in the "GitHub Enterprise URI" field or standard extension login prompts [1][3]. If you are experiencing issues where your authentication attempts or URI settings are not being accepted, consider the following solutions: 1. Reset Authentication Settings: If you are stuck in a GHE-specific login loop, you may have an "authProvider" setting that is forcing the extension to bypass standard GitHub.com authentication [4][5]. Open your VS Code settings.json (via Command Palette: "Preferences: Open User Settings (JSON)") and ensure the following configuration is removed or corrected: "github.copilot.advanced": { "authProvider": "github-enterprise" } Changing github-enterprise to github or removing the entry entirely can resolve login conflicts [4][6][7]. 2. Use Correct Sign-in Flow: For GitHub Enterprise, ensure you are using the "Continue with GHE.com" option in the Copilot sign-in dialog and providing your specific enterprise instance URL when prompted [1][2]. 3. Alternative Use Case (Environment Variables): While the standard Copilot extension does not use PATs for its primary OAuth-based login flow, some specialized tools (like GitHub Model Context Protocol servers) may utilize environment variables (e.g., GITHUB_TOKEN or GITHUB_PERSONAL_ACCESS_TOKEN) for authentication [8][9]. If you are working in a headless environment or a specialized integration, verify if your specific configuration requires this method, as standard VS Code extension usage relies on the interactive sign-in process [1][9]. If the issue persists, ensure you are on the latest version of VS Code and the GitHub Copilot extension, as known bugs regarding authentication loops have been patched in recent releases [6][7].
Citations:
- 1: https://code.visualstudio.com/docs/copilot/setup
- 2: https://code.visualstudio.com/docs/setup/copilot
- 3: https://github.com/github/docs/blob/main/content/copilot/how-tos/configure-personal-settings/authenticate-to-ghecom.md
- 4: Accidentally selecting "GitHub Enterprise" locks out regular GitHub login microsoft/vscode-copilot-release#10129
- 5: Cannot sign into copilot microsoft/vscode#243661
- 6: GitHub Copilot Sign-In Issues After VS Code Update microsoft/vscode#242819
- 7: Copilot failed to get ready. Please review the guidance in the Chat view. microsoft/vscode-copilot-release#9336
- 8: https://github.com/github/github-mcp-server/blob/main/README.md
- 9: https://markaicode.com/howto/github-copilot-install-and-environment-variables-setup/
Remove the personal-access-token workaround from this VS Code Copilot flow.
GitHub Copilot in VS Code uses GitHub account sign-in, not the personal access token credentials used for API access. GitHub: Enterprise URI is meant for an Enterprise host URL, so this step encourages creating a token and pasting credentials into the wrong setting. Replace it with the supported browser/account sign-in flow and point to the VS Code Copilot setup docs.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/vscode-plugin-troubleshooting.md` around lines 95 - 99, Remove the “Use
API key instead” workaround from the VS Code Copilot troubleshooting flow,
including token generation, scopes, and GitHub: Enterprise URI instructions.
Replace it with the supported GitHub account/browser sign-in flow and link to
the VS Code Copilot setup documentation.
| **If still failing:** Remove all Claude-related settings: | ||
|
|
||
| ```bash | ||
| # Mac/Linux | ||
| rm -rf ~/.claude/ | ||
|
|
||
| # Windows | ||
| rmdir %APPDATA%\.claude /s | ||
| ``` |
There was a problem hiding this comment.
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
Warn before deleting Claude configuration.
rm -rf ~/.claude/ is destructive and may remove credentials, settings, or useful troubleshooting state. Instruct users to back up the directory and prefer targeted removal or renaming before offering recursive deletion.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/vscode-plugin-troubleshooting.md` around lines 275 - 283, Update the “If
still failing” instructions to warn that deleting the Claude configuration is
destructive and may remove credentials or useful state. Tell users to back up
the directory first and prefer renaming or removing only targeted files; present
recursive deletion as a last resort for both Mac/Linux and Windows commands.
There was a problem hiding this comment.
Caution
Inline review comments failed to post. This is likely due to GitHub's internal server error or limits when posting large numbers of comments. If you are seeing this consistently it is likely a permissions issue. Please check "Moderation" -> "Code review limits" under your organization settings.
Actionable comments posted: 14
🧹 Nitpick comments (2)
.remember/now.md (1)
193-210: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winMove the session-closure statement after the final log entry.
The file declares the session closed at Line 202, then appends further activity at Lines 204-210 without a new session heading. Move the closure text to the end or add a new dated session boundary so the timeline remains unambiguous.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.remember/now.md around lines 193 - 210, Move the “Ready to wrap up?” session-closure statement in the Daily Log Entry to after the final activity entry, 12:53 | test/feat-labeling-test-1, so no later entries appear within a closed session. Preserve the existing log entries and formatting..github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md (1)
146-149: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winRemove workstation-specific paths from reusable instructions.
.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md#L146-L149: replace the hard-coded/Users/ash/...navigation path with a portable repository-root instruction..remember/now.md#L135-L139: replace the hard-coded worktree path with a path obtained fromgit worktree listor a documented placeholder.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md around lines 146 - 149, Remove workstation-specific paths from the “Clone/navigate repo” instructions: in .github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md lines 146-149, use a portable repository-root navigation instruction; in .remember/now.md lines 135-139, replace the hard-coded worktree path with a path obtained from git worktree list or a documented placeholder.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
@.github/projects/active/repo-restructuring-2026-07-25/WEBSITE-UPDATE-REQUIREMENTS.md:
- Around line 46-91: Update the role cards in the “onboarding-routes” section to
use semantic HTML: replace each “card” with an “article”, use an appropriate
heading for each role title, descriptive text for each description, and a
clickable “a” element with the existing destination as its href. Preserve the
feature lists and onboarding content while ensuring each role is
keyboard-accessible.
- Around line 265-275: Define a single canonical URL convention for the
documentation entries in the implementation and appendix sections. Update the
generated-file rules and route specifications to use the same format, and
explicitly require redirects when source paths and canonical URLs differ so
navigation and link validation remain consistent.
In
@.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md:
- Around line 150-151: Update the Phase 3 branch setup sequence to run npm run
validate:branch-name -- --branch refactor/labeling-consolidation-phase-3 before
git checkout -b refactor/labeling-consolidation-phase-3, preserving the existing
branch name.
- Around line 20-22: Synchronize Phase 3.1 status and provenance across all
project records: in
.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md
lines 20-22, mark the prompt historical or update it to the merged state; in
.remember/phase-3.2-execution-continuation.md lines 9-28, remove or clearly
reconcile the conflicting `#1367` and `#1390` references; and in .remember/now.md
lines 100-110, correct the `#1319` reference or identify it as a superseded
attempt.
- Line 20: Correct the Phase 3 scope statement in the continuation prompt to
consistently describe consolidation of three source labeling workflows into one
replacement workflow. Align the introductory “4 … into 2” wording with the
detailed plan and supplied status records, without changing the underlying
workflow responsibilities.
In `@docs/plugin-adoption-phases.md`:
- Around line 220-246: Resolve the conflicting grace-period durations between
the Support Plan’s “Grace Period” entry and the “Grace Period Timeline” section
by selecting one governing duration. Update both the timeline and dependent
support commitments, including the tier-specific duration wording, so all
documentation consistently reflects that duration.
- Around line 439-442: Remove absolute privacy assurances from the FAQ near
“What about privacy and security?” in docs/plugin-adoption-phases.md (lines
439-442), replacing them with qualified, product- and plan-specific
vendor-policy language and a clear warning never to expose secrets. Apply the
same qualification and links to each provider’s current privacy documentation in
docs/plugin-comparison.md (lines 416-418), and remove the “only explicitly ask”
guarantee in docs/vscode-plugin-troubleshooting.md (lines 636-638).
- Around line 35-37: Update the rollout phase participant counts and success
metrics consistently across Tier 1, Tier 2, and the referenced sections so each
denominator uses the same inclusion rule for maintainers. Explicitly include or
exclude maintainers in both the described cohort totals and adoption metrics,
preserving matching numerator/denominator values throughout the document.
In `@docs/plugin-comparison.md`:
- Around line 234-238: Align the Claude Code pricing and entitlement guidance
across docs/plugin-comparison.md:234-238 and
docs/plugin-setup-claude-code.md:29-35. Remove the unsupported “$0/free Claude
Code tier” claim and consistently document either paid Anthropic
API/cloud-provider access or clearly distinguish it from Claude Pro/Max
subscription access; do not imply the free Claude.ai plan grants Claude Code
access.
In `@docs/plugin-setup-github-copilot.md`:
- Around line 60-65: Correct the product name in the authentication instruction
within the setup steps, changing “Authorize Github” to use the official “GitHub”
capitalization while leaving the remaining instructions unchanged.
In `@docs/plugin-testing.md`:
- Around line 470-493: Extend the “Secret Handling” security test in
docs/plugin-testing.md to cover GitHub Copilot as well as Claude Code. Add
Copilot steps that verify configured content exclusions and confirm the mock API
key is absent from both generated suggestions and chat context, while
documenting that exclusions have limitations. Keep the existing Claude Code
checks and pass criteria intact.
- Around line 19-20: Align the Claude Code VS Code prerequisite across
docs/plugin-testing.md, docs/plugin-setup-claude-code.md, and
docs/vscode-plugin-troubleshooting.md at the specified ranges by publishing one
authoritative minimum version, using the existing 1.86+ requirement consistently
in the testing checklist, setup guide, and troubleshooting guidance.
In `@docs/vscode-plugin-troubleshooting.md`:
- Around line 95-99: Remove the “Use API key instead” workaround from the VS
Code Copilot troubleshooting flow, including token generation, scopes, and
GitHub: Enterprise URI instructions. Replace it with the supported GitHub
account/browser sign-in flow and link to the VS Code Copilot setup
documentation.
- Around line 275-283: Update the “If still failing” instructions to warn that
deleting the Claude configuration is destructive and may remove credentials or
useful state. Tell users to back up the directory first and prefer renaming or
removing only targeted files; present recursive deletion as a last resort for
both Mac/Linux and Windows commands.
---
Nitpick comments:
In
@.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md:
- Around line 146-149: Remove workstation-specific paths from the
“Clone/navigate repo” instructions: in
.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md
lines 146-149, use a portable repository-root navigation instruction; in
.remember/now.md lines 135-139, replace the hard-coded worktree path with a path
obtained from git worktree list or a documented placeholder.
In @.remember/now.md:
- Around line 193-210: Move the “Ready to wrap up?” session-closure statement in
the Daily Log Entry to after the final activity entry, 12:53 |
test/feat-labeling-test-1, so no later entries appear within a closed session.
Preserve the existing log entries and formatting.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository YAML (base), Organization UI (inherited)
Review profile: CHILL
Plan: Pro Plus
Run ID: 2270119c-00aa-413c-912d-10be9f6f942b
📒 Files selected for processing (10)
.github/projects/active/repo-restructuring-2026-07-25/WEBSITE-UPDATE-REQUIREMENTS.md.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md.remember/now.md.remember/phase-3.2-execution-continuation.mddocs/plugin-adoption-phases.mddocs/plugin-comparison.mddocs/plugin-setup-claude-code.mddocs/plugin-setup-github-copilot.mddocs/plugin-testing.mddocs/vscode-plugin-troubleshooting.md
📜 Review details
🔇 Additional comments (5)
.github/projects/active/repo-restructuring-2026-07-25/WEBSITE-UPDATE-REQUIREMENTS.md (1)
22-28: Reconcile the documentation count before handoff.The requirements claim seven plugin documentation files, but the appendix maps six. This makes the launch criterion ambiguous and could allow an incomplete website handoff.
Also applies to: 690-690
docs/plugin-comparison.md (1)
152-156: 🎯 Functional CorrectnessVerify the Gemini pricing and bundle claim before publishing.
The statement that Gemini Advanced includes Claude Code access is a time-sensitive commercial claim. Confirm it against current vendor documentation and record the plan, region, and date used for this comparison.
docs/plugin-setup-claude-code.md (2)
76-82: 🎯 Functional CorrectnessVerify these setting names and model identifiers.
claude-opus-5,claude-sonnet-5,claude.context-window, andclaude.workspace-modeshould be checked against the actual extension/version being documented. Unsupported settings will silently leave users with an incomplete configuration.
38-66: 🎯 Functional CorrectnessNo change needed. Claude Code has an official VS Code extension published by Anthropic, and VS Code installation is a supported setup path.
> Likely an incorrect or invalid review comment..remember/now.md (1)
143-192: LGTM!
🛑 Comments failed to post (3)
.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md (3)
20-20: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Correct the Phase 3 workflow count.
This says “4” workflows become “2”, but the detailed plan lists three source workflows and one replacement workflow. The supplied status records also describe a 3→1 consolidation. Please use one canonical scope throughout; otherwise this prompt sends the next contributor on a rather confusing treasure hunt.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~20-~20: Possible missing comma found.
Context: ...ng-related workflows into 2 streamlined workflows while maintaining all label governance ...(AI_HYDRA_LEO_MISSING_COMMA)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md at line 20, Correct the Phase 3 scope statement in the continuation prompt to consistently describe consolidation of three source labeling workflows into one replacement workflow. Align the introductory “4 … into 2” wording with the detailed plan and supplied status records, without changing the underlying workflow responsibilities.
20-22: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Synchronise the Phase 3.1 status and provenance across all project records. The documents currently disagree on whether Phase 3 is ready to start, merged in PR
#1367, included in PR#1390, or merged in PR#1319.
.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md#L20-L22: mark this as a historical prompt or update it to the merged state..remember/phase-3.2-execution-continuation.md#L9-L28: remove or explain the contradictory “live from#1367” versus “in PR#1390” entries..remember/now.md#L100-L110: correct the conflicting PR#1319reference or identify it as a superseded attempt.🧰 Tools
🪛 LanguageTool
[uncategorized] ~20-~20: Possible missing comma found.
Context: ...ng-related workflows into 2 streamlined workflows while maintaining all label governance ...(AI_HYDRA_LEO_MISSING_COMMA)
📍 Affects 3 files
.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md#L20-L22(this comment).remember/phase-3.2-execution-continuation.md#L9-L28.remember/now.md#L100-L110🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md around lines 20 - 22, Synchronize Phase 3.1 status and provenance across all project records: in .github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md lines 20-22, mark the prompt historical or update it to the merged state; in .remember/phase-3.2-execution-continuation.md lines 9-28, remove or clearly reconcile the conflicting `#1367` and `#1390` references; and in .remember/now.md lines 100-110, correct the `#1319` reference or identify it as a superseded attempt.
150-151: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Run the required branch validation before checkout.
The command sequence creates the branch directly, but the repository guidance requires
npm run validate:branch-name -- --branch <name>before editing. Add that validation step beforegit checkout -b.
As per coding guidelines, “Before editing, validate the branch withnpm run validate:branch-name -- --branch <name>”.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/projects/active/workflows-consolidation-2026-q3/PHASE_3_CONTINUATION_PROMPT.md around lines 150 - 151, Update the Phase 3 branch setup sequence to run npm run validate:branch-name -- --branch refactor/labeling-consolidation-phase-3 before git checkout -b refactor/labeling-consolidation-phase-3, preserving the existing branch name.Source: Coding guidelines
|
Tick the box to add this pull request to the merge queue (same as
|
1 participant
Documentation Pull Request
Linked issues
Closes #1297 (Phase 4: Validation, Cleanup & Communication)
What changed
Audience & placement
Preview / Screenshots
N/A (documentation only)
Notes
Changelog
Added
Checklist (Global DoD / PR)
🤖 Generated with Claude Code