feat: initialize portable AI plugin restructuring project with comprehensive epic, batch, and issue planning documentation.#322
Open
ashleyshaw wants to merge 1 commit into
Open
Conversation
…hensive epic, batch, and issue planning documentation.
Contributor
|
Note
|
| Layer / File(s) | Summary |
|---|---|
Issues index and parent epic hierarchy .github/projects/active/portable-ai-plugin-restructure/issues/README.md, .github/projects/active/portable-ai-plugin-restructure/issues/parents/* |
Master index defines all issue drafts with live GitHub issue URLs and batch ownership. Four parent epics (01-epic-planning-control-and-skeleton.md, 02-epic-portable-source-migration.md, 03-epic-core-plugin-and-tool-compatibility.md, 04-epic-validation-docs-and-rollout.md) frame the initiative into planning, migration, plugin, and validation phases, each with linked child issues, milestones, acceptance criteria, and DoR/DoD checklists. |
Planning, control, and folder skeleton (batches 0–1) .github/projects/active/portable-ai-plugin-restructure/issues/children/batch-00-planning-control/*, .github/projects/active/portable-ai-plugin-restructure/issues/children/batch-01-skeleton-boundary/* |
Initial phase: audit current AI asset inventory and create migration decision map; capture baseline dependency and validation state; plan GitHub milestones, labels, and issue linking; create top-level folder skeleton (/.schemas, /agents, /cookbook, /hooks, /instructions, /plugins, /skills, /workflows); document folder ownership via index READMEs; refactor file-organisation guidance to distinguish GitHub-native from portable assets; and scope repo-local Copilot instructions. |
Source migration audit and classification (batch 2) .github/projects/active/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/* |
Audit and validation before moving assets: classify GitHub-native files (templates, workflows, Dependabot, Copilot/agent files) that must stay under .github; clean stale path references and filename mismatches; audit and migrate reusable instruction files, agent specs, and JSON schemas to new top-level folders; define /workflows as portable agentic workflow source (separate from GitHub Actions). |
Skills library and cookbook foundation (batch 3) .github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/* |
Establish portable skills/cookbook structure: audit and classify legacy prompts; create /skills library index and naming conventions; create P0 governance skills (lightspeed-frontmatter-audit, lightspeed-pr-review, lightspeed-label-governance); document the initial /cookbook structure and establish favourite-skills backlog with candidate plugin themes. |
Pilot plugin implementation (batch 4) .github/projects/active/portable-ai-plugin-restructure/issues/children/batch-04-pilot-plugin/* |
Build the first portable plugin: create plugins/lightspeed-github-ops folder skeleton and README; add tool-specific plugin manifests (Copilot, Codex, Claude Code) with validation; package selected agent and pilot skills into the plugin; write installation, update, and troubleshooting guides covering VS Code/GitHub Copilot, Codex, and Claude Code. |
Validation and test infrastructure (batch 5) .github/projects/active/portable-ai-plugin-restructure/issues/children/batch-05-validation-reset/* |
Establish read-only, non-mutating validation: split validation commands from format/fix commands; add structure validation (required folders, READMEs, plugin packages); add plugin-manifest and skill-folder validators; add frontmatter validation and local Markdown link validators (treating archived legacy paths as warnings); fix misleading test coverage reporting and import-time side effects. |
Pilot release and findings documentation (batch 6) .github/projects/active/portable-ai-plugin-restructure/issues/children/batch-06-pilot-release/* |
Validate and roll out the pilot: run local tool smoke tests across VS Code, GitHub Copilot, Codex, and Claude Code; pilot the plugin in a LightSpeed repository and document gaps; research and plan future plugin pack backlogs; document all findings and learnings; validate release readiness across all acceptance criteria. |
Product requirements and strategic foundation .github/projects/active/portable-ai-plugin-restructure/portable-ai-plugin-restructure-prd-2026-05-14.md |
Comprehensive PRD (979 lines): defines problem statement, primary/secondary goals, non-goals, target folder structure, ownership boundaries, plugin product model, migration rules (instruction/agent/schema/workflow handling), functional and non-functional requirements, architecture decisions (keeping .github as governance, using top-level portable folders, piloting one plugin, separating GitHub Actions from agentic workflows), phased delivery plan (Phases 0–6 with exit criteria), favourite skills backlog, validation/test strategy, risk register, open decisions, acceptance criteria, immediate next actions, and appendices covering stale path cleanup and narrative arc. |
Estimated code review effort
🎯 2 (Simple) | ⏱️ ~12 minutes
Possibly related issues
#286: This PR adds the exact[Audit] Inventory AI assets and create the migration decision mapissue definition (batch-00, issue 00-01).#288: The PR includes theCreate milestone, label, and issue linking plantask matching the issue scope and checklist.#289: The PR adds theCreate target folder skeletontask (batch-01, issue 01-01) with required folder structure.#290: The PR includes theDocument folder ownership indexesdocumentation task (batch-01, issue 01-02).#291: The PR adds theRefactor file-organisation boundarytask (batch-01, issue 01-03) addressing.githubvs portable asset guidance.#292: The PR includes theScope .github Copilot instructions to this repo onlyrefactor (batch-01, issue 01-04).#293: The PR adds theClassify GitHub-native files that must remain in .githubaudit (batch-02, issue 02-01).#294: The PR includes theClean stale path references before migrationmaintenance task (batch-02, issue 02-02).#295: The PR adds theMigrate portable instructions to /instructionsrefactor (batch-02, issue 02-03).#296: The PR includes theMigrate portable agent specs to /agentsrefactor (batch-02, issue 02-04).#297: The PR adds theMove active schemas to /.schemasrefactor (batch-02, issue 02-05).#298: The PR includes theDefine /workflows as portable agentic workflow sourcefeature (batch-02, issue 02-06).#299: The PR adds theAudit and classify legacy promptstask (batch-03, issue 03-01).#300: The PR includes theCreate /skills library indexfeature (batch-03, issue 03-02).#301: The PR adds theCreate lightspeed-frontmatter-audit skillfeature (batch-03, issue 03-03).#302: The PR includes theCreate lightspeed-pr-review skillfeature (batch-03, issue 03-04).#303: The PR adds theCreate lightspeed-label-governance skillfeature (batch-03, issue 03-05).#304: The PR includes theDocument cookbook and favourite skills backlogdocumentation task (batch-03, issue 03-06).#305: The PR adds theCreate lightspeed-github-ops plugin skeletonfeature (batch-04, issue 04-01).#306: The PR includes Copilot plugin manifest compatibility task (batch-04, issue 04-02).#307: The PR adds Codex plugin manifest compatibility task (batch-04, issue 04-03).#308: The PR includes Claude Code plugin manifest compatibility task (batch-04, issue 04-04).#309: The PR adds thePackage selected agent and pilot skillsfeature (batch-04, issue 04-05).#310: The PR includes theWrite plugin installation and update guidedocumentation task (batch-04, issue 04-06).#311: The PR adds theFix invalid JSON schema syntaxmaintenance task (batch-05, issue 05-01).#312: The PR includes theSplit validation from formattingBuild/CI task (batch-05, issue 05-02).#313: The PR adds theAdd validate:structureBuild/CI task (batch-05, issue 05-03).#314: The PR includes theAdd validate:plugins and validate:skillsBuild/CI task (batch-05, issue 05-04).#315: The PR adds theAdd validate:frontmatter and validate:linksBuild/CI task (batch-05, issue 05-05).#316: The PR includes theFix coverage reporting and import side effectstest task (batch-05, issue 05-06).#317: The PR adds theRun local tool smoke tests for pilot plugincompatibility task (batch-06, issue 06-01).#318: The PR includes thePilot plugin in one LightSpeed repofeature (batch-06, issue 06-02).#319: The PR adds theDocument pilot findingsdocumentation task (batch-06, issue 06-03).#320: The PR includes theResearch future plugin pack backlogsresearch task (batch-06, issue 06-04).#321: The PR adds theRelease readiness checklistfor the first pilot milestone (batch-06, issue 06-05).#282: The PR includes the parent epic for planning and skeleton phase (parents/01-epic-planning-control-and-skeleton.md).#283: The PR adds the parent epic for source migration phase (parents/02-epic-portable-source-migration.md).#284: The PR includes the parent epic for core plugin and compatibility phase (parents/03-epic-core-plugin-and-tool-compatibility.md).#285: The PR adds the parent epic for validation, docs, and rollout phase (parents/04-epic-validation-docs-and-rollout.md).
Suggested labels
lang:md, documentation, status:needs-review
🚥 Pre-merge checks | ✅ 4 | ❌ 1
❌ Failed checks (1 warning)
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Description check | The PR description is entirely a template with placeholder sections (Closes #, empty changelog, placeholder risk level) and is not filled out with actual details. | Fill in the PR description with actual linked issues, changelog entries, risk assessment details, and specific testing instructions relevant to this PR. |
✅ Passed checks (4 passed)
| Check name | Status | Explanation |
|---|---|---|
| Title check | ✅ Passed | The title clearly describes the main change: initializing a portable AI plugin restructuring project with planning documentation. |
| Docstring Coverage | ✅ Passed | No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. |
| Linked Issues check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |
✏️ Tip: You can configure your own custom pre-merge checks in the settings.
✨ Finishing Touches
🧪 Generate unit tests (beta)
- Create PR with unit tests
- Commit unit tests in branch
codex/ash-refactor
Tip
💬 Introducing Slack Agent: The best way for teams to turn conversations into code.
Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
- Generate code and open pull requests
- Plan features and break down work
- Investigate incidents and troubleshoot customer tickets together
- Automate recurring tasks and respond to alerts with triggers
- Summarize progress and report instantly
Built for teams:
- Shared memory across your entire org—no repeating context
- Per-thread sandboxes to safely plan and execute work
- Governance built-in—scoped access, auditability, and budget controls
One agent for your entire SDLC. Right inside Slack.
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 @coderabbitai help to get the list of available commands and usage tips.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces a comprehensive project plan for restructuring the repository's AI assets into a portable plugin format, including a detailed Product Requirements Document (PRD) and a structured set of GitHub issue drafts. The review feedback highlights several technical inconsistencies across the new documents, such as mismatched branch prefix rules, missing leading slashes in path examples, incomplete task dependencies, and outdated status for implementation decisions in the PRD.
| ## Labels And Branch Prefixes | ||
|
|
||
| - Parent epics use `status:needs-planning`, `priority:important`, `type:epic`, and relevant area/type labels. | ||
| - AI operations work uses `type:ai-ops` and branch prefix `ai/`. |
There was a problem hiding this comment.
There is an inconsistency between this rule and the actual issue drafts in Batches 03 and 04. While the README specifies the ai/ branch prefix for type:ai-ops work, the drafts consistently use the feat/ prefix in their acceptance criteria. Please update the rule to include feat/ or align the drafts with the ai/ prefix.
Suggested change
| - AI operations work uses `type:ai-ops` and branch prefix `ai/`. | |
| - AI operations work uses type:ai-ops and branch prefix feat/ or ai/. |
| ## Example Code Snippets | ||
|
|
||
| ```text | ||
| .github/schemas/frontmatter.schema.json -> .schemas/frontmatter.schema.json |
There was a problem hiding this comment.
The target path in this example is missing the leading slash. This is inconsistent with the root-relative path convention used in other migration examples (e.g., /instructions, /agents) and the PRD's definition of the /.schemas folder.
Suggested change
| .github/schemas/frontmatter.schema.json -> .schemas/frontmatter.schema.json | |
| .github/schemas/frontmatter.schema.json -> /.schemas/frontmatter.schema.json |
|
|
||
| ## Dependencies | ||
|
|
||
| Depends on the three pilot skill issues and plugin skeleton. |
There was a problem hiding this comment.
This task includes packaging a governance agent (as noted on line 20 and 24), but the dependencies section only lists the pilot skill issues and the plugin skeleton. It should also explicitly depend on the agent migration task (02-04) to ensure the source files are available.
Suggested change
| Depends on the three pilot skill issues and plugin skeleton. | |
| Depends on the three pilot skill issues, the governance agent migration (02-04), and the plugin skeleton. |
| | Manual plugin materialisation vs build script | Manual for pilot, small build script only after repeated duplication appears. | | ||
| | Keep or remove legacy prompts after conversion | Archive first, delete after one release cycle. | | ||
| | Coverage target for the simplified JS layer | Start with meaningful coverage for validators only. | | ||
| | Codex and Claude Code adapter format | Document compatibility notes after Copilot pilot works. | |
There was a problem hiding this comment.
This item is listed as an "Open Implementation Decision" to be resolved before Phase 4. However, the issue drafts 04-03 and 04-04 (which are part of Phase 4) already specify the manifest paths as .codex-plugin/plugin.json and .claude-plugin/plugin.json. This decision appears to be already resolved and should be updated in the PRD to maintain consistency.
Suggested change
| | Codex and Claude Code adapter format | Document compatibility notes after Copilot pilot works. | | |
| | Codex and Claude Code adapter format | Resolved: use .codex-plugin/ and .claude-plugin/ manifests. | |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 20
Note
Due to the large number of review comments, Critical, Major severity comments were prioritized as inline comments.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (4)
.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-05-feature-create-label-governance-skill.md (1)
68-68:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winAdd missing newline at end of file.
Standard practice is to end files with a newline character.
📝 Proposed fix
- [ ] Release notes prepared; monitoring/alerts set. +🤖 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/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-05-feature-create-label-governance-skill.md at line 68, The file 03-05-feature-create-label-governance-skill.md is missing a trailing newline; open that markdown file and add a single newline character at the end of the file (ensure the file ends with "\n") so the file conforms to the standard POSIX/Unix end-of-file newline convention..github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-06-document-cookbook-and-favourite-skills-backlog.md (1)
50-50:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winAdd missing newline at end of file.
Standard practice is to end files with a newline character.
📝 Proposed fix
- [ ] PR uses correct branch prefix `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 @.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-06-document-cookbook-and-favourite-skills-backlog.md at line 50, The file is missing a trailing newline; update the file to end with a single newline character (POSIX-style '\n') so the last line is terminated—ensure the editor or commit adds the newline at EOF and that no extra blank lines are introduced..github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-03-feature-create-frontmatter-audit-skill.md (1)
68-68:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winAdd missing newline at end of file.
Standard practice is to end files with a newline character.
📝 Proposed fix
- [ ] Release notes prepared; monitoring/alerts set. +🤖 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/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-03-feature-create-frontmatter-audit-skill.md at line 68, The file is missing a trailing newline at EOF; open the Markdown document, move to the very end (end-of-file) and append a single newline character so the file ends with '\n' (ensure your editor/save process preserves it), then save and commit the change..github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-04-feature-create-pr-review-skill.md (1)
68-68:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winAdd missing newline at end of file.
Standard practice is to end files with a newline character.
📝 Proposed fix
- [ ] Release notes prepared; monitoring/alerts set. +🤖 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/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-04-feature-create-pr-review-skill.md at line 68, Add a single trailing newline character to the end of the markdown file (ensure the file ends with "\n") so it conforms to POSIX/EditorConfig conventions; open the file "03-04-feature-create-pr-review-skill.md", place the cursor after the final character, press Enter, save, and commit the change.
🟡 Minor comments (4)
.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-04-feature-create-pr-review-skill.md-6-7 (1)
6-7:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winThe referenced GitHub issues
#302and#283do not exist in lightspeedwp/.github. Before merging, either create these issues, update the references to point to existing issues, or explicitly mark them as placeholders (e.g.,TBD,placeholder, or link to tracking documents). This project file is in active work and should not proceed until these references are resolved.🤖 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/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-04-feature-create-pr-review-skill.md around lines 6 - 7, The YAML entries github_issue and github_parent reference non-existent issues (`#302` and `#283`); update these keys in the file to either point to existing issue URLs, create the missing issues and use their URLs, or explicitly mark them as placeholders (e.g., set github_issue: "TBD" and github_parent: "placeholder") so the file no longer references invalid issue links; ensure you edit the github_issue and github_parent values accordingly..github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-06-document-cookbook-and-favourite-skills-backlog.md-6-7 (1)
6-7:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winEnsure referenced GitHub issues
#304and#283exist in lightspeedwp/.github, or mark them as placeholders.The issues referenced on lines 6-7 do not currently exist in the repository. Before merging, either create these issues, update the URLs to existing issues, or explicitly mark them as placeholders to be created later (e.g.,
[PLACEHOLDER] https://github.com/lightspeedwp/.github/issues/304).🤖 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/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-06-document-cookbook-and-favourite-skills-backlog.md around lines 6 - 7, The referenced GitHub issue links assigned to the frontmatter keys github_issue and github_parent point to non-existent issues; either create the corresponding issues in lightspeedwp/.github matching IDs 304 and 283, update the values to point to existing issue URLs, or mark them explicitly as placeholders (e.g., set github_issue = "[PLACEHOLDER] https://github.com/lightspeedwp/.github/issues/304" and similarly for github_parent). Locate the metadata lines containing github_issue and github_parent in the file and apply one of those three fixes so the references are valid or clearly intentional placeholders..github/projects/active/portable-ai-plugin-restructure/issues/children/batch-04-pilot-plugin/04-03-compatibility-add-codex-plugin-manifest.md-42-42 (1)
42-42:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winClarify whether schema validation is required before merge.
The acceptance criterion "Manifest validates against the local Codex plugin schema once available" has the same ambiguity as the Copilot manifest issue: it's unclear whether this is a blocking requirement or can be deferred.
Consider applying the same resolution across all three plugin manifest issues (Copilot, Codex, Claude) for consistency.
🤖 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/portable-ai-plugin-restructure/issues/children/batch-04-pilot-plugin/04-03-compatibility-add-codex-plugin-manifest.md at line 42, Update the acceptance criterion "Manifest validates against the local Codex plugin schema once available" to explicitly state whether schema validation is required before merge or may be deferred; change the line to either a blocking requirement ("Must validate against the local Codex plugin schema before merge") or a non-blocking note ("Validate against the local Codex plugin schema when available; not required to merge"), and apply the same wording decision consistently to the equivalent acceptance criteria for the Copilot and Claude plugin manifest items so all three manifest issues share identical merge requirements..github/projects/active/portable-ai-plugin-restructure/issues/children/batch-04-pilot-plugin/04-02-compatibility-add-copilot-plugin-manifest.md-40-40 (1)
40-40:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winClarify whether schema validation is required before merge.
The acceptance criterion states "Manifest validates against the local plugin schema once available." The "once available" qualifier creates ambiguity: should this checkbox remain unchecked if the schema isn't ready, or can the issue be closed without schema validation?
Consider either:
- Making validation explicitly optional: "Manifest validates against plugin schema (if available)"
- Moving schema validation to a follow-up issue and requiring only manual verification here
- Confirming the schema will be available before this issue is worked (establishing batch-05 dependency)
🤖 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/portable-ai-plugin-restructure/issues/children/batch-04-pilot-plugin/04-02-compatibility-add-copilot-plugin-manifest.md at line 40, Update the ambiguous checklist item "- [ ] Manifest validates against the local plugin schema once available." to explicitly state the desired behavior: either make validation optional ("Manifest validates against plugin schema (if available)"), move schema validation into a follow-up issue and mark this item as "manual verification only" for now, or document that the schema will be available before work begins (establishing a dependency). Pick one of these options, change the checklist text accordingly, and if choosing the follow-up route create a new issue referencing the manifest validation requirement and link it from this checklist item.
🧹 Nitpick comments (6)
.github/projects/active/portable-ai-plugin-restructure/issues/README.md (1)
33-41: 🏗️ Heavy liftAlign issue draft filenames with the required project artefact naming convention.
The listed draft files (Line 35–Line 41) use batch/ordinal naming, which conflicts with the required
{project-slug}-{purpose}-{date}.{ext}format. This will make standards enforcement and archival automation inconsistent across the project docs.As per coding guidelines, "
.github/projects/**/*.md: Use naming convention{project-slug}-{purpose}-{date}.{ext}for project artefacts."🤖 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/portable-ai-plugin-restructure/issues/README.md around lines 33 - 41, The batch markdown filenames use batch/ordinal folder names (e.g., children/batch-00-planning-control/, children/batch-01-skeleton-boundary/, children/batch-02-portable-migration/, etc.) which violate the required `{project-slug}-{purpose}-{date}.{ext}` convention; rename each folder/file to follow that pattern (for example convert children/batch-00-planning-control/ into something like portable-ai-plugin-restructure-planning-YYYYMMDD.md or the equivalent project-slug-purpose-date form), update any links or references to those folders/files in the repo, and ensure the new names are applied consistently across the listed entries (batch-00 through batch-06)..github/projects/active/portable-ai-plugin-restructure/portable-ai-plugin-restructure-prd-2026-05-14.md (1)
32-47: ⚡ Quick winReformat the executive summary using the required Compressed Decision Record format.
The section starting at Line 32 is currently prose; it should include a CDR entry (
Decision | Rationale | Impact | Review) to match the project documentation standard.As per coding guidelines, "Use Compressed Decision Record format for pull request summaries and executive summaries:
Decision: [X] | Rationale: [Y] | Impact: [Z] | Review: [Date]."🤖 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/portable-ai-plugin-restructure/portable-ai-plugin-restructure-prd-2026-05-14.md around lines 32 - 47, Replace the current prose Executive Summary with a Compressed Decision Record entry in the required format: start the section with a single-line CDR "Decision: [X] | Rationale: [Y] | Impact: [Z] | Review: [Date]" that succinctly captures the proposal to split .github governance from portable AI assets, then add one or two short supporting sentences if needed; update the header that begins "Executive Summary" and the paragraph that describes the two concerns so they are summarized in the CDR line and a brief one-line rationale/impact pair, ensuring the Decision, Rationale, Impact and Review tokens appear exactly as specified..github/projects/active/portable-ai-plugin-restructure/issues/children/batch-00-planning-control/00-03-task-create-milestone-label-and-issue-linking-plan.md (2)
57-57: 💤 Low valueAdd final newline for POSIX compliance.
The file ends without a final newline. POSIX standards and many coding conventions expect text files to end with a newline character.
Applies to all 5 files in this review (ending at lines 57, 58, 55, 71, and 73 respectively).
🤖 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/portable-ai-plugin-restructure/issues/children/batch-00-planning-control/00-03-task-create-milestone-label-and-issue-linking-plan.md at line 57, Add a final newline character at the end of the file to satisfy POSIX/text-file conventions: open 00-03-task-create-milestone-label-and-issue-linking-plan.md (and the other four files flagged in this review) and ensure the last line ends with a newline character so the file terminates with '\n'.
1-57: ⚖️ Poor tradeoffFile naming doesn't follow the prescribed project artefact convention.
According to the coding guidelines, files matching
.github/projects/**/*.mdshould use the naming convention{project-slug}-{purpose}-{date}.{ext}. This file (and the four others in this review) uses a batch-numbered pattern like00-03-task-create-milestone-label-and-issue-linking-plan.mdinstead of something likeportable-ai-plugin-restructure-milestone-label-plan-2026-05-15.md.The current batch numbering scheme (
00-03,01-01, etc.) provides clear sequential ordering that supports the phased delivery model. Consider either:
- Renaming to follow the guideline using dates to encode batch order
- Proposing a guideline refinement for issue draft organization that accommodates batch-based sequencing
Applies to all 5 files in this review:
00-03-task-create-milestone-label-and-issue-linking-plan.md01-01-task-create-target-folder-skeleton.md01-02-document-folder-ownership-indexes.md01-03-refactor-file-organisation-boundary.md01-04-refactor-repo-local-copilot-instructions.mdAs per coding guidelines: "Use naming convention
{project-slug}-{purpose}-{date}.{ext}for project artefacts".🤖 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/portable-ai-plugin-restructure/issues/children/batch-00-planning-control/00-03-task-create-milestone-label-and-issue-linking-plan.md around lines 1 - 57, Rename the five project artefact files to follow the required convention {project-slug}-{purpose}-{date}.md (e.g., portable-ai-plugin-restructure-milestone-label-plan-2026-05-15.md) instead of the current batch-numbered names (00-03-task-create-milestone-label-and-issue-linking-plan.md, 01-01-task-create-target-folder-skeleton.md, 01-02-document-folder-ownership-indexes.md, 01-03-refactor-file-organisation-boundary.md, 01-04-refactor-repo-local-copilot-instructions.md); update any internal references or links that point to these filenames (search for those exact filenames) and ensure frontmatter fields remain intact after renaming, or alternatively add a brief proposal to the repo guidelines documenting acceptance of the batch-numbering scheme and cite these five files as examples if you choose to change the naming policy instead..github/projects/active/portable-ai-plugin-restructure/issues/children/batch-05-validation-reset/05-02-buildci-split-validation-from-formatting.md (1)
39-39: ⚡ Quick winConsider adding explicit dependency on issue 05-01.
The Additional Context (line 35) mentions that
validate:json:schemasis "currently mutating and failing." Issue 05-01 fixes the syntax errors causing the failures. While the batch ordering implies 05-01 should complete first, explicitly documenting this dependency in the "References" or a "Dependencies" section would make the relationship clearer and help with work sequencing.🤖 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/portable-ai-plugin-restructure/issues/children/batch-05-validation-reset/05-02-buildci-split-validation-from-formatting.md at line 39, Add an explicit dependency on issue 05-01 for the batch item that touches validate:json:schemas by updating the “References” or adding a new “Dependencies” section (or appending to Active PRD section 16.2, Required New Commands) to state that validate:json:schemas depends on issue 05-01 being merged first; mention both the issue id "05-01" and the command "validate:json:schemas" so sequencing is clear..github/projects/active/portable-ai-plugin-restructure/issues/children/batch-06-pilot-release/06-05-release-readiness-checklist.md (1)
1-50: Consider clarifying naming convention for issue templates.The file name
06-05-release-readiness-checklist.mddoesn't match the guideline pattern{project-slug}-{purpose}-{date}.{ext}. However, all 30+ issue template files in this project follow the{batch}-{number}-{description}.mdpattern, suggesting an intentional organizational structure.The coding guideline for
.github/projects/**/*.mdspecifies the{project-slug}-{purpose}-{date}.{ext}pattern for "project artefacts," but it's unclear whether issue templates fall under this category or if they're exempt due to their special role in structured issue creation.Consider either:
- Updating the guideline to explicitly exclude issue templates from the naming pattern (if intentional), or
- Renaming issue templates to follow the guideline (e.g.,
portable-ai-plugin-restructure-release-readiness-2026-05-14.md)As per coding guidelines, "
.github/projects/**/*.md: Use naming convention{project-slug}-{purpose}-{date}.{ext}for project artefacts (e.g.,checkout-refactor-tasks-2025-12-11.md,checkout-refactor-context-pack.md)."🤖 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/portable-ai-plugin-restructure/issues/children/batch-06-pilot-release/06-05-release-readiness-checklist.md around lines 1 - 50, The issue notes that the file .github/projects/.../06-05-release-readiness-checklist.md violates the project's `{project-slug}-{purpose}-{date}.{ext}` naming guideline; either explicitly exempt issue templates in the guideline (update the `.github/projects/**/*.md` naming rule text to state that issue templates may use the existing `{batch}-{number}-{description}.md` pattern) or rename the file to comply (e.g., portable-ai-plugin-restructure-release-readiness-2026-05-14.md) and update any tooling/docs that list project artefacts to reference the chosen convention; ensure the change is applied consistently across other issue template files and that the guideline example(s) reflect the final decision.
🤖 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/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-01-audit-classify-github-native-files.md:
- Around line 1-8: The filename 02-01-audit-classify-github-native-files.md
doesn't follow the required {project-slug}-{purpose}-{date}.md convention;
rename the file to match that pattern (e.g.,
audit-classify-github-native-files-YYYY-MM-DD.md) and update any references to
it (including the frontmatter title/name if they include the old slug) so they
point to the new filename; ensure the new slug is used consistently in the
YAML/frontmatter (fields like name and title) and update links in other project
markdown that reference 02-01-audit-classify-github-native-files.md.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-02-maintenance-clean-stale-path-references.md:
- Around line 1-8: The file name
"02-02-maintenance-clean-stale-path-references.md" doesn't follow the required
`{project-slug}-{purpose}-{date}.md` pattern; rename the file to remove the
numeric prefix and adopt the convention (for example
`portable-ai-plugin-restructure-maintenance-2026-05-15.md`), ensuring the new
slug reflects the project (`portable-ai-plugin-restructure`) and purpose
(`maintenance`) plus a date; also verify the YAML front-matter `name`/`title`
values remain accurate after renaming.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-03-refactor-migrate-portable-instructions.md:
- Around line 1-8: The filename
.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-03-refactor-migrate-portable-instructions.md
does not follow the required `{project-slug}-{purpose}-{date}.md` convention;
rename the file to that pattern (e.g.,
portable-ai-plugin-restructure-refactor-migrate-instructions-YYYYMMDD.md using
the current date) and update all inbound links and references (search repo for
the old filename and update in any PROJECT files, README, issue metadata like
github_parent/github_issue fields if they reference it) so no broken links
remain; ensure the new filename is reflected in any project manifests under
.github/projects and that link targets use the new name.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-04-refactor-migrate-portable-agent-specs.md:
- Around line 1-8: The file name
".github/projects/active/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-04-refactor-migrate-portable-agent-specs.md"
does not follow the required `{project-slug}-{purpose}-{date}.md` naming
convention; rename this file to follow that pattern (for example
`portable-ai-plugin-restructure-refactor-migrate-agent-specs-YYYY-MM-DD.md`) and
update any references to it (README, project index, issue links, or other
markdown that imports or links this file) so they point to the new filename;
ensure the new slug and purpose accurately reflect the project and task and
include a date in ISO format to satisfy `.github/projects/**/*.md` guidelines.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-05-refactor-move-active-schemas-to-root-schemas.md:
- Around line 1-8: The file named
".github/projects/active/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-05-refactor-move-active-schemas-to-root-schemas.md"
doesn't follow the required artifact filename convention; rename it to use the
pattern {project-slug}-{purpose}-{date}.md (e.g.,
portable-ai-plugin-restructure-refactor-move-active-schemas-2026-05-15.md) so it
complies with the `.github/projects/**/*.md` guideline; update any references to
the old filename in docs or links (search for
"02-05-refactor-move-active-schemas-to-root-schemas.md") to the new filename.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-06-feature-define-portable-workflows-source.md:
- Around line 1-8: The file name
`.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-06-feature-define-portable-workflows-source.md`
does not follow the required `{project-slug}-{purpose}-{date}.md` pattern;
rename the file to match that convention (e.g., use the project slug
`portable-ai-plugin-restructure`, a short purpose like
`feature-define-workflows`, and a date) and update any references to this file
if present; ensure the frontmatter `title: "[Feature] Define `/workflows` as
portable agentic workflow source"` remains unchanged.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-01-audit-classify-legacy-prompts.md:
- Around line 1-8: The file currently titled "[Audit] Classify legacy prompts as
skill, cookbook, archive, or delete" must be renamed to follow the project
artifact convention {project-slug}-{purpose}-{date}.md; rename the file to use
the project slug portable-ai-plugin-restructure, a short purpose token like
"audit" (or "audit-classify-prompts"), and an ISO date (YYYY-MM-DD) so the
filename becomes portable-ai-plugin-restructure-audit-YYYY-MM-DD.md (update any
internal references if present).
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-02-feature-create-skills-library-index.md:
- Around line 1-8: The frontmatter/title file "[Feature] Create the portable
`/skills` library index" currently uses a nonstandard filename; rename the
markdown to follow the project artifact naming convention
`{project-slug}-{purpose}-{date}.md` (e.g., use a slugified project name,
purpose like "feature" or "proposal", and an ISO-like date), update any internal
references if present, and ensure the frontmatter fields
(name/title/github_issue) remain correct after renaming so the file conforms to
`.github/projects/**/*.md` guidelines.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-05-validation-reset/05-03-buildci-add-validate-structure.md:
- Around line 1-8: The markdown file 05-03-buildci-add-validate-structure.md
does not follow the required artifact naming convention; rename the file to the
`{project-slug}-{purpose}-{date}.md` format (e.g., use the project slug from the
front-matter "name" or a short slug like
build-ci-validate-structure-YYYY-MM-DD.md) and update any internal front-matter
fields if needed (check the front-matter keys `name`, `title`, and
`github_issue` in the diff to ensure they still match the new filename and
intent).
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-05-validation-reset/05-04-buildci-add-validate-plugins-and-skills.md:
- Around line 1-8: The file .github/projects/... currently named
"05-04-buildci-add-validate-plugins-and-skills.md" does not follow the required
project artefact naming convention; rename it to the
`{project-slug}-{purpose}-{date}.md` format (for example use the project slug
from the frontmatter "build-ci" or "build-and-ci", a short purpose like
"validate-plugins-skills", and an ISO date like "2026-05-15") so the filename
becomes e.g. "build-ci-validate-plugins-skills-2026-05-15.md"; update any
references if needed and ensure the YAML frontmatter (name/title) remains
unchanged.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-05-validation-reset/05-05-buildci-add-validate-frontmatter-and-links.md:
- Around line 1-8: The file name
05-05-buildci-add-validate-frontmatter-and-links.md doesn't follow the required
`{project-slug}-{purpose}-{date}.{ext}` convention; rename the artifact to match
that pattern (include a clear project-slug like "build-ci" or "build-and-ci", a
short purpose such as "validate-frontmatter-links", and an ISO date) — e.g.,
change "05-05-buildci-add-validate-frontmatter-and-links.md" to
"build-ci-validate-frontmatter-links-2026-05-15.md" (or similar) so it conforms
with the `.github/projects/**/*.md` naming rule referenced in the guidelines.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-05-validation-reset/05-06-test-fix-coverage-reporting-and-import-side-effects.md:
- Around line 1-8: The file name
05-06-test-fix-coverage-reporting-and-import-side-effects.md does not follow the
required project artefact naming convention; rename it to the
`{project-slug}-{purpose}-{date}.md` pattern (for example:
test-coverage-fix-2026-05-15.md or
portable-ai-plugin-test-coverage-2026-05-15.md) so it matches the
`.github/projects/**/*.md` guideline; ensure the chosen project-slug reflects
the project (e.g., portable-ai-plugin or test-coverage) and include an ISO date
suffix.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-06-pilot-release/06-01-compatibility-run-local-tool-smoke-tests.md:
- Around line 1-8: The file name
06-01-compatibility-run-local-tool-smoke-tests.md doesn't follow the required
project artifact naming convention; rename the file to the
`{project-slug}-{purpose}-{date}.md` pattern (for example use a slug like
"compatibility", a purpose like "run-local-tool-smoke-tests" and a YYYY-MM-DD
date), update any references if needed, and ensure the new name replaces the
existing 06-01-compatibility-run-local-tool-smoke-tests.md entry in the
.github/projects tree so it conforms to the `.github/projects/**/*.md` naming
guideline.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-06-pilot-release/06-02-feature-pilot-plugin-in-one-lightspeed-repo.md:
- Around line 1-8: The file 06-02-feature-pilot-plugin-in-one-lightspeed-repo.md
must be renamed to follow the project artefact naming convention
`{project-slug}-{purpose}-{date}.{ext}`; pick a concise project-slug like
lightspeed-github-ops, a purpose such as feature-pilot-plugin, and append an ISO
date (e.g., 2026-05-15) so the new filename becomes something like
lightspeed-github-ops-feature-pilot-plugin-2026-05-15.md, then update any
references (if any) to the old filename in related metadata or links.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-06-pilot-release/06-03-document-pilot-findings.md:
- Around line 1-8: The filename 06-03-document-pilot-findings.md doesn't follow
the required `{project-slug}-{purpose}-{date}.{ext}` convention; rename the
artefact to use the project slug (portable-ai-plugin-restructure), a clear
purpose token (e.g., document-pilot-findings), and an ISO date suffix
(YYYY-MM-DD) so it becomes
portable-ai-plugin-restructure-document-pilot-findings-<date>.md, and update any
internal links or references that point to 06-03-document-pilot-findings.md to
the new filename.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-06-pilot-release/06-04-research-create-future-plugin-pack-backlogs.md:
- Around line 1-8: Rename the artifact file so it follows the required
{project-slug}-{purpose}-{date}.{ext} convention; replace the current filename
"06-04-research-create-future-plugin-pack-backlogs.md" with a name like
"<project-slug>-research-YYYY-MM-DD.md" (e.g.,
"portable-ai-plugin-restructure-research-2026-05-15.md"), ensuring the project
slug matches the repository/project and the date is the creation or milestone
date; update any references to the old filename if present.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/parents/01-epic-planning-control-and-skeleton.md:
- Line 5: The labels array currently lists status:needs-planning,
priority:important, area:core, type:ai-ops but is missing the epic label; update
the labels array to include "type:epic" (e.g., labels: [status:needs-planning,
priority:important, area:core, type:ai-ops, type:epic]) so the parent issue
retains epic-level automation and filtering.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/parents/02-epic-portable-source-migration.md:
- Line 5: The labels array on the parent epic is missing the epic type tag;
update the labels line (the labels: [...] entry) to include "type:epic" in
addition to the existing labels so the array becomes labels:
[status:needs-planning, priority:important, area:core, type:ai-ops, type:epic],
ensuring automation and epic-specific triage will pick up this parent epic.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/parents/03-epic-core-plugin-and-tool-compatibility.md:
- Line 5: The labels list on the epic parent entry is missing the explicit epic
classification; update the labels array to include type:epic (e.g., change
labels: [status:needs-planning, priority:important, area:core, type:ai-ops,
type:compatibility] to include type:epic) so the item is correctly recognized as
an epic; modify the labels declaration in the same block where labels are
defined to add "type:epic" alongside the existing labels.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/parents/04-epic-validation-docs-and-rollout.md:
- Line 5: Add the missing epic type to the parent issue labels by updating the
labels array (labels: [...]) to include type:epic alongside the existing entries
(status:needs-planning, priority:important, area:core, area:ci,
area:documentation) so epic-level views and automations recognize this parent
issue.
---
Outside diff comments:
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-03-feature-create-frontmatter-audit-skill.md:
- Line 68: The file is missing a trailing newline at EOF; open the Markdown
document, move to the very end (end-of-file) and append a single newline
character so the file ends with '\n' (ensure your editor/save process preserves
it), then save and commit the change.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-04-feature-create-pr-review-skill.md:
- Line 68: Add a single trailing newline character to the end of the markdown
file (ensure the file ends with "\n") so it conforms to POSIX/EditorConfig
conventions; open the file "03-04-feature-create-pr-review-skill.md", place the
cursor after the final character, press Enter, save, and commit the change.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-05-feature-create-label-governance-skill.md:
- Line 68: The file 03-05-feature-create-label-governance-skill.md is missing a
trailing newline; open that markdown file and add a single newline character at
the end of the file (ensure the file ends with "\n") so the file conforms to the
standard POSIX/Unix end-of-file newline convention.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-06-document-cookbook-and-favourite-skills-backlog.md:
- Line 50: The file is missing a trailing newline; update the file to end with a
single newline character (POSIX-style '\n') so the last line is
terminated—ensure the editor or commit adds the newline at EOF and that no extra
blank lines are introduced.
---
Minor comments:
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-04-feature-create-pr-review-skill.md:
- Around line 6-7: The YAML entries github_issue and github_parent reference
non-existent issues (`#302` and `#283`); update these keys in the file to either
point to existing issue URLs, create the missing issues and use their URLs, or
explicitly mark them as placeholders (e.g., set github_issue: "TBD" and
github_parent: "placeholder") so the file no longer references invalid issue
links; ensure you edit the github_issue and github_parent values accordingly.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-06-document-cookbook-and-favourite-skills-backlog.md:
- Around line 6-7: The referenced GitHub issue links assigned to the frontmatter
keys github_issue and github_parent point to non-existent issues; either create
the corresponding issues in lightspeedwp/.github matching IDs 304 and 283,
update the values to point to existing issue URLs, or mark them explicitly as
placeholders (e.g., set github_issue = "[PLACEHOLDER]
https://github.com/lightspeedwp/.github/issues/304" and similarly for
github_parent). Locate the metadata lines containing github_issue and
github_parent in the file and apply one of those three fixes so the references
are valid or clearly intentional placeholders.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-04-pilot-plugin/04-02-compatibility-add-copilot-plugin-manifest.md:
- Line 40: Update the ambiguous checklist item "- [ ] Manifest validates against
the local plugin schema once available." to explicitly state the desired
behavior: either make validation optional ("Manifest validates against plugin
schema (if available)"), move schema validation into a follow-up issue and mark
this item as "manual verification only" for now, or document that the schema
will be available before work begins (establishing a dependency). Pick one of
these options, change the checklist text accordingly, and if choosing the
follow-up route create a new issue referencing the manifest validation
requirement and link it from this checklist item.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-04-pilot-plugin/04-03-compatibility-add-codex-plugin-manifest.md:
- Line 42: Update the acceptance criterion "Manifest validates against the local
Codex plugin schema once available" to explicitly state whether schema
validation is required before merge or may be deferred; change the line to
either a blocking requirement ("Must validate against the local Codex plugin
schema before merge") or a non-blocking note ("Validate against the local Codex
plugin schema when available; not required to merge"), and apply the same
wording decision consistently to the equivalent acceptance criteria for the
Copilot and Claude plugin manifest items so all three manifest issues share
identical merge requirements.
---
Nitpick comments:
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-00-planning-control/00-03-task-create-milestone-label-and-issue-linking-plan.md:
- Line 57: Add a final newline character at the end of the file to satisfy
POSIX/text-file conventions: open
00-03-task-create-milestone-label-and-issue-linking-plan.md (and the other four
files flagged in this review) and ensure the last line ends with a newline
character so the file terminates with '\n'.
- Around line 1-57: Rename the five project artefact files to follow the
required convention {project-slug}-{purpose}-{date}.md (e.g.,
portable-ai-plugin-restructure-milestone-label-plan-2026-05-15.md) instead of
the current batch-numbered names
(00-03-task-create-milestone-label-and-issue-linking-plan.md,
01-01-task-create-target-folder-skeleton.md,
01-02-document-folder-ownership-indexes.md,
01-03-refactor-file-organisation-boundary.md,
01-04-refactor-repo-local-copilot-instructions.md); update any internal
references or links that point to these filenames (search for those exact
filenames) and ensure frontmatter fields remain intact after renaming, or
alternatively add a brief proposal to the repo guidelines documenting acceptance
of the batch-numbering scheme and cite these five files as examples if you
choose to change the naming policy instead.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-05-validation-reset/05-02-buildci-split-validation-from-formatting.md:
- Line 39: Add an explicit dependency on issue 05-01 for the batch item that
touches validate:json:schemas by updating the “References” or adding a new
“Dependencies” section (or appending to Active PRD section 16.2, Required New
Commands) to state that validate:json:schemas depends on issue 05-01 being
merged first; mention both the issue id "05-01" and the command
"validate:json:schemas" so sequencing is clear.
In
@.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-06-pilot-release/06-05-release-readiness-checklist.md:
- Around line 1-50: The issue notes that the file
.github/projects/.../06-05-release-readiness-checklist.md violates the project's
`{project-slug}-{purpose}-{date}.{ext}` naming guideline; either explicitly
exempt issue templates in the guideline (update the `.github/projects/**/*.md`
naming rule text to state that issue templates may use the existing
`{batch}-{number}-{description}.md` pattern) or rename the file to comply (e.g.,
portable-ai-plugin-restructure-release-readiness-2026-05-14.md) and update any
tooling/docs that list project artefacts to reference the chosen convention;
ensure the change is applied consistently across other issue template files and
that the guideline example(s) reflect the final decision.
In @.github/projects/active/portable-ai-plugin-restructure/issues/README.md:
- Around line 33-41: The batch markdown filenames use batch/ordinal folder names
(e.g., children/batch-00-planning-control/,
children/batch-01-skeleton-boundary/, children/batch-02-portable-migration/,
etc.) which violate the required `{project-slug}-{purpose}-{date}.{ext}`
convention; rename each folder/file to follow that pattern (for example convert
children/batch-00-planning-control/ into something like
portable-ai-plugin-restructure-planning-YYYYMMDD.md or the equivalent
project-slug-purpose-date form), update any links or references to those
folders/files in the repo, and ensure the new names are applied consistently
across the listed entries (batch-00 through batch-06).
In
@.github/projects/active/portable-ai-plugin-restructure/portable-ai-plugin-restructure-prd-2026-05-14.md:
- Around line 32-47: Replace the current prose Executive Summary with a
Compressed Decision Record entry in the required format: start the section with
a single-line CDR "Decision: [X] | Rationale: [Y] | Impact: [Z] | Review:
[Date]" that succinctly captures the proposal to split .github governance from
portable AI assets, then add one or two short supporting sentences if needed;
update the header that begins "Executive Summary" and the paragraph that
describes the two concerns so they are summarized in the CDR line and a brief
one-line rationale/impact pair, ensuring the Decision, Rationale, Impact and
Review tokens appear exactly as specified.
🪄 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: Path: .coderabbit.yml
Review profile: CHILL
Plan: Pro
Run ID: c0fbf6f2-9fad-410d-8b10-e86fe1390ea1
📒 Files selected for processing (42)
.github/projects/active/portable-ai-plugin-restructure/issues/README.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-00-planning-control/00-01-audit-current-asset-inventory-and-migration-map.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-00-planning-control/00-02-audit-baseline-validation-and-dependency-state.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-00-planning-control/00-03-task-create-milestone-label-and-issue-linking-plan.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-01-skeleton-boundary/01-01-task-create-target-folder-skeleton.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-01-skeleton-boundary/01-02-document-folder-ownership-indexes.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-01-skeleton-boundary/01-03-refactor-file-organisation-boundary.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-01-skeleton-boundary/01-04-refactor-repo-local-copilot-instructions.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-01-audit-classify-github-native-files.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-02-maintenance-clean-stale-path-references.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-03-refactor-migrate-portable-instructions.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-04-refactor-migrate-portable-agent-specs.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-05-refactor-move-active-schemas-to-root-schemas.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-06-feature-define-portable-workflows-source.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-01-audit-classify-legacy-prompts.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-02-feature-create-skills-library-index.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-03-feature-create-frontmatter-audit-skill.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-04-feature-create-pr-review-skill.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-05-feature-create-label-governance-skill.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-03-skills-cookbook/03-06-document-cookbook-and-favourite-skills-backlog.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-04-pilot-plugin/04-01-feature-create-lightspeed-github-ops-plugin-skeleton.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-04-pilot-plugin/04-02-compatibility-add-copilot-plugin-manifest.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-04-pilot-plugin/04-03-compatibility-add-codex-plugin-manifest.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-04-pilot-plugin/04-04-compatibility-add-claude-plugin-manifest.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-04-pilot-plugin/04-05-feature-package-pilot-agent-and-skills.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-04-pilot-plugin/04-06-document-plugin-installation-guide.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-05-validation-reset/05-01-maintenance-fix-invalid-json-schema-syntax.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-05-validation-reset/05-02-buildci-split-validation-from-formatting.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-05-validation-reset/05-03-buildci-add-validate-structure.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-05-validation-reset/05-04-buildci-add-validate-plugins-and-skills.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-05-validation-reset/05-05-buildci-add-validate-frontmatter-and-links.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-05-validation-reset/05-06-test-fix-coverage-reporting-and-import-side-effects.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-06-pilot-release/06-01-compatibility-run-local-tool-smoke-tests.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-06-pilot-release/06-02-feature-pilot-plugin-in-one-lightspeed-repo.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-06-pilot-release/06-03-document-pilot-findings.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-06-pilot-release/06-04-research-create-future-plugin-pack-backlogs.md.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-06-pilot-release/06-05-release-readiness-checklist.md.github/projects/active/portable-ai-plugin-restructure/issues/parents/01-epic-planning-control-and-skeleton.md.github/projects/active/portable-ai-plugin-restructure/issues/parents/02-epic-portable-source-migration.md.github/projects/active/portable-ai-plugin-restructure/issues/parents/03-epic-core-plugin-and-tool-compatibility.md.github/projects/active/portable-ai-plugin-restructure/issues/parents/04-epic-validation-docs-and-rollout.md.github/projects/active/portable-ai-plugin-restructure/portable-ai-plugin-restructure-prd-2026-05-14.md
Comment on lines
+1
to
+8
| --- | ||
| name: "Audit" | ||
| about: "Propose, conduct, or document a security, accessibility, code, or process audit." | ||
| title: "[Audit] Classify GitHub-native files that must remain in `.github`" | ||
| labels: [status:needs-audit, priority:important, area:core] | ||
| github_issue: "https://github.com/lightspeedwp/.github/issues/293" | ||
| github_parent: "https://github.com/lightspeedwp/.github/issues/283" | ||
| --- |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major | ⚡ Quick win
Rename this project artifact to match the required filename pattern.
The current filename (02-01-audit-classify-github-native-files.md) does not follow the required {project-slug}-{purpose}-{date}.md convention for project markdown artifacts. Please rename it (and references) to the mandated pattern.
As per coding guidelines .github/projects/**/*.md: “Use naming convention {project-slug}-{purpose}-{date}.{ext} for project artefacts (e.g., checkout-refactor-tasks-2025-12-11.md, checkout-refactor-context-pack.md).`
🤖 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/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-01-audit-classify-github-native-files.md
around lines 1 - 8, The filename 02-01-audit-classify-github-native-files.md
doesn't follow the required {project-slug}-{purpose}-{date}.md convention;
rename the file to match that pattern (e.g.,
audit-classify-github-native-files-YYYY-MM-DD.md) and update any references to
it (including the frontmatter title/name if they include the old slug) so they
point to the new filename; ensure the new slug is used consistently in the
YAML/frontmatter (fields like name and title) and update links in other project
markdown that reference 02-01-audit-classify-github-native-files.md.
Comment on lines
+1
to
+8
| --- | ||
| name: "Maintenance" | ||
| about: "Propose routine hygiene, dependency bumps, CI updates, or other maintenance tasks" | ||
| title: "[Maintenance] Clean stale path references before migration" | ||
| labels: [status:needs-triage, priority:normal, type:maintenance] | ||
| github_issue: "https://github.com/lightspeedwp/.github/issues/294" | ||
| github_parent: "https://github.com/lightspeedwp/.github/issues/283" | ||
| --- |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major | ⚡ Quick win
Filename should follow {project-slug}-{purpose}-{date}.md.
Please rename this file to the required project-artifact naming format; the numeric-prefixed filename does not comply.
As per coding guidelines .github/projects/**/*.md: “Use naming convention {project-slug}-{purpose}-{date}.{ext} for project artefacts.”
🤖 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/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-02-maintenance-clean-stale-path-references.md
around lines 1 - 8, The file name
"02-02-maintenance-clean-stale-path-references.md" doesn't follow the required
`{project-slug}-{purpose}-{date}.md` pattern; rename the file to remove the
numeric prefix and adopt the convention (for example
`portable-ai-plugin-restructure-maintenance-2026-05-15.md`), ensuring the new
slug reflects the project (`portable-ai-plugin-restructure`) and purpose
(`maintenance`) plus a date; also verify the YAML front-matter `name`/`title`
values remain accurate after renaming.
Comment on lines
+1
to
+8
| --- | ||
| name: "Code Refactor" | ||
| about: "Request or propose a code refactoring or review to improve code quality, maintainability, and consistency." | ||
| title: "[Refactor] Migrate reusable instructions to `/instructions`" | ||
| labels: [status:needs-review, priority:important, type:ai-ops, area:core] | ||
| github_issue: "https://github.com/lightspeedwp/.github/issues/295" | ||
| github_parent: "https://github.com/lightspeedwp/.github/issues/283" | ||
| --- |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major | ⚡ Quick win
Apply the repository artifact naming convention to this file.
This filename is not in {project-slug}-{purpose}-{date}.md format. Please rename it accordingly and update inbound links.
As per coding guidelines .github/projects/**/*.md: “Use naming convention {project-slug}-{purpose}-{date}.{ext} for project artefacts.”
🤖 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/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-03-refactor-migrate-portable-instructions.md
around lines 1 - 8, The filename
.github/projects/active/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-03-refactor-migrate-portable-instructions.md
does not follow the required `{project-slug}-{purpose}-{date}.md` convention;
rename the file to that pattern (e.g.,
portable-ai-plugin-restructure-refactor-migrate-instructions-YYYYMMDD.md using
the current date) and update all inbound links and references (search repo for
the old filename and update in any PROJECT files, README, issue metadata like
github_parent/github_issue fields if they reference it) so no broken links
remain; ensure the new filename is reflected in any project manifests under
.github/projects and that link targets use the new name.
Comment on lines
+1
to
+8
| --- | ||
| name: "Code Refactor" | ||
| about: "Request or propose a code refactoring or review to improve code quality, maintainability, and consistency." | ||
| title: "[Refactor] Migrate reusable agent specs to `/agents`" | ||
| labels: [status:needs-review, priority:important, type:ai-ops, area:core] | ||
| github_issue: "https://github.com/lightspeedwp/.github/issues/296" | ||
| github_parent: "https://github.com/lightspeedwp/.github/issues/283" | ||
| --- |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major | ⚡ Quick win
This file name is out of spec for project markdown artifacts.
Please rename to {project-slug}-{purpose}-{date}.md and adjust references.
As per coding guidelines .github/projects/**/*.md: “Use naming convention {project-slug}-{purpose}-{date}.{ext} for project artefacts.”
🤖 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/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-04-refactor-migrate-portable-agent-specs.md
around lines 1 - 8, The file name
".github/projects/active/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-04-refactor-migrate-portable-agent-specs.md"
does not follow the required `{project-slug}-{purpose}-{date}.md` naming
convention; rename this file to follow that pattern (for example
`portable-ai-plugin-restructure-refactor-migrate-agent-specs-YYYY-MM-DD.md`) and
update any references to it (README, project index, issue links, or other
markdown that imports or links this file) so they point to the new filename;
ensure the new slug and purpose accurately reflect the project and task and
include a date in ISO format to satisfy `.github/projects/**/*.md` guidelines.
Comment on lines
+1
to
+8
| --- | ||
| name: "Code Refactor" | ||
| about: "Request or propose a code refactoring or review to improve code quality, maintainability, and consistency." | ||
| title: "[Refactor] Move active portable schemas to `/.schemas`" | ||
| labels: [status:needs-review, priority:important, area:core, area:ci] | ||
| github_issue: "https://github.com/lightspeedwp/.github/issues/297" | ||
| github_parent: "https://github.com/lightspeedwp/.github/issues/283" | ||
| --- |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major | ⚡ Quick win
Rename needed to comply with artifact filename convention.
Current filename is not in {project-slug}-{purpose}-{date}.md format.
As per coding guidelines .github/projects/**/*.md: “Use naming convention {project-slug}-{purpose}-{date}.{ext} for project artefacts.”
🤖 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/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-05-refactor-move-active-schemas-to-root-schemas.md
around lines 1 - 8, The file named
".github/projects/active/portable-ai-plugin-restructure/issues/children/batch-02-portable-migration/02-05-refactor-move-active-schemas-to-root-schemas.md"
doesn't follow the required artifact filename convention; rename it to use the
pattern {project-slug}-{purpose}-{date}.md (e.g.,
portable-ai-plugin-restructure-refactor-move-active-schemas-2026-05-15.md) so it
complies with the `.github/projects/**/*.md` guideline; update any references to
the old filename in docs or links (search for
"02-05-refactor-move-active-schemas-to-root-schemas.md") to the new filename.
Comment on lines
+1
to
+8
| --- | ||
| name: "Research" | ||
| about: "Propose or document technical research, investigation, or exploratory work." | ||
| title: "[Research] Create future plugin pack backlogs" | ||
| labels: [status:needs-review, priority:normal, type:ai-ops] | ||
| github_issue: "https://github.com/lightspeedwp/.github/issues/320" | ||
| github_parent: "https://github.com/lightspeedwp/.github/issues/285" | ||
| --- |
Contributor
There was a problem hiding this comment.
Rename file to match required project artefact naming convention.
The current filename (06-04-research-create-future-plugin-pack-backlogs.md) does not follow the required {project-slug}-{purpose}-{date}.{ext} format for .github/projects/**/*.md artefacts.
As per coding guidelines, ".github/projects/**/*.md: Use naming convention {project-slug}-{purpose}-{date}.{ext} for project artefacts (e.g., checkout-refactor-tasks-2025-12-11.md, checkout-refactor-context-pack.md)."
🤖 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/portable-ai-plugin-restructure/issues/children/batch-06-pilot-release/06-04-research-create-future-plugin-pack-backlogs.md
around lines 1 - 8, Rename the artifact file so it follows the required
{project-slug}-{purpose}-{date}.{ext} convention; replace the current filename
"06-04-research-create-future-plugin-pack-backlogs.md" with a name like
"<project-slug>-research-YYYY-MM-DD.md" (e.g.,
"portable-ai-plugin-restructure-research-2026-05-15.md"), ensuring the project
slug matches the repository/project and the date is the creation or milestone
date; update any references to the old filename if present.
| name: "Epic" | ||
| about: "Propose/manage a large, multi-part initiative or project grouping stories/features/tasks" | ||
| title: "[Epic] Portable AI plugin restructure: planning control and target skeleton" | ||
| labels: [status:needs-planning, priority:important, area:core, type:ai-ops] |
Contributor
There was a problem hiding this comment.
Add the type:epic label to preserve epic-level automation and filtering.
Line 5 omits type:epic, which can cause parent issues to miss epic-specific workflows/views.
Suggested fix
-labels: [status:needs-planning, priority:important, area:core, type:ai-ops]
+labels: [status:needs-planning, priority:important, area:core, type:ai-ops, type:epic]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| labels: [status:needs-planning, priority:important, area:core, type:ai-ops] | |
| labels: [status:needs-planning, priority:important, area:core, type:ai-ops, type:epic] |
🤖 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/portable-ai-plugin-restructure/issues/parents/01-epic-planning-control-and-skeleton.md
at line 5, The labels array currently lists status:needs-planning,
priority:important, area:core, type:ai-ops but is missing the epic label; update
the labels array to include "type:epic" (e.g., labels: [status:needs-planning,
priority:important, area:core, type:ai-ops, type:epic]) so the parent issue
retains epic-level automation and filtering.
| name: "Epic" | ||
| about: "Propose/manage a large, multi-part initiative or project grouping stories/features/tasks" | ||
| title: "[Epic] Portable AI plugin restructure: source asset migration" | ||
| labels: [status:needs-planning, priority:important, area:core, type:ai-ops] |
Contributor
There was a problem hiding this comment.
Include type:epic in parent epic labels.
Line 5 is missing type:epic, so this parent can be excluded from epic-specific triage or reporting automation.
Suggested fix
-labels: [status:needs-planning, priority:important, area:core, type:ai-ops]
+labels: [status:needs-planning, priority:important, area:core, type:ai-ops, type:epic]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| labels: [status:needs-planning, priority:important, area:core, type:ai-ops] | |
| labels: [status:needs-planning, priority:important, area:core, type:ai-ops, type:epic] |
🤖 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/portable-ai-plugin-restructure/issues/parents/02-epic-portable-source-migration.md
at line 5, The labels array on the parent epic is missing the epic type tag;
update the labels line (the labels: [...] entry) to include "type:epic" in
addition to the existing labels so the array becomes labels:
[status:needs-planning, priority:important, area:core, type:ai-ops, type:epic],
ensuring automation and epic-specific triage will pick up this parent epic.
| name: "Epic" | ||
| about: "Propose/manage a large, multi-part initiative or project grouping stories/features/tasks" | ||
| title: "[Epic] Portable AI plugin restructure: core plugin and compatibility" | ||
| labels: [status:needs-planning, priority:important, area:core, type:ai-ops, type:compatibility] |
Contributor
There was a problem hiding this comment.
Keep parent-epic classification explicit with type:epic.
Line 5 should include type:epic; type:compatibility is complementary, not a substitute for epic classification.
Suggested fix
-labels: [status:needs-planning, priority:important, area:core, type:ai-ops, type:compatibility]
+labels: [status:needs-planning, priority:important, area:core, type:ai-ops, type:compatibility, type:epic]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| labels: [status:needs-planning, priority:important, area:core, type:ai-ops, type:compatibility] | |
| labels: [status:needs-planning, priority:important, area:core, type:ai-ops, type:compatibility, type:epic] |
🤖 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/portable-ai-plugin-restructure/issues/parents/03-epic-core-plugin-and-tool-compatibility.md
at line 5, The labels list on the epic parent entry is missing the explicit epic
classification; update the labels array to include type:epic (e.g., change
labels: [status:needs-planning, priority:important, area:core, type:ai-ops,
type:compatibility] to include type:epic) so the item is correctly recognized as
an epic; modify the labels declaration in the same block where labels are
defined to add "type:epic" alongside the existing labels.
| name: "Epic" | ||
| about: "Propose/manage a large, multi-part initiative or project grouping stories/features/tasks" | ||
| title: "[Epic] Portable AI plugin restructure: validation, docs, pilot, and release" | ||
| labels: [status:needs-planning, priority:important, area:core, area:ci, area:documentation] |
Contributor
There was a problem hiding this comment.
Add type:epic to this parent issue label set.
Without type:epic on Line 5, epic-level views and automation can miss this parent.
Suggested fix
-labels: [status:needs-planning, priority:important, area:core, area:ci, area:documentation]
+labels: [status:needs-planning, priority:important, area:core, area:ci, area:documentation, type:epic]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| labels: [status:needs-planning, priority:important, area:core, area:ci, area:documentation] | |
| labels: [status:needs-planning, priority:important, area:core, area:ci, area:documentation, type:epic] |
🤖 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/portable-ai-plugin-restructure/issues/parents/04-epic-validation-docs-and-rollout.md
at line 5, Add the missing epic type to the parent issue labels by updating the
labels array (labels: [...]) to include type:epic alongside the existing entries
(status:needs-planning, priority:important, area:core, area:ci,
area:documentation) so epic-level views and automations recognize this parent
issue.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
name: "Pull Request"
about: "General changes, refactors, and maintenance"
title: "PR: {short summary}"
labels: ["status:needs-review"]
General Pull Request
Linked issues
Closes #
Changelog
Added
Changed
Fixed
Removed
Risk Assessment
Risk Level:
Potential Impact:
Mitigation Steps:
How to Test
Prerequisites
Test Steps
Expected Results
Edge Cases to Verify
Checklist (Global DoD / PR)
References
Summary by CodeRabbit
New Features
Documentation
Chores
.github-centric to portable plugin-based layout