refactor(prompts): migrate prompt library and align label governance#750
refactor(prompts): migrate prompt library and align label governance#750ashleyshaw wants to merge 1 commit into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 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 |
There was a problem hiding this comment.
Code Review
This pull request refactors and migrates 38 reusable prompts from .github/prompts/ to the root prompts/ directory, establishing a two-tier prompt architecture and updating associated label configurations and documentation. However, the code review identified a critical issue where the specialized instructions of the migrated prompts were replaced with generic boilerplate, effectively disabling their functionality. Additionally, the reviewer noted that migration references in the READMEs should point to a central /docs/MIGRATION.md file rather than active project artifacts, and flagged the use of an absolute local file path in INDEX.md that needs to be converted to a relative path.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| # Create Implementation Plan | ||
|
|
||
| ## Context | ||
|
|
||
| Define the repository context, objective, and constraints relevant to this task. | ||
|
|
||
| ## Task | ||
|
|
||
| Describe exactly what needs to be produced and where outputs should be stored. | ||
|
|
||
| ## Constraints | ||
|
|
||
| - Use UK English. | ||
| - Keep outputs practical, reproducible, and maintainable. | ||
| - Prefer minimal, modular solutions. | ||
| - Include validation steps for quality, performance, and accessibility where applicable. | ||
|
|
||
| ## Acceptance Criteria | ||
|
|
||
| - Deliverable is complete and aligned to LightSpeed standards. | ||
| - Any generated code/documentation includes clear rationale. | ||
| - Validation checks are listed and, where possible, executed. |
There was a problem hiding this comment.
⚠️ Loss of Specialized Prompt Functionality
It appears that during the standardization process, the actual specialized instructions for this prompt (and all other 37 migrated prompts) have been entirely replaced by a generic boilerplate template. The original functional instructions have been relegated to a ## Legacy Source (For Transition) code block at the bottom of the file.
This effectively disables the specialized behavior of the prompt, making it act as a generic placeholder.
Recommendation:
Instead of using a generic boilerplate with the actual prompt commented out, the specialized instructions should be refactored to fit into the new standard structure (## Context, ## Task, ## Constraints, ## Acceptance Criteria) as the active, executable content of the prompt.
|
|
||
| - `prompts/` is the canonical location for organisation-wide reusable prompts. | ||
| - `.github/prompts/` is reserved for `.github` control-plane and repository-governance prompts. | ||
| - Migration authority: `.github/projects/active/refactor-migrate-prompts/artifacts/migration-matrix.md`. |
There was a problem hiding this comment.
Per the repository's general rules, migration maps and notes must be documented in a central /docs/MIGRATION.md file to ensure contributors can easily follow migration rules mentioned in README files across the repository. Please update this reference to point to /docs/MIGRATION.md instead of the active project artifact.
| - Migration authority: `.github/projects/active/refactor-migrate-prompts/artifacts/migration-matrix.md`. | |
| - Migration authority: [MIGRATION.md](../docs/MIGRATION.md). |
References
- Document migration maps and notes in a central
/docs/MIGRATION.mdfile to ensure contributors can follow migration rules mentioned in README files across the repository.
| ## Migration Notice | ||
|
|
||
| - Prompt migration and classification is tracked in: | ||
| - `.github/projects/active/refactor-migrate-prompts/artifacts/migration-matrix.md` |
There was a problem hiding this comment.
Per the repository's general rules, migration maps and notes must be documented in a central /docs/MIGRATION.md file. Please update this reference to point to /docs/MIGRATION.md instead of the active project artifact.
| - `.github/projects/active/refactor-migrate-prompts/artifacts/migration-matrix.md` | |
| - [MIGRATION.md](../../docs/MIGRATION.md) |
References
- Document migration maps and notes in a central
/docs/MIGRATION.mdfile to ensure contributors can follow migration rules mentioned in README files across the repository.
| - [Current .github prompt library](https://github.com/lightspeedwp/.github/tree/develop/.github/prompts) | ||
| - [Root prompts directory](https://github.com/lightspeedwp/.github/tree/develop/prompts) | ||
| - [Active projects directory](https://github.com/lightspeedwp/.github/tree/develop/.github/projects/active) | ||
| - `/Users/ash/.codex/worktrees/f767/.github/AGENTS.md` |
There was a problem hiding this comment.
Avoid using absolute local file paths (e.g., /Users/ash/...) in documentation as they are environment-specific and will not resolve for other contributors or in CI environments. Please use a relative path to reference AGENTS.md instead.
| - `/Users/ash/.codex/worktrees/f767/.github/AGENTS.md` | |
| - [AGENTS.md](../../../../AGENTS.md) |
Summary
Validation
skills/design-md-agent/pdfs/js/__tests__/installDeps.test.js