feat(PF-4157): restructure plugin taxonomy to 6 plugins - #95
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (23)
📒 Files selected for processing (82)
📝 WalkthroughWalkthroughThis PR reorganizes the plugin taxonomy by consolidating and renaming plugins. The marketplace catalogs, plugin manifests, and all documentation are updated to replace design-foundations, figma, issue-management, and repo-management with new plugins: code-review, design-to-code, migration, and pf-workshop. React plugin skills are refined with expanded testing guidance. ChangesPlugin Marketplace and Manifest Updates
React Plugin and Workshop Skills Refinement
Repository Documentation Sync
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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.
Actionable comments posted: 5
🤖 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 `@PLUGINS.md`:
- Line 76: Update the description for the `pf-create-issue` entry in PLUGINS.md
to use the hyphenated form "follow-up tracking" instead of "followup tracking"
so the line reads: | `pf-create-issue` | Create GitHub issues for PatternFly
repositories with smart templates, follow-up tracking, and duplicate detection.
|
In `@plugins/code-review/README.md`:
- Around line 29-38: The fenced code block showing the repository tree in
README.md is missing a language tag which triggers markdownlint MD040; update
the opening fence in the snippet that contains the tree (the block starting with
``` and the tree lines "code-review/ ├── .claude-plugin/ ...") to use the text
language (i.e., change the opening fence to ```text) so the tree block is typed
and the lint warning is resolved.
In `@plugins/design-to-code/README.md`:
- Around line 45-61: Update the fenced code block that shows the repository tree
in README.md to include the language identifier "text" (i.e., change the opening
triple backticks to ```text) so the markdown linter rule MD040 is satisfied;
locate the fenced block that begins with the triple backticks followed by the
design-to-code/ tree and add the "text" specifier to the opening fence.
In `@plugins/migration/README.md`:
- Around line 31-40: The code fence showing the directory tree in README.md
lacks a language tag and triggers MD040; update the opening fence for the block
that begins with "migration/" to use a language tag (e.g., change "```" to
"```text") so the markdown linter passes and the tree is treated as plain text.
In `@plugins/pf-workshop/README.md`:
- Around line 53-73: Update the fenced block in README.md that shows the
pf-workshop directory tree to specify the language "text" (change the opening
fence from ``` to ```text) so the markdown code fence is explicitly labeled;
locate the directory tree block under README.md around the pf-workshop/ listing
and update its fence accordingly to satisfy markdownlint MD040.
🪄 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.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 446d1b43-fc1e-4298-bd8b-0857e518d9e8
⛔ Files ignored due to path filters (23)
plugins/design-to-code/skills/pf-ai-experience-patterns/references/ai-generated-content-label.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/ai-icons-actions.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/ai-icons-in-use.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/ai-icons-information.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/ai-icons-overview.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/chat-message-dont-gradients.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/chat-messages-do-control-token.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/chatbot-avatar-donts.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/chatbot-avatar-in-use.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/chatbot-avatar-robot.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/chatbot-avatar-variations.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/chatbot-donts-gradients.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/chatbot-launch-button.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/chatbot-launch-examples.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/color-dos-donts.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/color-no-gradients.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/icons-do-this.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/icons-dont-create-new.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/icons-dont-use-without-disclosure.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/transparency-components.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/transparency-notices-chatbot.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/transparency-notices-features.pngis excluded by!**/*.pngplugins/design-to-code/skills/pf-ai-experience-patterns/references/transparency-requirement.pngis excluded by!**/*.png
📒 Files selected for processing (82)
.claude-plugin/marketplace.json.cursor-plugin/marketplace.jsonCONTRIBUTING-SKILLS.mdCONTRIBUTING.mdPLUGINS.mdREADME.mdplugins/code-review/.claude-plugin/plugin.jsonplugins/code-review/.cursor-plugin/plugin.jsonplugins/code-review/README.mdplugins/code-review/skills/summarize-pr-reviews/SKILL.mdplugins/design-foundations/README.mdplugins/design-to-code/.claude-plugin/plugin.jsonplugins/design-to-code/.cursor-plugin/plugin.jsonplugins/design-to-code/README.mdplugins/design-to-code/skills/figma-changes/README.mdplugins/design-to-code/skills/figma-changes/SKILL.mdplugins/design-to-code/skills/figma-changes/examples/.figma-sync-cache.jsonplugins/design-to-code/skills/figma-changes/examples/sample-output.mdplugins/design-to-code/skills/figma-changes/examples/token-mappings.jsonplugins/design-to-code/skills/figma-changes/references/figma-api-guide.mdplugins/design-to-code/skills/figma-changes/references/template-changelog.mdplugins/design-to-code/skills/figma-changes/references/template-detailed-report.mdplugins/design-to-code/skills/figma-changes/references/template-release-notes.mdplugins/design-to-code/skills/figma-changes/references/troubleshooting.mdplugins/design-to-code/skills/figma-changes/references/validation-checklists.mdplugins/design-to-code/skills/figma-changes/report-templates.mdplugins/design-to-code/skills/figma-changes/scripts/compare-tokens.jsplugins/design-to-code/skills/figma-changes/scripts/compare-tokens.shplugins/design-to-code/skills/figma-changes/scripts/extract-figma-file-key.shplugins/design-to-code/skills/figma-changes/scripts/figma-sync.shplugins/design-to-code/skills/figma-icon-finder/SKILL.mdplugins/design-to-code/skills/figma-icon-finder/references/common-icons.mdplugins/design-to-code/skills/icon-finder/SKILL.mdplugins/design-to-code/skills/pf-ai-experience-patterns/SKILL.mdplugins/design-to-code/skills/pf-ai-experience-patterns/guidelines/design-rules.mdplugins/design-to-code/skills/pf-ai-experience-patterns/guidelines/reference-mapping.mdplugins/design-to-code/skills/pf-ai-experience-patterns/references/README.mdplugins/design-to-code/skills/pf-ai-experience-patterns/references/REFERENCE-INDEX.mdplugins/design-to-code/skills/pf-compliance-checker/SKILL.mdplugins/design-to-code/skills/pf-compliance-checker/scripts/patternfly-check.jsplugins/design-to-code/skills/pf-design-mode/SKILL.mdplugins/design-to-code/skills/pf-design-mode/references/approved-sources.mdplugins/design-to-code/skills/pf-raw-colors-scan/SKILL.mdplugins/design-to-code/skills/pf-token-auditor/SKILL.mdplugins/design-to-code/skills/pf-token-auditor/token-reference.mdplugins/figma/README.mdplugins/issue-management/README.mdplugins/migration/.claude-plugin/plugin.jsonplugins/migration/.cursor-plugin/plugin.jsonplugins/migration/README.mdplugins/migration/skills/pf-class-migration-scanner/SKILL.mdplugins/pf-workshop/.claude-plugin/plugin.jsonplugins/pf-workshop/.cursor-plugin/plugin.jsonplugins/pf-workshop/README.mdplugins/pf-workshop/skills/analytics-repo-pruning/SKILL.mdplugins/pf-workshop/skills/analytics-repo-pruning/reference.mdplugins/pf-workshop/skills/analytics-repo-pruning/scripts/analytics-repo-pruning.shplugins/pf-workshop/skills/css-var-analyzer/SKILL.mdplugins/pf-workshop/skills/css-var-analyzer/css-var-analyzer.jsplugins/pf-workshop/skills/css-var-analyzer/format-css-report.jsplugins/pf-workshop/skills/css-var-analyzer/scripts/analyze-css-vars.shplugins/pf-workshop/skills/duplicate-epic/SKILL.mdplugins/pf-workshop/skills/duplicate-epic/scripts/duplicate_epic.shplugins/pf-workshop/skills/pf-analyze-modifiers/SKILL.mdplugins/pf-workshop/skills/pf-bug-triage/SKILL.mdplugins/pf-workshop/skills/pf-bug-triage/reference.mdplugins/pf-workshop/skills/pf-create-issue/EXAMPLE.mdplugins/pf-workshop/skills/pf-create-issue/README.mdplugins/pf-workshop/skills/pf-create-issue/SKILL.mdplugins/pf-workshop/skills/pf-org-version-update/SKILL.mdplugins/pf-workshop/skills/pf-tokens/SKILL.mdplugins/pf-workshop/skills/quarterly-initiative-report/SKILL.mdplugins/pf-workshop/skills/semantic-release-troubleshooting/SKILL.mdplugins/pf-workshop/skills/summarize-jira-issues/SKILL.mdplugins/pf-workshop/skills/write-example-description/SKILL.mdplugins/react/README.mdplugins/react/skills/pf-library-test-writer/SKILL.mdplugins/react/skills/pf-unit-test-generator/SKILL.mdplugins/repo-management/.claude-plugin/plugin.jsonplugins/repo-management/.cursor-plugin/plugin.jsonplugins/repo-management/README.mdplugins/repo-management/skills/dependency-recommender/SKILL.md
💤 Files with no reviewable changes (8)
- plugins/repo-management/.cursor-plugin/plugin.json
- plugins/react/skills/pf-library-test-writer/SKILL.md
- plugins/figma/README.md
- plugins/repo-management/skills/dependency-recommender/SKILL.md
- plugins/repo-management/.claude-plugin/plugin.json
- plugins/repo-management/README.md
- plugins/design-foundations/README.md
- plugins/issue-management/README.md
4709309 to
7150191
Compare
7150191 to
b147a2f
Compare
Summary
Reorganizes the repo from the old plugin structure (design-foundations, figma, issue-management, repo-management) into the agreed 6-plugin taxonomy: react, migration, design-to-code, a11y, code-review, pf-workshop.
Other changes
Why pf-workshop?
The dual-purpose plugin (permanent team tools + skill incubator) needed a name that communicates both roles. Workshop works — a workshop has permanent tools AND the project on the bench. It does not repel contributors the way internal might, and it does not need explanation the way incubator would.
Closes #76
Summary by CodeRabbit
New Features
Chores