القائمة
Summarize GitHub pull requests awaiting your review with status, age, and priority. Use when triaging your review queue, prioritizing code reviews, or checking what PRs need attention.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Integrate @patternfly/design-comments into React apps for on-page design feedback, pinned comment threads, GitHub Issues sync, and Jira linking. Use when adding design comments, review overlays, or removing the commenting system from a PatternFly React project.
Check Figma designs against PatternFly v6 standards for colors, typography, spacing, and component usage. Use when validating a design before handoff, auditing existing mockups for compliance, or reviewing design token usage. Requires Figma MCP.
Identify PatternFly icons in Figma mockups and provide the correct React import statements. Use when implementing a design from Figma, verifying icon usage in a prototype, or finding the correct icon imports for React components. Requires Figma MCP.
Find raw color values (hex, rgb, hsl) in code and suggest PatternFly design token replacements. Use when auditing stylesheets for hardcoded colors or enforcing token compliance.
Audit designs against the PatternFly 6 token architecture and bridge Figma styles to PF semantic tokens. Use when validating token usage, mapping Figma variables to PF tokens, or checking designs for token compliance.
Apply Red Hat's AI design language to AI-powered features — chatbots, assistants, generation UIs. Use when building AI experiences that should follow Red Hat brand and UX patterns.
| name | summarize-pr-reviews |
| description | Summarize GitHub pull requests awaiting your review with status, age, and priority. Use when triaging your review queue, prioritizing code reviews, or checking what PRs need attention. |
Fetch all GitHub pull requests where the current user is requested as a reviewer, summarize the changes, and provide prioritization recommendations.
Identify the authenticated GitHub user's login.
Search for open PRs where the user is requested as a reviewer, sorted by most recently updated. Run both queries in parallel:
If the user asks about a specific org or repo, scope the search accordingly.
For each PR found, fetch in parallel: metadata (title, author, labels, created date), files changed (count, lines added/deleted, key paths), existing reviews and their states, and CI/check status.
Extract from each PR:
| Size | Criteria | Review Time Estimate |
|---|---|---|
| 🟢 Small | <100 lines changed, <5 files | ~10-15 min |
| 🟡 Medium | 100-500 lines, 5-15 files | ~30-60 min |
| 🔴 Large | >500 lines or >15 files | 1+ hours |
Flag PRs as high-priority when:
priority, urgent, blocker, or criticalNote when PRs involve:
Structure the output in this order. Adapt detail level to queue size: full detail for <5 PRs, grouped summaries for 5-15, top priorities only for >15.
Open with a quick snapshot:
Table of PRs that are urgent, stale (>3 days without review), security/hotfix, or blocking others. Include a "Why Priority" column.
For each priority PR, provide a detail block:
+X/-Y lines across N filesRemaining PRs in suggested review order. Table with PR number, repository, author, size, wait time, and notes. Detail blocks for each.
Compact table of small PRs that can be knocked out quickly — good for short time blocks.
Flag concerning patterns:
Numbered list combining priority, size, and wait time into a recommended sequence. End with an estimated total review time.
Understand the changes:
Identify what matters:
Make it actionable:
Provide context:
Adapt to queue size: